Apywire: Lazy Object Wiring and Dependency Injection for Python 3.12

Posted19 days agoActive15 days ago

gaigalas

1 points

1 comments

github.comProgrammingstory

informativeneutral

Debate

0/100

PythonDependency InjectionProgramming

Key topics

Python

Dependency Injection

Programming

Discussion Activity

Light discussion

First comment

N/A

Peak period

78-84h

Avg / period

1.2

Key moments

01Story posted
Dec 15, 2025 at 8:04 AM EST
19 days ago
Step 01
02First comment
Dec 15, 2025 at 8:04 AM EST
0s after posting
Step 02
03Peak activity
2 comments in 78-84h
Hottest window of the conversation
Step 03
04Latest activity
Dec 19, 2025 at 10:04 AM EST
15 days ago
Step 04

Generating AI Summary...

Analyzing up to 500 comments to identify key contributors and discussion patterns

Discussion (1 comments)

Showing 6 comments

compressedgas

17 days ago

1 reply

This reminds me of _The Billion-Dollar Fix: Safe Modular Circular Initialisation with Placeholders and Placeholder Types_ https://dl.acm.org/doi/abs/10.1007/978-3-642-39038-8_9 https://ecs.wgtn.ac.nz/foswiki/pub/Main/TechnicalReportSerie...

Apywire reports it can't handle circular dependency: https://github.com/alganet/apywire/blob/1c9a39df36a9385d8b34...

gaigalasAuthor

16 days ago

1 reply

The code you pointed to in apywire is related to circular dependencies in constant scalar types. Like a printf that is meant to replace %s with its whole output (therefore, impossible).

However, apywire also throws CircularWiringError if you make objects that have circular dependencies as well (we do not solve it).

The paper seems like a worth read. I skimmed over it, and it seems like an interesting solution: proxy-like objects that only allow construction-type interaction but no method calls or property access until the container fully realizes the instance.

Our overall syntax allows for that implementation in the future, and python in theory is flexible enough to allow us to go for that route.

It does seem like a lot of work, but I might try to do it (for objects, for the scalars it's impossible). I was looking for a nice feature to make the project more distinct!

Thanks for your feedback!

compressedgas

16 days ago

2 replies

It is around where CircularWiringError is thrown from the implementation of topological sort. If the instantiation of the objects was not lazy, the topological sort would have been applied to the entire dependency graph. As it is lazy, with objects being created when they are accessed CircularWiringError can be thrown upon access. I think this should never happen as it should be checked for in the Wiring constructor though the application of the topological sort.

gaigalasAuthor

15 days ago

Again, thanks for your feedback. Moving the topological sort not only yileded a better experience but actually simplified the code and thread model.

I've made the changes and they'll be on the next version.

gaigalasAuthor

15 days ago

You are right, that is an overlook on my part. Throwing on the constructor makes much more sense than upon access.

Thanks!

gaigalasAuthor

19 days ago

Small project I've been developing. It's designed to make configuration easier, after many frustrations with omegaconf and hydra in the past.

Would love to hear feedback!

View full discussion on Hacker News

ID: 46273981Type: storyLast synced: 12/15/2025, 1:05:15 PM

Want the full context?

Jump to the original sources

Read the primary article or dive into the live Hacker News thread when you're ready.

Open link View on HN