On Sat, Feb 19, 2022 at 01:35:25AM +1100, Chris Angelico <[email protected]>
wrote:
> On Sat, 19 Feb 2022 at 01:30, Steven D'Aprano <[email protected]> wrote:
> >
> > On Fri, Feb 18, 2022 at 01:18:55PM +1100, Chris Angelico wrote:
> >
> > > OR! You maintain your own requirements.txt manually, and always use
> > > 'pip install -r requirements.txt' when you change it.
> >
> > That only works the first two times you use pip to install something. On
> > the third time, you write a shell script to automate the process, and by
> > the time you have finished debugging the script, the reason for creating
> > the venv in the first place is no longer relevent.
> >
> > *wink*
>
> Not sure. I can type 'pip install -r re<tab>" fairly quickly, so
> there's nothing to script. Not every one-line operation needs to be a
> shell script.
pip i<tab> -r re<tab> # ;-)
> > Isn't the issue here that pip is not a full package manager, but just an
> > installer?
>
> Hmm, what do you expect it to be? It installs, it removes, it resolves
> dependencies, it upgrades.
It doesn't replace. I cannot declare package "X" to be replacement
for package "y". I cannot declare "y" is outdated by "X".
It doesn't have post-install and pre-uninstall scripts. Post-install
can be implemented for sdists but not for wheels.
> ChrisA
Oleg.
--
Oleg Broytman https://phdru.name/ [email protected]
Programmers don't die, they just GOSUB without RETURN.
_______________________________________________
Python-ideas mailing list -- [email protected]
To unsubscribe send an email to [email protected]
https://mail.python.org/mailman3/lists/python-ideas.python.org/
Message archived at
https://mail.python.org/archives/list/[email protected]/message/H4WMS4VNTJT25VIKTBAU23U7O7LRHVMF/
Code of Conduct: http://python.org/psf/codeofconduct/
