-
Notifications
You must be signed in to change notification settings - Fork 14
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
Remove six
from production code
#12
Conversation
There are a couple references to python2 in |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we need to remove references to python2 in packaging directories?
Probably, but I'm actually not sure what it's going to take to re-write the debian packaging stuff to work "correctly" with the new hatch build? |
Removes the `six` module from released production code. The old code in the test cases used for testing compatability still uses `six`, so it is kept as a dev dependency. Signed-off-by: Joshua Watt <[email protected]>
I do know a bit about debian packaging so I might be able to help out what that. The pep-517 backend stuff will be new to me, but I assume the upstream debian python packaging helper scripts know about it. |
Seems like |
Upstream Fedora will eventually need to switch over to our new repo, but the current source for the old |
Okay, I'll merge this. |
hmm.... i don't think using a clean update/install it fails with:
|
Blerg sorry |
|
We may need to refactor for a newer urllib (urllib3 or something like that from memory). |
Removes the
six
module from released production code. The old code in the test cases used for testing compatability still usessix
, so it is kept as a dev dependency.