[Python-Dev] Getting Tulip (PEP 3156) into the 3.4 stdlib, marked provisional, named asyncio (original) (raw)
Barry Warsaw barry at python.org
Sat Sep 28 16:35:41 CEST 2013
- Previous message: [Python-Dev] Getting Tulip (PEP 3156) into the 3.4 stdlib, marked provisional, named asyncio
- Next message: [Python-Dev] Getting Tulip (PEP 3156) into the 3.4 stdlib, marked provisional, named asyncio
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Sep 27, 2013, at 09:14 PM, Brett Cannon wrote:
I don't see any issue with redirecting the discussion. python-tulip@ is acting like a SIG for the module, so no real precedent beyond it not being hosted as a mail.python.org list.
The PEP process even allows for this formally. Please add a Discussions-To header to PEP 3156. See PEP 1 for details.
-Barry
- Previous message: [Python-Dev] Getting Tulip (PEP 3156) into the 3.4 stdlib, marked provisional, named asyncio
- Next message: [Python-Dev] Getting Tulip (PEP 3156) into the 3.4 stdlib, marked provisional, named asyncio
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]