On 17 December 2016 at 20:39, brett.cannon wrote:
> https://hg.python.org/cpython/rev/287d4290b1b4
> changeset: 105714:287d4290b1b4
> branch: 2.7
> parent: 105677:eb02db65e148
> user:Brett Cannon
> date:Sat Dec 17 12:38:54 2016 -0800
> summary:
> Update the porting H
I have updated the porting HOWTO to drop recommending unicode_literals and
also to mention running optional type checkers like mypy and pytype twice
(once under Python 2 and again under Python 3).
On Fri, 16 Dec 2016 at 11:25 Guido van Rossum wrote:
> I am beginning to think that `from __future_
It is my pleasure to announce the release of Python 2.7.13, the latest
bugfix release of the venerable Python 2.7 series. This release
incorporates conservative bugfixes as well as improvements to keep
Python 2.7 running on modern systems.
The only change from the 2.7.13 release candidate 2 weeks
On 17 December 2016 at 21:58, Serhiy Storchaka wrote:
> On 17.12.16 13:44, Christian Heimes wrote:
>
>> On 2016-12-17 10:06, Serhiy Storchaka wrote:
>>
>>> On 16.12.16 21:24, Guido van Rossum wrote:
>>>
e.g. the argument to getattr() -- I still hear of code that breaks due
to this occas
On 17.12.16 13:44, Christian Heimes wrote:
On 2016-12-17 10:06, Serhiy Storchaka wrote:
On 16.12.16 21:24, Guido van Rossum wrote:
e.g. the argument to getattr() -- I still hear of code that breaks due
to this occasionally)
What is the problem with unicode in getattr()? Unicode attribute name
On 2016-12-17 10:06, Serhiy Storchaka wrote:
> On 16.12.16 21:24, Guido van Rossum wrote:
>> e.g. the argument to getattr() -- I still hear of code that breaks due
>> to this occasionally)
>
> What is the problem with unicode in getattr()? Unicode attribute name is
> converted to str, and since th
On 16.12.16 21:24, Guido van Rossum wrote:
e.g. the argument to getattr() -- I still hear of code that breaks due
to this occasionally)
What is the problem with unicode in getattr()? Unicode attribute name is
converted to str, and since the result is cached, this even don't add
much overhead.
