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 to classifiers supported python versions #12

Closed
wants to merge 1 commit into from

Conversation

shurph
Copy link

@shurph shurph commented Apr 19, 2019

It will help those people who will do some version compatability checking with officially recomended tool caniusepython3 which looks exactly into classifiers to detect that an examined lib supports Python 3.

I think it might especially helpful for those who realized that Python 2 EOL is coming :-)

Related to #8.

It will help those people who will do some version compatability
checking with officially recomended tool **caniusepython3** which
looks exactly into classifiers to detect that an examined lib supports
Python 3.
@shurph
Copy link
Author

shurph commented Apr 19, 2019

Hi folks from Odeon, @stefantalpalaru, could you please look at this PR when you will have a chance?

Also it will be really awesome to push a latest version of the lib to pypi, as described in #7 and #11.

/cc @djm, @madhusudancs

@djm
Copy link

djm commented Apr 19, 2019

@shurph Hey. Did you mean to mention me? If so, I'll need reminding as to why - I haven't dealt with this project for a while to my recent knowledge.

@shurph
Copy link
Author

shurph commented Apr 19, 2019

Hey @djm, I just mention you because I saw your commits in the project, very old commits although… I'm just wondering maybe you have access to push this project to PyPI or to merge PRs. Or… Maybe you know someone who can do it.

BTW, I'm sorry to bother you with this "blast form the past" :-)

@djm
Copy link

djm commented Apr 19, 2019

Haha, so I do! I'm afraid the only knowledge I have is that Odeon CG seem to no longer be a trading entity.

I think your best bet might be to fork the project, rename and push to PyPI yourself. Unless you can get in touch with anyone that is..

@stefantalpalaru
Copy link

stefantalpalaru commented Apr 19, 2019

I'm maintaining it here: https://github.com/stefantalpalaru/django-pygments

I'm afraid the PyPI package was uploaded by someone with no relation to the project. Take it up with PyPI maintainers who allow this to happen: https://pypi.org/project/django-pygments/

@shurph
Copy link
Author

shurph commented Apr 19, 2019

@stefantalpalaru, thank you for information!
Unfortunately it seems like there are no a maintainer's contact info in the PyPI…
I will try to contact with PyPI folks to figure is it possible to contact with the current maintainer or even change ownership.

Are you interested to keep going with django-pygments support and also support the lib in PyPI?
If so I think it's a good idea to delegate a PyPI lib ownership to you and change the lib's homepage to stefantalpalaru/django-pygments instead of the current odeoncg/django-pygments (if it is possible at all).

@stefantalpalaru
Copy link

Yes, I'm interested. Thanks for the help.

@shurph
Copy link
Author

shurph commented Apr 19, 2019

@stefantalpalaru, before starting this process… I have a concern regarding an license change in you fork . I've described details there: stefantalpalaru#1

@shurph
Copy link
Author

shurph commented Nov 26, 2019

This repositore is the main one now: https://github.com/stefantalpalaru/django-pygments/issues

@shurph shurph closed this Nov 26, 2019
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.

None yet

3 participants