-
Notifications
You must be signed in to change notification settings - Fork 64
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
version 3.0.4 (PyPi) fails building octavia due to setuptools 67+ being very strict on PEP 440 #652
Closed
3 tasks done
Comments
ajkavanagh
added a commit
to ajkavanagh/charm-tools
that referenced
this issue
Mar 9, 2023
PEP-440 is more strict about requirement lines. As an example: pytz>dev is non-compliant, but is in 5.2.4 of kombu's requirements. This breaks building wheelhouses from source (such as the octavia charm). This patch pins pip and setuptools to the latest versions that will defintely still allow PEP-440 non-compliant packages to install. The option --upgrade-buildvenv-core-deps can be used to override this and will install the latest versions of pip and setuptools available. Fixes-Bug: juju#652
3 tasks
javacruft
pushed a commit
that referenced
this issue
Mar 14, 2023
PEP-440 is more strict about requirement lines. As an example: pytz>dev is non-compliant, but is in 5.2.4 of kombu's requirements. This breaks building wheelhouses from source (such as the octavia charm). This patch pins pip and setuptools to the latest versions that will defintely still allow PEP-440 non-compliant packages to install. The option --upgrade-buildvenv-core-deps can be used to override this and will install the latest versions of pip and setuptools available. Fixes-Bug: #652
Closed by #653 |
ajkavanagh
added a commit
to ajkavanagh/charm-tools
that referenced
this issue
Mar 15, 2023
to allow PEP-440 non compliance. (backported relevant parts from master branch in juju#653) PEP-440 is more strict about requirement lines. As an example: pytz>dev is non-compliant, but is in 5.2.4 of kombu's requirements. This breaks building wheelhouses from source (such as the octavia charm). This patch pins pip and setuptools to the latest versions that will defintely still allow PEP-440 non-compliant packages to install. The option --upgrade-buildvenv-core-deps can be used to override this and will install the latest versions of pip and setuptools available. Fixes-Bug: juju#652
3 tasks
ajkavanagh
added a commit
to ajkavanagh/charm-tools
that referenced
this issue
Mar 15, 2023
to allow PEP-440 non compliance. (backported relevant parts from master branch in juju#653) PEP-440 is more strict about requirement lines. As an example: pytz>dev is non-compliant, but is in 5.2.4 of kombu's requirements. This breaks building wheelhouses from source (such as the octavia charm). This patch pins pip and setuptools to the latest versions that will defintely still allow PEP-440 non-compliant packages to install. The option --upgrade-buildvenv-core-deps can be used to override this and will install the latest versions of pip and setuptools available. Fixes-Bug: juju#652
javacruft
pushed a commit
that referenced
this issue
Mar 15, 2023
to allow PEP-440 non compliance. (backported relevant parts from master branch in #653) PEP-440 is more strict about requirement lines. As an example: pytz>dev is non-compliant, but is in 5.2.4 of kombu's requirements. This breaks building wheelhouses from source (such as the octavia charm). This patch pins pip and setuptools to the latest versions that will defintely still allow PEP-440 non-compliant packages to install. The option --upgrade-buildvenv-core-deps can be used to override this and will install the latest versions of pip and setuptools available. Fixes-Bug: #652
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Checklist
What version am I running?
I'm using 3.0.4 from PyPi inside charmcraft.
I am using: Ubuntu 22.04
Versions of relevant modules within charm-build run:
Issue/Feature
Charm build fails with:
Apparenty,
pytz>dev
is not a valid PEP440 requirements string. It would need to bepytz>0.dev.0
. Anyway, I can't change that package as it is buried many dependencies down.setuptools >= 67 seems to have become very strict. I think, but will test, that setuptools < 67 will still work with non PEP440 valid requirement lines.
Possible fix
The possible fixes are to just pin setuptools < 67 for the moment, or to provide an option to allow the pip requirement to be passed as an option. I'll investigate both those issues.
The text was updated successfully, but these errors were encountered: