Skip to content
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

Add a LegacySpecifierSet #92

Closed
wants to merge 1 commit into from

Conversation

jimporter
Copy link

@jimporter jimporter commented Jan 25, 2017

This creates a LegacySpecifierSet class that can be used for specifying version requirements when you know you have LegacyVersions. I tried to make it similar to the Version/LegacyVersion split, so it has a .prereleases attribute, even though it doesn't do much with it.

This should fix #74.

@dstufft
Copy link
Member

dstufft commented Jan 26, 2017

Huh, I'm not sure what the tests that are failing mean. I'll take a look to figure out why.

@jimporter
Copy link
Author

Yeah, it looked like it couldn't find Python 2.6? I ran test_specifiers.py locally and it was all good, but I was having trouble with tox.

@xavfernandez
Copy link
Member

@jimporter Could you rebase on master ?

@jimporter jimporter force-pushed the legacy-specifier-set branch from 8c74c88 to 50c0aa3 Compare November 1, 2017 08:25
@jimporter
Copy link
Author

@xavfernandez Ok, rebased. Sorry for not seeing this sooner!

@jaraco
Copy link
Member

jaraco commented Nov 13, 2017

Travis is failing because not all of this new behavior is covered by tests. The exact lines that aren't covered are indicated in the job output. Please expand the tests to satisfy the 100% test coverage that packaging currently implements.

@albertosottile
Copy link

Are there still plans to pull this? If you need help for expanding the test coverage, I could do that.

@jimporter
Copy link
Author

@albertosottile I doubt I'll have time to look at this in the foreseeable future, so feel free to take this and fix it up!

@jimporter jimporter force-pushed the legacy-specifier-set branch 3 times, most recently from 73d757c to 663da25 Compare December 23, 2019 23:35
@jimporter
Copy link
Author

@brettcannon It looks like you've been doing reviews for this project lately. I think everything here is (finally) good to go, aside from maybe tweaking the type annotation stuff. I didn't look too hard at how Python type annotations work, so it's possible I'm doing a few things wrong there.

@pradyunsg pradyunsg changed the title Add a LegacySpecifierSet; resolves #74 Add a LegacySpecifierSet Dec 24, 2019
@brettcannon
Copy link
Member

@jimporter my reviews have been very much contained to a single module packaging.tags and my involvement is about to wane significantly as I have been letting other projects suffer while I focused on things here. IOW I'm not the right person to pull into this review. 😄

@jimporter
Copy link
Author

@brettcannon No worries! I know the feeling of neglecting other projects (which is why I had to put this PR aside for 3 years...).

@jimporter jimporter requested a review from pradyunsg January 28, 2020 09:04
@jimporter
Copy link
Author

@pradyunsg Would you be the right person to review this? If not, feel free to unflag yourself and/or redirect to a better person. Thanks!

@pradyunsg pradyunsg self-assigned this Feb 6, 2020
@pradyunsg
Copy link
Member

I think so -- I'll take a look sometime early next week. Feel free to ping me if I don't though. :)

@jimporter jimporter force-pushed the legacy-specifier-set branch from 0c72b4b to f1893d5 Compare July 10, 2020 04:22
@jimporter jimporter force-pushed the legacy-specifier-set branch from f1893d5 to 3e4d297 Compare July 10, 2020 05:08
@jimporter
Copy link
Author

@pradyunsg I totally forgot about this thanks to all the craziness from the pandemic, but this should be fixed up and ready to merge after a review. :)

@jimporter
Copy link
Author

Closing this in light of #321.

@jimporter jimporter closed this Sep 29, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Legacy versions aren't in SpecifierSets if the specifier is PEP 440-compatible
7 participants