Re: [Python-Dev] Exact date of Python 2 EOL?

2017-03-24 Thread Barry Warsaw
On Mar 24, 2017, at 04:03 PM, Nick Coghlan wrote:

>As far as I'm aware, Samba is the main remaining challenge for Fedora
>Server on that front, but at least all of the libraries it depends on have
>received the necessary updates to make them Python 2/3 compatible:
>http://fedora.portingdb.xyz/pkg/samba/

Samba is the last big one keeping 2.7 on the Ubuntu desktop edition as well.

-Barry


pgp0RfH3tstoy.pgp
Description: OpenPGP digital signature
___
Python-Dev mailing list
[email protected]
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com


[Python-Dev] Await and Async keywords

2017-03-24 Thread Aymeric Fromherz
Hi,

I'm currently looking into how Python3 is parsed, and I'm wondering why
await and async aren't considered as keywords? Are there programs
actually using await and async as variable names? Is there another
behaviour where it is interesting to use async for something different?

Cheers,
Aymeric
___
Python-Dev mailing list
[email protected]
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com


Re: [Python-Dev] Await and Async keywords

2017-03-24 Thread Jelle Zijlstra
2017-03-24 3:57 GMT-07:00 Aymeric Fromherz :

> Hi,
>
> I'm currently looking into how Python3 is parsed, and I'm wondering why
> await and async aren't considered as keywords? Are there programs
> actually using await and async as variable names? Is there another
> behaviour where it is interesting to use async for something different?
>
> They are not keywords to prevent breaking backwards compatibility, but
they will be full keywords in 3.7. async/await was introduced in 3.5, and
Python generally avoids introducing backwards-incompatible in minor
versions. Usually, that's done with __future__ imports; if I recall
correctly, when "with" statements were introduced (making "with" a
keyword), Python first released one or two versions where you had to do
"from __future__ import with_statement" to use them, and then this flag was
turned on by default. For async/await, instead the parser was hacked to
recognize "async def" as a special token, and to add special parsing rules
within "async def" function to recognize other uses of async and await.
However, this is temporary and async and await will be full keywords in
Python 3.7. See https://www.python.org/dev/peps/pep-0492/#transition-plan.

And yes, real code uses async and await as identifiers. asyncio itself had
a function called asyncio.async() (now renamed to ensure_future()). Making
async and await full keywords would have immediately broken any such code
for people who were upgrading to Python 3.5.



> Cheers,
> Aymeric
> ___
> Python-Dev mailing list
> [email protected]
> https://mail.python.org/mailman/listinfo/python-dev
> Unsubscribe: https://mail.python.org/mailman/options/python-dev/
> jelle.zijlstra%40gmail.com
>
___
Python-Dev mailing list
[email protected]
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com


Re: [Python-Dev] Await and Async keywords

2017-03-24 Thread Aymeric Fromherz
Thanks for the quick answer! I'll have a look at this PEP.

Cheers

On 24/03/2017 16:17, Jelle Zijlstra wrote:
> 
> 
> 2017-03-24 3:57 GMT-07:00 Aymeric Fromherz  >:
> 
> Hi,
> 
> I'm currently looking into how Python3 is parsed, and I'm wondering why
> await and async aren't considered as keywords? Are there programs
> actually using await and async as variable names? Is there another
> behaviour where it is interesting to use async for something different?
> 
> They are not keywords to prevent breaking backwards compatibility, but
> they will be full keywords in 3.7. async/await was introduced in 3.5,
> and Python generally avoids introducing backwards-incompatible in minor
> versions. Usually, that's done with __future__ imports; if I recall
> correctly, when "with" statements were introduced (making "with" a
> keyword), Python first released one or two versions where you had to do
> "from __future__ import with_statement" to use them, and then this flag
> was turned on by default. For async/await, instead the parser was hacked
> to recognize "async def" as a special token, and to add special parsing
> rules within "async def" function to recognize other uses of async and
> await. However, this is temporary and async and await will be full
> keywords in Python 3.7.
> See https://www.python.org/dev/peps/pep-0492/#transition-plan.
> 
> And yes, real code uses async and await as identifiers. asyncio itself
> had a function called asyncio.async() (now renamed to ensure_future()).
> Making async and await full keywords would have immediately broken any
> such code for people who were upgrading to Python 3.5.
> 
>  
> 
> Cheers,
> Aymeric
> ___
> Python-Dev mailing list
> [email protected] 
> https://mail.python.org/mailman/listinfo/python-dev
> 
> Unsubscribe:
> 
> https://mail.python.org/mailman/options/python-dev/jelle.zijlstra%40gmail.com
> 
> 
> 
> 
___
Python-Dev mailing list
[email protected]
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com


[Python-Dev] Summary of Python tracker Issues

2017-03-24 Thread Python tracker

ACTIVITY SUMMARY (2017-03-17 - 2017-03-24)
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:
  open5860 (+19)
  closed 35792 (+40)
  total  41652 (+59)

