Open mgedmin opened 1 year ago
Hey @mgedmin, I can see how this is unexpected and could be considered a bug, considering the CLI called for building the suds
package. I'd be open to a fix if you can find one.
I think an alternative answer is to release a final version of suds-community that has a simple dependency on a recent version of suds
. An example I've seen is here: https://github.com/simonw/pypi-rename. I believe that would be non-breaking to consumers of suds-community.
I'm trying to keep a local mirror of all the package so our builds can work even if PyPI goes down temporarily. This is how I noticed this rare corner case:
I expect it's because the setup.py in suds-1.1.2.tar.gz calls
setup(name='suds-community', ...)
if you don't know to define the SUDS_PACKAGE environment variable.I won't be bothered too much if you close this bug as WONTFIX because preparing slightly different setup.py files for the twin suds vs suds-community releases might be a pain, and people can use wheels which do not suffer from this problem.