On 5 May 2017 at 16:01, Victor Stinner wrote:
> Le 5 mai 2017 6:31 AM, "Nick Coghlan" a écrit :
>
> The note just needs to say that folks that care about doing "complete"
> builds need to adjust their command sequence to be "./configure
> && make regen-all && make install", rather than the previ
Le 5 mai 2017 6:31 AM, "Nick Coghlan" a écrit :
The note just needs to say that folks that care about doing "complete"
builds need to adjust their command sequence to be "./configure
&& make regen-all && make install", rather than the previous
pattern of "./configure && make install".
Hum, yo
On 5 May 2017 at 02:25, Antoine Pitrou wrote:
> On Thu, 4 May 2017 11:24:27 +0900
> INADA Naoki wrote:
>> Hi, Nick and all core devs who are interested in this PEP.
>>
>> I'm reviewing PEP 538 and I want to accept it in this month.
>> It will reduces much UnicodeError pains which server-side OPs
On 4 May 2017 at 08:25, Victor Stinner wrote:
> If you start to backport support for the fspath protocol, be prepared
> to have to backport it *many* places. I expect that slowly in the near
> future, many functions will be patched to support the fspath protocol.
>
> I suggest to only do that in m
On 5 May 2017 at 03:40, Brett Cannon wrote:
> I see no issue backporting since I don't think we have any compatibility
> promises when it comes to Makefile commands. Plus if the perf changes to add
> PGO support could be backported then I don't see why this shouldn't be
> allowed.
For the benefit
On Sat, Mar 4, 2017 at 11:50 PM, Nick Coghlan wrote:
>
> Providing implicit locale coercion only when running standalone
> ---
>
> Over the course of Python 3.x development, multiple attempts have been made
> to improve the handling of in
On Thu, May 4, 2017 at 8:30 PM, Terry Reedy wrote:
> On 5/4/2017 10:43 AM, Koos Zevenhoven wrote:
>> On Thu, May 4, 2017 at 4:19 AM, Terry Reedy wrote:
>>> Enhancing public APIs in normal (non-provisional) modules in bugfix
>>> releases
>>> has turned out to be a bad thing to do. Hence the polic
FWIW this will also make cross-compiling a lot easier, since you can't
accidentally overwrite the cross-compiled pgen as easily.
On Thu, May 4, 2017 at 12:13 PM, Victor Stinner
wrote:
> Hi,
>
> tl;dr Are you ok to backport my change replacing "make touch" with
> "make regen-all"? (commit a5c62a8e
On 04.05.17 21:01, Berker Peksağ wrote:
We've already backported a few patches that improves the PEP 519
support in the stdlib with the permission from the release manager of
3.6. I'd ask Ned whether bpo-30218 qualifies for backporting to 3.6.
AFAIK it was before releasing 3.6.1. Some users avo
On Wed, May 3, 2017 at 9:15 PM, Brett Cannon wrote:
> My allergies have hit me hard so I'm not thinking at full capacity, but did
> we ever decide if supporting os.PathLike in the stdlib was viewed as an
> enhancement or bugfix? Specifically I'm thinking of
> https://bugs.python.org/issue30218 for
Yes. It is perfectly reasonable to backport improvements to the tooling as
long as it doesn't break anyone's existing build process.
Sent from my iPhone
> On May 4, 2017, at 10:13 AM, Victor Stinner wrote:
>
> tl;dr Are you ok to backport my change replacing "make touch" with
> "make regen-a
I see no issue backporting since I don't think we have any compatibility
promises when it comes to Makefile commands. Plus if the perf changes to
add PGO support could be backported then I don't see why this shouldn't be
allowed.
On Thu, 4 May 2017 at 10:15 Victor Stinner wrote:
> Hi,
>
> tl;dr
On 5/4/2017 10:43 AM, Koos Zevenhoven wrote:
On Thu, May 4, 2017 at 4:19 AM, Terry Reedy wrote:
What did not get done for 3.6 should be proposed for 3.7.
Anyone, feel free. The nightmare part is done, so this could be a case
where a PR actually pays off in terms of being able to use the
fea
Thanks for the feedback, everyone. I'll just consider it an enhancement
then.
On Wed, 3 May 2017 at 15:07 Terry Reedy wrote:
> On 5/3/2017 2:15 PM, Brett Cannon wrote:
> > My allergies have hit me hard so I'm not thinking at full capacity, but
> > did we ever decide if supporting os.PathLike in
Hi,
tl;dr Are you ok to backport my change replacing "make touch" with
"make regen-all"? (commit a5c62a8e)
Since the creation of CPython, generated files were regenerated
depending on file modification time. For development, that's a
convenient feature. But in practice, it caused a long list of
On Thu, 4 May 2017 11:24:27 +0900
INADA Naoki wrote:
> Hi, Nick and all core devs who are interested in this PEP.
>
> I'm reviewing PEP 538 and I want to accept it in this month.
> It will reduces much UnicodeError pains which server-side OPs facing.
> Thank you Nick for working on this PEP.
>
>
On 03.05.17 21:15, Brett Cannon wrote:
My allergies have hit me hard so I'm not thinking at full capacity, but
did we ever decide if supporting os.PathLike in the stdlib was viewed as
an enhancement or bugfix? Specifically I'm thinking
of https://bugs.python.org/issue30218 for adding support to
s
On 4 May 2017 at 04:15, Brett Cannon wrote:
> My allergies have hit me hard so I'm not thinking at full capacity, but did
> we ever decide if supporting os.PathLike in the stdlib was viewed as an
> enhancement or bugfix? Specifically I'm thinking of
> https://bugs.python.org/issue30218 for adding
On 4 May 2017 at 12:24, INADA Naoki wrote:
> [PEP 538]
>> * PEP 540 proposes to entirely decouple CPython's default text encoding from
>> the C locale system in that case, allowing text handling inconsistencies to
>> arise between CPython and other locale-aware components running in the same
>
On Thu, May 4, 2017 at 4:19 AM, Terry Reedy wrote:
> On 5/3/2017 7:13 PM, Koos Zevenhoven wrote:
>>
[...]
>> Shutil was among the most important to be updated, IMO.
>>
>> I had made some sort of list of affected modules elsewhere [1]:
>> ntpath, posixpath, os.scandir, os.[other stuff], DirEntry (
20 matches
Mail list logo
