[Python-ideas] Re: Irrelevant venv? [was: Requirements.txt inside virtual environment]

2022-02-20 Thread Stephen J. Turnbull
Steven D'Aprano writes:
 > On Sat, Feb 19, 2022 at 04:14:57PM +0900, Stephen J. Turnbull wrote:
 > > Steven D'Aprano writes:
 > > 
 > >  > by the time you have finished debugging the script, the reason for
 > >  > creating the venv in the first place is no longer relevent.
 > > 
 > > Eh?  Would you be willing to unpack that reference to 'venv'
 > > specifically, or was that just your patent-pending snark?  I can't
 > > recall a venv being obviated by later developments,
 > 
 > You have never created a venv and then later decided that it wasn't 
 > needed because the project was cancelled, the job fell through, somebody 
 > solved the problem in another way, your client changed the project 
 > specifications and you deleted the old venv and created a new one, you 
 > decided to work on something else instead, the company went bust,
 > etc? 

Oh, sure, that happens.  If most of a code base goes away, of course
so does the venv.  That's actually a feature!  But the *reason* for a
venv in the first place is to ensure that neither the system nor the
project pollutes the other with the "wrong" version of some
dependency.  I thought *that* was the "reason" you referred to as
becoming irrelevant.

 > we sure are touchy about any suggestion that pip and venvs aren't
 > the greatest tools ever made.

Eh, no, I really wanted to know if the need for isolation that venvs
provide somehow goes away and under what circumstances.  I have
nothing invested in pip or venvs that would prevent me from adopting
(or even helping to develop) something better (at least for future
projects).

 > Here's a hint for the future. When I follow a comment with a smiley
 > emoticon or emoji, or *wink*, it means that my comment isn't
 > intended to be taken too seriously.

Well, yes, that's why I asked whether it was your patent-pending
snark.  Thank you for confirming that it was.

 > especially the tendency to spend more time automating a task than will 
 > ever be saved by the automation.

LOL.  All of the automation using pip and venvs that I work with has
more than paid back my investment (especially those that were
developed by somebody else! :-)

Yet-another-Steve-who-knows-how-when-and-why-to-use-smilies

___
Python-ideas mailing list -- python-ideas@python.org
To unsubscribe send an email to python-ideas-le...@python.org
https://mail.python.org/mailman3/lists/python-ideas.python.org/
Message archived at 
https://mail.python.org/archives/list/python-ideas@python.org/message/MGZVFLUZILV6JBG7LLJEOMVUJAFNYU7S/
Code of Conduct: http://python.org/psf/codeofconduct/


[Python-ideas] Re: Irrelevant venv? [was: Requirements.txt inside virtual environment]

2022-02-19 Thread Steven D'Aprano
On Sat, Feb 19, 2022 at 04:14:57PM +0900, Stephen J. Turnbull wrote:
> Steven D'Aprano writes:
> 
>  > by the time you have finished debugging the script, the reason for
>  > creating the venv in the first place is no longer relevent.
> 
> Eh?  Would you be willing to unpack that reference to 'venv'
> specifically, or was that just your patent-pending snark?  I can't
> recall a venv being obviated by later developments,

You have never created a venv and then later decided that it wasn't 
needed because the project was cancelled, the job fell through, somebody 
solved the problem in another way, your client changed the project 
specifications and you deleted the old venv and created a new one, you 
decided to work on something else instead, the company went bust, etc? 
Lucky you.

For a mailing list community that loves to be hyper-skeptical about the 
usefulness of 90% of ideas proposed here, we sure are touchy about any 
suggestion that pip and venvs aren't the greatest tools ever made.

Here's a hint for the future. When I follow a comment with a smiley 
emoticon or emoji, or *wink*, it means that my comment isn't intended to 
be taken too seriously. It's a bit of light-hearted banter. And there's 
at least a 50% chance that it is intended to be self-mocking, or at 
least affectionate teasing of the tropes and memes that are common in 
programming circles, such as the "Three Strikes Rule".

http://wiki.c2.com/?ThreeStrikesAndYouAutomate

especially the tendency to spend more time automating a task than will 
ever be saved by the automation. Even XKCD has joked about that.

https://xkcd.com/1319/


-- 
Steve
___
Python-ideas mailing list -- python-ideas@python.org
To unsubscribe send an email to python-ideas-le...@python.org
https://mail.python.org/mailman3/lists/python-ideas.python.org/
Message archived at 
https://mail.python.org/archives/list/python-ideas@python.org/message/OFCA37W4N7Z3X6LKIL3V3DA7G6LA2G63/
Code of Conduct: http://python.org/psf/codeofconduct/