On 13 November 2017 at 04:38, Antoine Pitrou wrote:
> On Sun, 12 Nov 2017 12:20:45 +
> Paul Moore wrote:
>>
>> > Well, not exactly. Do you do python -m venv, or py -x.x -m venv or
>> > pythonx -m venv ? Wait, it's not installed by default on debian.
2017-11-13 3:32 GMT+01:00 Nick Coghlan :
>
> So technically it's ensurepip that's broken by default, but that
> translates to venv also being broken by default.
>
> I haven't worked out what the actual steps needed to fix it are
>
On Debian, ensurepip is in the
On 12 November 2017 at 13:18, Nick Coghlan wrote:
>> Seriously? Debian don't provide venv in the standard Python install?
>> That's just broken.
>
> Yup. And RHEL/CentOS don't provide Python 3.x by default at all - you
> need to grab it via other means.
Wow. I have no problem
On 2017-11-12 05:18, Nick Coghlan wrote:
* the `pip install` option really is nicer looking than `python -m pip
install`, and it only has actual problems in the presence of multiple
Python versions and when upgrading pip itself on Windows (plus: lots
of third party guides recommend it, as do
On 12 November 2017 at 16:20, Michel Desmoulin
wrote:
> Le 10/11/2017 à 09:01, Nick Coghlan a écrit :
>> On 10 November 2017 at 17:05, Michel Desmoulin
>> wrote:
>> When we choose not to use venv, then it becomes necessary to ensure
>> each
On 12 November 2017 at 06:19, Michel Desmoulin
wrote:
>> 1. Go back to adding Python to PATH. Because our installers don't say
>> "do you want to uninstall the old version", we should probably do a
>> check for a "python" command on PATH in the installer, and if there
On 12 November 2017 at 22:20, Paul Moore wrote:
> On 12 November 2017 at 06:19, Michel Desmoulin
> wrote:
>>> We still have to deal with the fact that basically every Unix
>>> environment is "advanced" in the above sense (the python2/python3
>>>
On Sun, 12 Nov 2017 23:18:26 +1000
Nick Coghlan wrote:
>
> We haven't forgotten our early years - we've just spent years (both
> individually and collectively) working on the problem of helping
> people get started with software development, and thus have a very
> good idea
2017-11-12 13:20 GMT+01:00 Paul Moore :
> On 12 November 2017 at 06:19, Michel Desmoulin
> wrote:
>
> > Well, not exactly. Do you do python -m venv, or py -x.x -m venv or
> > pythonx -m venv ? Wait, it's not installed by default on debian.
>
>
On Sun, 12 Nov 2017 12:20:45 +
Paul Moore wrote:
>
> > Well, not exactly. Do you do python -m venv, or py -x.x -m venv or
> > pythonx -m venv ? Wait, it's not installed by default on debian.
>
> Seriously? Debian don't provide venv in the standard Python install?
>
On 12 November 2017 at 18:38, Antoine Pitrou wrote:
> On Sun, 12 Nov 2017 12:20:45 +
> Paul Moore wrote:
>>
>> > Well, not exactly. Do you do python -m venv, or py -x.x -m venv or
>> > pythonx -m venv ? Wait, it's not installed by default on debian.
On Mon, Nov 13, 2017 at 6:24 AM, Stephan Houben wrote:
> Hi Antoine,
>
> The venv module is included,
> however the pyvenv script is in a separate package
> python3.5-venv .
>
> By the way, I was totally confused by the following text form the doc.
>
>
Hi Antoine,
The venv module is included,
however the pyvenv script is in a separate package
python3.5-venv .
By the way, I was totally confused by the following text form the doc.
https://docs.python.org/3/library/venv.html
Deprecated since version 3.6: pyvenv was the recommended tool
Hi Stephan,
Le 12/11/2017 à 20:24, Stephan Houben a écrit :
> Hi Antoine,
>
> The venv module is included,
> however the pyvenv script is in a separate package
> python3.5-venv .
Thanks for the correction. That's definitely a silly decision --
especially as the "pyvenv" script must be very
On 13 November 2017 at 02:59, Brendan Barnwell wrote:
> On 2017-11-12 05:18, Nick Coghlan wrote:
>>
>> * the `pip install` option really is nicer looking than `python -m pip
>> install`, and it only has actual problems in the presence of multiple
>> Python versions and when
On 13 November 2017 at 07:11, Chris Angelico wrote:
> On Mon, Nov 13, 2017 at 6:24 AM, Stephan Houben wrote:
>> Hi Antoine,
>>
>> The venv module is included,
>> however the pyvenv script is in a separate package
>> python3.5-venv .
>>
>> By the way, I was
On Mon, Nov 13, 2017 at 10:29 AM, Nick Coghlan wrote:
> On 13 November 2017 at 07:11, Chris Angelico wrote:
>> On Mon, Nov 13, 2017 at 6:24 AM, Stephan Houben wrote:
>>> Hi Antoine,
>>>
>>> The venv module is included,
>>> however the
> -Original Message-
> From: Python-ideas [mailto:python-ideas-bounces+tritium-
> list=sdamon@python.org] On Behalf Of Nick Coghlan
> Sent: Sunday, November 12, 2017 6:19 PM
> To: Brendan Barnwell
> Cc: python-ideas@python.org
> Subject: Re: [Python-ideas]
On 13 November 2017 at 09:29, Nick Coghlan wrote:
> On 13 November 2017 at 07:11, Chris Angelico wrote:
>> On Mon, Nov 13, 2017 at 6:24 AM, Stephan Houben wrote:
>>> Hi Antoine,
>>>
>>> The venv module is included,
>>> however the
19 matches
Mail list logo