proto-pep capturing the concurrency discusion
I tried to capture all the ideas generated during the concurrency discussion early this month in the form of an informational PEP. I believe that information is worth preserving where others can find it, and a PEP seems like a logical place. Since it doesn't make a specific proposal, it's informational PEP. Possibly this is an abuse of the PEP mechanism, in which case I'll find another forum for it. The point this time is not to debate the ideas proposed, but to check for errors and omissions. If there's an alternative I missed, let me know. If there's a problem with some alternative I missed, let me know. If I think it's already in the document, I'll probably point it out and ask for suggestions on how to make it more obvious. Thanks, <mike
On Wed, Nov 23, 2011 at 9:09 AM, Mike Meyer <mwm@mired.org> wrote:
I tried to capture all the ideas generated during the concurrency discussion early this month in the form of an informational PEP. I believe that information is worth preserving where others can find it, and a PEP seems like a logical place. Since it doesn't make a specific proposal, it's informational PEP. Possibly this is an abuse of the PEP mechanism, in which case I'll find another forum for it.
The Python wiki is a fairly common location for pre-PEPs that haven't really made it to the point of proposing specific changes: http://wiki.python.org/moin/PythonEnhancementProposals It also uses ReST for formatting, so you can just drop your proto-PEP into a new page and go from there. Cheers, Nick. -- Nick Coghlan | ncoghlan@gmail.com | Brisbane, Australia
participants (2)
-
Mike Meyer -
Nick Coghlan