On 15.05.2016 19:30, Guido van Rossum wrote:
Right. I still have no good intuition for what Type[BasicUser,
ProUser] would mean so I think you should be required to use the
Union, which is clear. Type[] should only allow one parameter.
Type[A, B] reminds me of isinstance(obj, (A, B)).
Sven
_
Hi,
I modified regrtest to not ignore -j1 anymore (issue #25285). I also
modified Tools/buildbot/test.bat to add the -j1 option (-j1 was
already used on UNIX on "make buildbottest").
All buildbots will now run each test file in a fresh subprocess. It
helps to restrict all kinds of side effects of
ACTIVITY SUMMARY (2016-05-13 - 2016-05-20)
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:
open5504 ( +3)
closed 33322 (+52)
total 38826 (+55)
Open issues wit
Is there a specific reason for calling out two spaces in comments after a
period(I realize it's probably for consistency, but I sure don't ever think
about this when I write comment)? Otherwise who actually still writes using
two spaces after punctuation? :)
In Emacs, the paragraph reflow commands still try to keep a period
followed by only one space together on a line, under the assumption
that it might be something like `Dr. Brett Cannon`. A reasonable HTML
generator should ignore the second space. So all in all I still like
the two-space rule -- not
On 05/20/2016 01:27 PM, Brett Cannon wrote:
Is there a specific reason for calling out two spaces in comments after a
period(I realize it's probably for consistency, but I sure don't ever think
about this when I write comment)? Otherwise who actually still writes using
two spaces after punctuatio
On Fri, May 20, 2016 at 1:27 PM, Brett Cannon wrote:
> Is there a specific reason for calling out two spaces in comments after a
> period(I realize it's probably for consistency, but I sure don't ever think
> about this when I write comment)? Otherwise who actually still writes using
> two spaces
Three questions:
1. Should pathlib gain __fspath__() all the way back to 3.4?
2. Should pathlib's constructor support __fspath__() all the way back to
3.4? (separate question as os.fspath() will only be in 3.6; and if we
backport I'm not looking forward to making Typeshed happy w/o os.
On 05/20/2016 09:27 AM, Brett Cannon wrote:
Is there a specific reason for calling out two spaces in comments after
a period(I realize it's probably for consistency, but I sure don't ever
think about this when I write comment)? Otherwise who actually still
writes using two spaces after punctuati
ALso, in case anyone reading this didn't realize, this is a classic
internet debate that has been going on for decades (just not on
python-dev). Just Google it.
On Fri, May 20, 2016 at 9:40 AM, Facundo Batista
wrote:
> On Fri, May 20, 2016 at 1:27 PM, Brett Cannon wrote:
>
>> Is there a specific
Let's start in 3.6 with all this. I added path to 3.4 because I didn't
realize it was in security-mode only. I've now undone all my work
there. Let's not disturb it again, not even its docs.
I don't think there's an "upstream" repo for pathlib (like there still
is for asyncio) and I don't think th
Nick Coghlan wrote:
> PEP 3121 is insufficient, since a lot of extension modules can't (or
> at least haven't) adopted it in practice.
> https://www.python.org/dev/peps/pep-0489/ has some more background on
> that (since it was the first step towards tackling the problem in a
> different way that
On 05/20/2016 09:27 AM, Brett Cannon wrote:
The period is a full-stop punctuation mark, but visually obscure [1].
It is small. This does not make it hard to notice, however. Not to
mention that it will usually be followed by a capitalized letter, which
further highlights it. Commas usually us
On Fri, 20 May 2016 at 09:46 Guido van Rossum wrote:
> ALso, in case anyone reading this didn't realize, this is a classic
> internet debate that has been going on for decades (just not on
> python-dev). Just Google it.
>
Yes, I don't mean to suggest we should change the two space specification
Because Emacs. :-) I am going to mute this thread now.
On Fri, May 20, 2016 at 11:40 AM, Brett Cannon wrote:
>
>
> On Fri, 20 May 2016 at 09:46 Guido van Rossum wrote:
>>
>> ALso, in case anyone reading this didn't realize, this is a classic
>> internet debate that has been going on for decades
On Fri, 20 May 2016 at 09:56 Guido van Rossum wrote:
> Let's start in 3.6 with all this. I added path to 3.4 because I didn't
> realize it was in security-mode only. I've now undone all my work
> there. Let's not disturb it again, not even its docs.
>
> I don't think there's an "upstream" repo fo
2016-05-20 18:56 GMT+02:00 Guido van Rossum :
> Let's start in 3.6 with all this. I added path to 3.4 because I didn't
> realize it was in security-mode only.
I also had to ask the question to myself about branches, that's why I
wrote this table ;-)
https://docs.python.org/devguide/#status-of-pyth
So is line breaks before or after operators .
--
Philip Jenvey
> On May 20, 2016, at 9:46 AM, Guido van Rossum wrote:
>
> ALso, in case anyone reading this didn't realize, this is a classic
> internet debate that has been going on for decades (just not on
> python-dev). Just Google it.
>
> On
On 05/20/2016 09:15 PM, Victor Stinner wrote:
> 2016-05-20 18:56 GMT+02:00 Guido van Rossum :
>> Let's start in 3.6 with all this. I added path to 3.4 because I didn't
>> realize it was in security-mode only.
>
> I also had to ask the question to myself about branches, that's why I
> wrote this ta
19 matches
Mail list logo
