-
Notifications
You must be signed in to change notification settings - Fork 756
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
Notify users that "pep8" was renamed to "pycodestyle" #572
Comments
13 months later and I've only just noticed the name change and am still on the old pep8 1.7.0. I've updated (or tried to update) pep8 many times, and a warning would have helped me. A prominent note has been added to [2]:
Thanks! It'd be great to also put one at [1] as well. I've created PR #690 to issue a warning in pep8. |
On further investigation, it looks like the warning has already been done in d4a6003 in in May 2016 in the release/1.7.x branch, but not yet released. Please could we have a new release of pep8 with that warning? Thank you! |
1.7.1 was released with a runtime warning |
Thanks! I think this issue can be closed now.
|
There are many places were there is still outdated information refering to "pep8" instead of "pycodestyle" making no mention of the name change (#466, #481) which can be quite misleading.
For example I just installed "pep8" unaware of the fact and wondered why it was outputting a lot of W503s when it shouldn't. That's when I realized the project had been renamed and I had installed the outdated pep8 version 1.7.0 instead of the current pycodestyle 2.0.0
I'm not familiar with PyPI and don't know if there is a possibility to deprecate packages but it would be a huge help for new users if the name change was announced prominently at [1] and [2].
An updated package of pep8 with a deprecation warning might be yet another option if that's not too much to ask.
[1] https://pypi.python.org/pypi/pep8
[2] http://pep8.readthedocs.io/
The text was updated successfully, but these errors were encountered: