Zanie Blue
Zanie Blue
We do maintain `python-build-standalone`, and use it for our managed Python distributions. I don't know what's to be done about the `dbm.gnu` problem though. As described in the link, it's...
Can you share more about why / how Celery depends specifically on `dbm.gnu`? It looks like that's only the case if an existing state file created by a different Python...
I'm going to close this as this is as-designed, but feel free to comment if you have a use-case that this blocks!
That's an impressive amount of problems! Sorry you ran into these. We'll need to follow-up on a few thnings here.
Regarding the Python version constraint, it looks like this is missing from their published package Here's the wheel metadata, which does not include a `Requires-Python` field https://inspector.pypi.io/project/textual-paint/0.4.0/packages/71/ca/7929fa18b01403682da3180fedfcfeebabaa5a7e6ad773821a4e8cc7da64/textual_paint-0.4.0-py3-none-any.whl/textual_paint-0.4.0.dist-info/METADATA for an example...
Cool thanks for looking into this!
My changes in #428 will make this a little more complicated, but it's probably still worth pursuing. I'm happy to investigate it.
Hm yeah we'll use a managed Python over an unmanaged one. You think we should prefer the system CPython in this case? You can do `--python cpython3.9` or `--python cp39`...
Yeah that makes sense. We should probably change the ordering, though it'll be a bit of a pain.
Oh I might be fixing this by accident while working on #7286 haha