Re: [python-committers] python-committers is dead, long live discuss.python.org
El vie., 28 de sep. de 2018 a la(s) 18:45, Łukasz Langa (luk...@langa.pl) escribió: > We'll be enabling GitHub and social logins soon, ideally with adding > identified committers to the committers group by default. We are looking into > this right now. In the mean time, please request membership, an existing > member will add you. We'd like to migrate old discussion off of the mailing > lists to our Discourse instance so that search is immediately useful. We'll > look into that after the governance crisis is resolved. Hello! How do I request membership to the commiters group in Discourse? Thanks! -- .Facundo Blog: http://www.taniquetil.com.ar/plog/ PyAr: http://www.python.org.ar/ Twitter: @facundobatista ___ python-committers mailing list python-committers@python.org https://mail.python.org/mailman/listinfo/python-committers Code of Conduct: https://www.python.org/psf/codeofconduct/
Re: [python-committers] Python 4.0 or Python 3.10?
2018-09-25 16:30 GMT-03:00 Yury Selivanov : > deprecating APIs or behavior. Right now I'm saying "Python 4.0" > implying that 4.0 will be released right after 3.9. > > I've heard multiple opinions on this subject. One of them is that we > should release 4.0 when we have a major new change, like removal of > the GIL or introduction of a JIT compiler. On the other hand, we have > no estimate when we have such a change. We also don't want Python 4.0 > to be backwards incompatible with Python 3.0 (at least not at the > scale of 2 vs 3). So to me, it seems logical that we simply release > Python 4.0 after Python 3.9. After all, after 3.9 Python will be > drastically different from 3.0 and from 2.7. It sounds better. :) On the other hand... the best chance we have to let the world know that "we will never ever again break everything as we did with the 2 to 3 transition" is to just release 4.0 after 3.9 as a simple follow up release with just the minor and usual glitches we have from minor to minor release. IOW, we're breaking the major/minor revision evolution, but we're firmly signaling that a transition that could take a decade will not happen anymore in the future, that we learned the lesson and all evolution steps will be smooth. See it as more a political/social decision, than a technical one. Note 1: I remember Guido saying something like this, but to be fair I couldn't find any mail with a statement like that in a 10' exploration I just did. Note 2: I know we planned 2.7.10 after 2.7.9, but that just reinforces my point: the idea is to communicate that we'll never have again a dead end like 2.7. Regards, -- .Facundo Blog: http://www.taniquetil.com.ar/plog/ PyAr: http://www.python.org.ar/ Twitter: @facundobatista ___ python-committers mailing list python-committers@python.org https://mail.python.org/mailman/listinfo/python-committers Code of Conduct: https://www.python.org/psf/codeofconduct/
Re: [python-committers] PQM?
2008/8/14 Barry Warsaw [EMAIL PROTECTED]: it would be the developer who committed the broken change. The problem of not having access to all the platforms, or not being able to debug problems on those platforms is a different issue. I want to grab a little attention on this issue. It happened to me a few times that I commited code that caused platform specific problems (working with sockets, for example): sometimes it's all ok, but it fails in *one* of the buildbots. Fixing those issues is a PIA, because sometimes you may have some clue of what could have gone wrong, but it's complicated, because you can not try it. Don't know really how to improve this situations. There're two things that it'd be great to have, though: - Not only the traceback, but a very detailed traceback to download. With very detailed traceback I mean a traceback like the cgitb one: with the state of all the objects in all the frames in the traceback. - A VirtualBox image with the buildbot system ready to svn up, make and test. It needs to be done only once by somebody who knows that platform. Note that we may face license issues here. OTOH, I think I read somewhere that you somehow can send a patch only to that buildbot... where I can read more about this? Thank you!! -- . Facundo Blog: http://www.taniquetil.com.ar/plog/ PyAr: http://www.python.org/ar/ ___ python-committers mailing list python-committers@python.org http://mail.python.org/mailman/listinfo/python-committers
