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

Added trove classifiers showing versions supported #284

Closed
wants to merge 2 commits into from

Conversation

@alex
Copy link
Member

@alex alex commented Mar 15, 2014

No description provided.

@@ -67,7 +67,14 @@
'License :: OSI Approved :: GNU Library or Lesser General Public License (LGPL)',
'Operating System :: OS Independent',
'Topic :: Internet',
'Topic :: Security :: Cryptography' ],
'Topic :: Security :: Cryptography'

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You're missing a comma here.

Loading

@alex
Copy link
Member Author

@alex alex commented Mar 17, 2014

Thanks -- fixed.

Loading

@CyrilRoelandteNovance
Copy link

@CyrilRoelandteNovance CyrilRoelandteNovance commented Mar 17, 2014

Was about to propose the same thing - this would be quite useful.

While we're at it, is the latest release compatible with Python 3? It seems like it was released just before the Python 3 branch was merged, so I guess not.

Loading

@fuhrysteve
Copy link

@fuhrysteve fuhrysteve commented Mar 18, 2014

Says Python 3 support right in the changelog for 1.13.0 http://www.paramiko.org/changelog.html

Loading

@CyrilRoelandteNovance
Copy link

@CyrilRoelandteNovance CyrilRoelandteNovance commented Mar 18, 2014

Excellent. I've pushed a pull request to caniusepython3 to whitelist paramiko: brettcannon/caniusepython3#42

Loading

@fuhrysteve
Copy link

@fuhrysteve fuhrysteve commented Mar 18, 2014

I believe this pull is all that's standing in the way of getting a green light on the Wall of Superpowers as well.

Loading

@bitprophet
Copy link
Member

@bitprophet bitprophet commented Mar 21, 2014

Crazy, I could swear this got updated during the 1.13/Python 3 stuff, but apparently not. Will backport to open lines (1.11+) ASAP. Thanks!

Think I can post-facto edit this data for some of the recent releases on PyPI as well - will do that too.

Loading

@bitprophet
Copy link
Member

@bitprophet bitprophet commented Mar 21, 2014

Edited the PyPI metadata for the latest 1.10, 1.11, 1.12 and 1.13 releases, with Python+2+2.5+2.6+2.7+2::Only for the first three, and Python+2+2.6+2.7+3+3.2+3.3 for 1.13.

Loading

@alex
Copy link
Member Author

@alex alex commented Mar 21, 2014

Cool, this should be GTG for master then?

Loading

@bitprophet
Copy link
Member

@bitprophet bitprophet commented Mar 21, 2014

@alex Well I still need to backport it in git so subsequent releases don't regress, above was just me editing PyPI TTW. Will do it in a sec!

Loading

bitprophet added a commit that referenced this issue Mar 21, 2014
@bitprophet
Copy link
Member

@bitprophet bitprophet commented Mar 21, 2014

Naturally I went in and reformatted shit too so now nothing cleanly applies. Meh. Added a changelog entry for attribution :)

Loading

@bitprophet bitprophet closed this Mar 21, 2014
@alex
Copy link
Member Author

@alex alex commented Mar 21, 2014

lol, awesome. Thanks!

Loading

@alex alex deleted the patch-2 branch Mar 21, 2014
@bitprophet
Copy link
Member

@bitprophet bitprophet commented Mar 21, 2014

Loading

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Linked issues

Successfully merging this pull request may close these issues.

None yet

4 participants