Antoine Pitrou antoine at python.org
Fri Jun 6 16:05:52 CEST 2014

• Previous message: [Python-Dev] asyncio/Tulip: use CPython as the new upstream
• Next message: [Python-Dev] asyncio/Tulip: use CPython as the new upstream
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

Le 06/06/2014 07:00, R. David Murray a écrit :
>
> I don't have any opinion on the workflow.
>
> My understanding is that part of the purpose of the "provisional"
> designation is to allow faster evolution (read: fixing) of an API before
> the library becomes non-provisional.  Thus I agree with Guido here, and
> will be doing something similar with at least one of the minor provisional
> email API features in 3.4.2 (unless I miss the cutoff again ... :(

I would personally distinguish API fixes (compatibility-breaking 
changes) from feature additions (new APIs).

Regards

Antoine.

---

• Previous message: [Python-Dev] asyncio/Tulip: use CPython as the new upstream
• Next message: [Python-Dev] asyncio/Tulip: use CPython as the new upstream
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

More information about the Python-Dev mailing list