[Python-Dev] Proposed schedule for Python 3.4 (original) (raw)
Jesus Cea jcea at jcea.es
Thu Oct 4 15:32:25 CEST 2012
- Previous message: [Python-Dev] Proposed schedule for Python 3.4
- Next message: [Python-Dev] Proposed schedule for Python 3.4
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 03/10/12 17:27, Nick Coghlan wrote:
I received a fair number of complaints from people that wanted to experiment with yield from, but couldn't, because the first alpha wasn't out yet and they weren't sufficiently interested to go to the effort of building their own copy of Python.
In my job, we do "alpha" releases quite frequently. The promises for alpha is: a) no feature complete, b) the API, etc , can change before release, c) features included are useable. The point is to use them and experiment with them.
We don't call them "alphas", but "engineering previews". And they expires after six months.
Delivering useable alphas requires to do a "minimal" of release engineering, like disabling features half done, documenting known bugs, etc. So yes, it it a bit of extra work.
In Python context, the idea of somebody using a "alpha" in production is scary, and I have a few bad experiences doing a "make install" of a alpha and when installing the final release keeping some alpha files around causing erratic behaviour until I did a "\rm -r /usr/local/SOME" and reinstall again. I think it happened to me with 2.6 :). There are some consequences here, like bytecode (pyc) changes, modules renaming or vanishing before the final release, etc.
Jesús Cea Avión // /// /// jcea at jcea.es - http://www.jcea.es/ // // // // // jabber / xmpp:jcea at jabber.org // // ///// . // // // // // "Things are not so easy" // // // // // // "My name is Dump, Core Dump" /// //_/ // // "El amor es poner tu felicidad en la felicidad de otro" - Leibniz -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://www.enigmail.net/
iQCVAwUBUG2P6Jlgi5GaxT1NAQJLBgP9GRnurLjdx2IIcrnbjGuRC0EoQF5ISh5p nVQldPRefb3c3MEpsVK0pmTDiPY0Nelepg8j8YMjZeri87AKHojMQ6Teu6NGvx/5 ZMRFsBve8YKfkqAr0ygVl8RlscOMXZsCq2iUHhc8I4L2Nqx7H7yoUDlMcak8JB4t VxYAhugWOmE= =/2aa -----END PGP SIGNATURE-----
- Previous message: [Python-Dev] Proposed schedule for Python 3.4
- Next message: [Python-Dev] Proposed schedule for Python 3.4
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]