On 9/19/2015 1:24 AM, Stephen J. Turnbull wrote:
Barry Warsaw writes:
> One thing that came up in a similar discussion is pip, and the
> suggested move to `python -m pip`, which makes a lot of sense.
> However, *inside* a virtualenv, there's no ambiguity about the
> Python version associ
Mark Lawrence writes:
> I agree very strongly with your point here. Raising umpteen issues
> over installation failures when a full release comes out strikes me
> as below the belt when there have been multiple previous releases
> without a squeak.
Raising issues is always useful and appropr
Barry Warsaw writes:
> One thing that came up in a similar discussion is pip, and the
> suggested move to `python -m pip`, which makes a lot of sense.
> However, *inside* a virtualenv, there's no ambiguity about the
> Python version associated with direct `pip` invocation, so it still
> makes
On 19 September 2015 at 01:16, Barry Warsaw wrote:
> On Sep 18, 2015, at 07:53 PM, Nick Coghlan wrote:
>
>>I currently use pyvenv directly, but I agree with starting a migration
>>to only supporting the more explicit "python -m venv". There's always
>>an inherent ambiguity on *nix with unqualified
On 9/18/2015 9:18 AM, Victor Stinner wrote:
Sadly, Python 3.5.0 comes with regressions. FYI I fixed the following
regressions:
The tracker needs a new keyword: '3.5regression', to match others.
"OSError in os.waitpid() on Windows"
http://bugs.python.org/issue25118
"Windows: datetime.datetim
ACTIVITY SUMMARY (2015-09-11 - 2015-09-18)
Python tracker at http://bugs.python.org/
To view or respond to any of the issues listed below, click on the issue.
Do NOT respond to this message.
Issues counts and deltas:
open5130 (+54)
closed 31798 (+45)
total 36928 (+99)
Open issues wit
On 18/09/2015 16:27, R. David Murray wrote:
Once Steve comes back from vacation he's going to have a lot of Windows
install issues to look at. IMO, we should resolve those, and then issue
3.5.1.
It's really too bad more people didn't test the installation with the
release candidates, and I'm ve
Once Steve comes back from vacation he's going to have a lot of Windows
install issues to look at. IMO, we should resolve those, and then issue
3.5.1.
It's really too bad more people didn't test the installation with the
release candidates, and I'm very glad that those people who did so did
so...
On Sep 18, 2015, at 07:53 PM, Nick Coghlan wrote:
>I currently use pyvenv directly, but I agree with starting a migration
>to only supporting the more explicit "python -m venv". There's always
>an inherent ambiguity on *nix with unqualified version sensitive
>Python commands as to whether they're
(Oh hey, I don't understand how I sent the previous email. Mistake
with keyboard shortcut in Gmail?)
Hi,
Sadly, Python 3.5.0 comes with regressions. FYI I fixed the following
regressions:
"OSError in os.waitpid() on Windows"
http://bugs.python.org/issue25118
"Windows: datetime.datetime.now() ra
Hi,
Sadly, Python 3.5.0 comes with regressions. FYI I fixed the following
regressions:
"OSError in os.waitpid() on Windows"
http://bugs.python.org/issue25118
"Windows: datetime.datetime.now() raises an OverflowError for date
after year 2038"
http://bugs.python.org/issue25155
Victor
___
On 18 September 2015 at 05:04, Barry Warsaw wrote:
> On Sep 17, 2015, at 06:40 PM, Brett Cannon wrote:
>
>>I propose that the pyvenv script be deprecated in Python 3.5.1 and
>>removed in Python 3.8. The reason for this proposal is because it is
>>non-obvious what version of Python a pyvenv command
12 matches
Mail list logo