Open issues with patches: 2431 


Issues opened (40)
==

#29838: Check that sq_length and mq_length return non-negative result
http://bugs.python.org/issue29838  opened by serhiy.storchaka

#29839: Avoid raising OverflowError in len() when __len__() returns ne
http://bugs.python.org/issue29839  opened by serhiy.storchaka

#29840: Avoid raising OverflowError in bool()
http://bugs.python.org/issue29840  opened by serhiy.storchaka

#29841: errors raised by bytes and bytearray constructors for invalid 
http://bugs.python.org/issue29841  opened by Oren Milman

#29842: Make Executor.map work with infinite/large inputs correctly
http://bugs.python.org/issue29842  opened by josh.r

#29843: errors raised by ctypes.Array for invalid _length_ attribute
http://bugs.python.org/issue29843  opened by Oren Milman

#29844: Windows Python installers not installing DLL to System32/SysWO
http://bugs.python.org/issue29844  opened by TBBle

#29846: ImportError: Symbol not found: __PyCodecInfo_GetIncrementalDec
http://bugs.python.org/issue29846  opened by ajstewart

#29847: Path takes and ignores **kwargs
http://bugs.python.org/issue29847  opened by Jelle Zijlstra

#29851: Have importlib.reload() raise ImportError when a spec can't be
http://bugs.python.org/issue29851  opened by Richard Cooper

#29852: Argument Clinic: add common converter to Py_ssize_t that accep
http://bugs.python.org/issue29852  opened by serhiy.storchaka

#29854: Segfault when readline history is more then 2 * history size
http://bugs.python.org/issue29854  opened by nirs

#29857: Provide `sys.executable_argv` for host application's command l
http://bugs.python.org/issue29857  opened by ncoghlan

#29858: inspect.signature includes bound argument for wrappers around 
http://bugs.python.org/issue29858  opened by anton-ryzhov

#29860: smtplib.py doesn't capitalize EHLO.
http://bugs.python.org/issue29860  opened by Lord Anton Hvornum

#29862: Fix grammar typo in importlib.reload() exception
http://bugs.python.org/issue29862  opened by brett.cannon

#29863: Add a COMPACT constant to the json module
http://bugs.python.org/issue29863  opened by brett.cannon

#29867: Add asserts in PyXXX_GET_SIZE macros
http://bugs.python.org/issue29867  opened by serhiy.storchaka

#29868: multiprocessing.dummy missing cpu_count
http://bugs.python.org/issue29868  opened by johnwiseman

#29869: Underscores in numeric literals not supported in lib2to3.
http://bugs.python.org/issue29869  opened by nevsan

#29870: ssl socket leak
http://bugs.python.org/issue29870  opened by thehesiod

#29871: Enable optimized locks on Windows
http://bugs.python.org/issue29871  opened by josh.r

#29877: compileall hangs when accessing urandom even if number of work
http://bugs.python.org/issue29877  opened by virtuald

#29878: Add global instances of int 0 and 1
http://bugs.python.org/issue29878  opened by serhiy.storchaka

#29879: typing.Text not available in python 3.5.1
http://bugs.python.org/issue29879  opened by Charles Bouchard-Légaré

#29881: Add a new private API clear private variables, which are initi
http://bugs.python.org/issue29881  opened by haypo

#29882: Add an efficient popcount method for integers
http://bugs.python.org/issue29882  opened by niklasf

#29883: asyncio: Windows Proactor Event Loop UDP Support
http://bugs.python.org/issue29883  opened by Adam Meily

#29885: Allow GMT timezones to be used in datetime.
http://bugs.python.org/issue29885  opened by Decorater

#29886: links between binascii.{un,}hexlify / bytes.{,to}hex
http://bugs.python.org/issue29886  opened by chrysn

#29887: test_normalization doesn't work
http://bugs.python.org/issue29887  opened by serhiy.storchaka

#29888: The link referring to "Python download page" is broken
http://bugs.python.org/issue29888  opened by cocoatomo

#29889: test_asyncio fails always
http://bugs.python.org/issue29889  opened by Thomas Knox

#29890: Constructor of ipaddress.IPv*Interface does not follow documen
http://bugs.python.org/issue29890  opened by Ilya.Kulakov

#29891: urllib.request.Request accepts but doesn't check bytes headers
http://bugs.python.org/issue29891  opened by ezio.melotti

#29892: change statement for open() is splited into two part in middle
http://bugs.python.org/issue29892  opened by OSAMU.NAKAMURA

#29893: create_subprocess_exec doc doesn't match software
http://bugs.python.org/issue29893  opened by Torrin Jones

#29894: Deprecate returning a subclass of complex from __complex__
http://bugs.python.org/issue29894  opened by serhiy.storchaka

#29895: Distutils blows up with an incorrect pypirc, should be caught
http://bugs.python.org/issue29895  opened by Tommy Carpenter

#29896: ElementTree.fromstring raises undocumen