David Seddon
David Seddon
Ah right - I usually call these 'inline imports' or sometimes 'runtime imports'. Interesting idea! One way of doing this would be a bit like the `exclude_type_checking` setting which is...
> Are you going to want to essentially maintain two code bases for this functionality? I'd rather not 😄 . But it's a fairly isolated part of the code so...
> add some kind of scope property to grimp.domain.valueobjects.DirectImport I would much prefer the inline imports scanning mode to be limited to the `ImportScanner` - i.e. add an extra `inline_imports_mode`...
Thanks for requesting this. I've now updated the release steps so next time I do a release, it should 🤞🏻 build a wheel for Python 3.13. I'm not planning to...
I'm afraid I had to back out the release of the 3.13 wheel as [Py03](https://github.com/PyO3/pyo3) (a Rust crate which we use to provide Python binding to Rust) doesn't yet support...
Thanks for the link. I've subscribed to that issue now so I should be able to add this once they release 0.22.
Hmm, I just released Grimp 3.4.1 with support for Python 3.13. But for some reason the wheels are only being built for Windows. E.g. have a look in [this job...
Thanks for the nudge, yes I'll look into this ASAP.
Github automatically closed this, reopening until I can see it working!