Reject my own PEP 511 (code transformers)
This commit is contained in:
parent
c99fb8bf5b
commit
9d8fd95001
22
pep-0511.txt
22
pep-0511.txt
|
@ -3,12 +3,32 @@ Title: API for code transformers
|
|||
Version: $Revision$
|
||||
Last-Modified: $Date$
|
||||
Author: Victor Stinner <victor.stinner@gmail.com>
|
||||
Status: Draft
|
||||
Status: Rejected
|
||||
Type: Standards Track
|
||||
Content-Type: text/x-rst
|
||||
Created: 4-January-2016
|
||||
Python-Version: 3.6
|
||||
|
||||
Rejection Notice
|
||||
================
|
||||
|
||||
This PEP was rejected by its author.
|
||||
|
||||
This PEP was seen as blessing new Python-like programming languages
|
||||
which are close but incompatible with the regular Python language. It
|
||||
was decided to not promote syntaxes incompatible with Python.
|
||||
|
||||
This PEP was also seen as a nice tool to experiment new Python features,
|
||||
but it is already possible to experiment them without the PEP, only with
|
||||
importlib hooks. If a feature becomes useful, it should be directly part
|
||||
of Python, instead of depending on an third party Python module.
|
||||
|
||||
Finally, this PEP was driven was the FAT Python optimization project
|
||||
which was abandonned in 2016, since it was not possible to show any
|
||||
significant speedup, but also because of the lack of time to implement
|
||||
the most advanced and complex optimizations.
|
||||
|
||||
|
||||
Abstract
|
||||
========
|
||||
|
||||
|
|
Loading…
Reference in New Issue