Just because legacy Python needs to be kept around for a bit longer for a few uses does not mean that "Python 3 is not ready yet". Any decent package system can have two or more versions of Python installed at the same time.
It is not "critical self-evaluation" to repeat "Python 3 is not ready" as litany in #Python and your supporting website. I use the word "litany" here because #Python refers users to what appears to be a religious website http://python-commandments.org/python3.html I have further witnessed (and even been the other party to) you and other ops in #Python telling package developers, who have clearly said that they are working to port their legacy package to Py3, that "Python 3 is not ready". One of our Summer of Code students this year actually included in his application that he was told (strongly) in #Python that he shouldn't be working with Py3 - even after he expressed his intent to apply under the PSF to help with the Py3 migration effort as his project. Besides rally against it what have you, as a Twisted developer, done regarding the Python 3 migration process? On Sat, Jun 19, 2010 at 8:12 AM, <exar...@twistedmatrix.com> wrote: > On 10:59 am, arcri...@gmail.com wrote: > >> You mean Twisted support, because library support is at the point where >> there are fewer actively maintained packages not yet ported than those >> which >> are. Of course if your Python experience is hyper-focused to one >> framework >> that isn't ported yet, it will certainly seem like a lot, and you guys who >> run #Python are clearly hyper-focused on Twisted. >> > > Arc, > > This isn't about Twisted. Let's not waste everyone's time by trying to > make it into a conflict between Twisted users and the rest of the Python > community. > > You listed six other major packages that you yourself use that aren't > available on Python 3 yet, so why are you trying to say here that this is > all about Twisted? > >> [snip] >> >> >> This anti-Py3 rhetoric is damaging to the community and needs to stop. >> We're moving forward toward Python 3.2 and beyond, complaining about it >> only >> saps valuable developer time (including your own) from getting these >> libraries you need ported faster. >> > > No, it's not damaging. Critical self-evaluation is a useful tool. Trying > to silence differing perspectives is what's damaging to the community. > > Jean-Paul >
_______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
