Closed hackaugusto closed 8 years ago
Hi!
Looks like that setup.py file has created more issues that its worth... I'm going to solve this for once and for all, but I'm afraid you might not like it.
Over the next few days I'll make a new 2.0 release which removes the file completely. There will be one (and only one) way to install it, either to ~/.pythonz, the user specified PYTHONZ_ROOT or systemwide.
That is as far as I plan to take this tool and I won't be taking patches to change this. I've given some thought to it, and ultimately it comes down to the cost of maintenance. I made pythonz because pythonbrew was abandoned and did too many things, pythonz is supposed to do one thing and do it well (or as good as possible!).
Sorry about that.
Before giving up on pythonz, I'd like to understand what's the problem in merging #90
Merging that would solve the problem with setup.py, so you wouldn't have to spend time maintaining it: once it's working it won't spontaneously break, and I also double checked again, and the pythonz installer works with those changes.
By default the project saves the patches inside the ROOT folder, that only works if the user uses the
pythonz-install
script, but wont work withpython setup.py install --user
since the patches won't be copied to the ROOT directory.