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

Reconsider the name? #9

Closed
ncoghlan opened this Issue Jan 2, 2018 · 7 comments

Comments

Projects
None yet
2 participants
@ncoghlan

ncoghlan commented Jan 2, 2018

This is a really cool project, and as an individual, I really like the current name :)

As a Python Packaging User Guide maintainer though, I'm far less keen on the idea of explaining to folks what SNAFU means (even though it's a thoroughly accurate description of the world of software distribution in general).

While I know it's less fun that way, would you be willing to consider a more boring name like winpyenv or winpyrm? (the latter would be short for "WINdows PYthon Runtime Manager")

@uranusjr

This comment has been minimized.

Owner

uranusjr commented Jan 2, 2018

I agree; the name was chosen half as an inside joke, and is suitable only as a personal project.

I personally really dislike pyenv’s name (the env part is so confusing), so that’s probably out. I’m fine winpyrm in general, but it sounds like we’re removing something (the rm part).

Some other possible directions…

  • pywinst (does this miss the managing part?)
  • pywm or pwm (”Python for Windows“ Manager)

@uranusjr uranusjr added the help wanted label Jan 2, 2018

@ncoghlan

This comment has been minimized.

ncoghlan commented Jan 2, 2018

Unfortunately wininst is a bit confusing due to the old bdist_wininst format, and pyinstaller is similarly out due to the project that makes full Windows installers for Python projects.

winpym (for "WINdows PYthon Manager", pronounced "win-pim") would avoid the "rm" suffix, while pym4win ("PYthon Manager for WINdows") would avoid colliding with the existing (non-Python) program "WinPIM".

@uranusjr

This comment has been minimized.

Owner

uranusjr commented Jan 2, 2018

Or maybe just pym?

@uranusjr

This comment has been minimized.

Owner

uranusjr commented Jan 4, 2018

It occurred to me while working on another similar tool this is basically what rustup is to Rust. So… pythonup? Just throwing it out.

@ncoghlan

This comment has been minimized.

ncoghlan commented Jan 5, 2018

pythonup could work - I'd originally discounted it due to https://pyup.io/, but https://www.google.com.au/search?q=pythonup looks promisingly empty.

And if you eventually expanded beyond Windows (e.g. by depending on pyenv), the name would still fit.

@uranusjr

This comment has been minimized.

Owner

uranusjr commented Jan 5, 2018

I think I’ll go with PythonUp then. I already built a similar tool for Mac (as a Homebrew Tap), and yes it is depending on pyenv (more specifically the bundled python-build plugin). :p

@uranusjr uranusjr referenced this issue Jan 5, 2018

Open

Migrate to PythonUp #11

2 of 4 tasks complete
@uranusjr

This comment has been minimized.

Owner

uranusjr commented Jan 5, 2018

Tracking in #11.

@uranusjr uranusjr closed this Jan 5, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment