[code-quality] Is the pep8-naming project moribund?

[Florent]

Hello,

thank you for your interest in this project.

Actually, I've created the pep8-naming package one year ago as a
proof-of-concept for a pep8 extension.
It evolved quickly as the first extension to flake8 2.0.

At this time I declared that I don't intend to maintain it, and I
asked for a volunteer to continue the effort :
https://github.com/jcrocholl/pep8/issues/44#issuecomment-14000874

So I welcome you on-board, and I just gave you write access to the repository.


-- 
Florent


2014-04-17 1:12 GMT+02:00 Keith Derrick <keith.derrick at lge.com>:
> There are numerous issues open, and at least one pull-request (mine).
> there has been no activity by the owner for at least a year.
>
> Right now the official pypi version (2.2.1) is broken for Python 3.4. My
> PR (https://github.com/flintwork/pep8-naming/pull/11) is working well
> for me in my own fork, but I'm working up a library of my own and don't
> want to use my fork as an installation requirement when I finally
> publish to pypi.
>
> How do we re-invigorate the project?
>
> And, out of curiosity,  if the owner of a published package has 'gone
> away' (i.e. abandoned the project), how does someone else take it over?
> Forking is easy enough, but you would eventually need to publish the new
> version on pypi. Is that protected (so that people can't hijack a
> trusted package like paramiko or pycrypto, for example)? It could be
> always be published with a different package name, but then existing
> users don't get the bug-fix automatically.
>
> Keith
> _______________________________________________
> code-quality mailing list
> code-quality at python.org
> https://mail.python.org/mailman/listinfo/code-quality