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.
If you have something worrying about this PEP, please post a
On 5/3/2017 7:13 PM, Koos Zevenhoven wrote:
On Thu, May 4, 2017 at 1:07 AM, 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 the stdlib was
On Thu, May 4, 2017 at 1:07 AM, 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 the stdlib was viewed as an
>> enhancement or bugfix?
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 master. It's not that hard to cast
manually to a string:
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 the stdlib was viewed as
an enhancement or bugfix? Specifically I'm thinking of
https://bugs.python.org/issue30218 for adding support
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
shutil.unpack_archive() and whether it
On Wed, May 3, 2017 at 4:16 AM, Erik Bray wrote:
> I have been saying for several months now that I would like to set up
> a Cygwin buildbot--an important step in making that platform
> supportable again. I now have the infrastructure available to do so
> (Windows VM on an
On Wed, 3 May 2017 at 01:24 Victor Stinner wrote:
> Hi,
>
> I spent last week working on fixing buildbots:
>
>https://www.python.org/dev/buildbot/
>
> It should now be able again to rely on them to detect regressions.
Thanks, Victor!
> Changes:
>
> * Fix various
You can remove thread_foobar.h. I don't think that anyone still wants
to use this template. The other thread_*.h files can be used as
template as well.
Victor
___
Python-Dev mailing list
Python-Dev@python.org
Good catch! It's actually a template for writing a threading adaptation for
new platforms. But it's probably hopelessly out of date so unless someone
wants to adopt it and keep it up to date, we can delete it. (Also, new
platforms with unique threading APIs don't come along at the rate they did
in
Hi, python-dev.
I'm reading the part of threading feature to replace TLS API with TSS API
(PEP 539). Python/thread_foobar.h hasn't be included to Python/thread.c
(its include directive is comment out) and anywhere. This looks like dead
code and we want to delete it, does anyone have a reason we
On Wed, May 3, 2017 at 10:22 AM, Victor Stinner
wrote:
> Hi,
>
> I spent last week working on fixing buildbots:
>
>https://www.python.org/dev/buildbot/
>
Thanks!
> * Add more buildbots! Zachary Ware proposed to add a buildbot running
> "regen-all" to check that
Hi,
I spent last week working on fixing buildbots:
https://www.python.org/dev/buildbot/
It should now be able again to rely on them to detect regressions. Changes:
* Fix various bugs (I don't even recall which ones)
* Fix multiple random failures
* Fix dozen of warnings
I also enhanced the
13 matches
Mail list logo