Re: Opinions on name for PyPI
Mark Lawrence <[email protected]>
| Newsgroups | gmane.comp.python.wxpython.devel |
|---|---|
| Message-ID | <[email protected]> |
On Tuesday, April 4, 2017 at 4:32:33 AM UTC+1, Robin Dunn wrote: > > Hi all, > > I'm getting ready to test uploading a Phoenix alpha to PyPI, basically as > a proof-of-concept of a few of the major changes since Classic > (installer-less binaries, more fully using PyPI, using buildbot to make > release binaries, etc.) IMO, this is the last hurdle we need to cross > before getting into a more regular release mode, and pushing forward from > there. > > Anyway, the question came up for what name to use for Phoenix going > forward. All of us here know what Phoenix is and how it relates to Classic, > (and what Classic is, for that matter) but I expect that the name could > cause some confusion for the rest of the Python community, especially folks > new to Python. Here are the options as I see them: > > wxPython_Phoenix: Leave things as they are now and try to reduce > potential confusion through READMEs and other documentation, release > announcements, etc. > > wxPython: This will certainly preserve the perceptual continuity from > Classic to Phoenix, but until Classic is more than just mostly dead I think > there will be too much potential for confusion between the two if Phoenix > was released under this name. > > wx: Mariano Reingart has been using this project name to facilitate doing > unofficial builds/installs for linux from a snapshot of the code from > August. He has added me as an owner on PyPI so we could use this name if it > makes sense. It's short and sweet, and given that it matches the top-level > package name, it will probably be the first thing that people try to `pip > install` if they are not already familiar with the wxPython name. > > wxPhoenix: This name hasn't really been on my radar for long, but > somebody used it in an email recently and it's kind of been growing on me. > > Any other suggestions? > > -- > Robin Dunn > Software Craftsman > http://wxPython.org > My preference by millions of light years is to stick with wxPython. It should be obvious to anyone attempting to get the code from pypi that's it's Python 3 only from the file names for the wheels. A note saying that this is the new Phoenix but you can still download the old Classic from xyz.com wouldn't go amiss. To be completely fail safe why not put the question to the main Python mailing list? Also consider that the Python Packaging Authority (PyPa) are working on a new code base for pypi called Warehouse https://pypi.org/ so perhaps their advice should be sort. Kindest regards. Mark Lawrence -- You received this message because you are subscribed to the Google Groups "wxPython-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.