[Python-Dev] Multilingual programming article on the Red Hat Developer blog
Since it may come in handy when discussing "Why was Python 3 necessary?" with folks, I wanted to point out that my article on the transition to multilingual programming has now been reposted on the Red Hat developer blog: http://developerblog.redhat.com/2014/09/09/transition-to-multilingual-programming-python/ I wouldn't normally bring the Red Hat brand into an upstream discussion like that, but this myth that Python 3 is killing the language, and that Python 2 could have continued as a viable development platform indefinitely "if only Guido and the core development team hadn't decided to go ahead and create Python 3", is just plain wrong, and it really needs to die. I'm hoping that borrowing a bit of Red Hat's enterprise credibility will finally get people to understand that we really do have some idea what we're doing, which is why most of our redistributors and many of our key users are helping to push the migration forward, while we also continue to support existing Python 2 users :) Cheers, Nick. -- Nick Coghlan | [email protected] | Brisbane, Australia ___ Python-Dev mailing list [email protected] https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Multilingual programming article on the Red Hat Developer blog
On Wed, Sep 10, 2014 at 05:17:57PM +1000, Nick Coghlan wrote: > Since it may come in handy when discussing "Why was Python 3 > necessary?" with folks, I wanted to point out that my article on the > transition to multilingual programming has now been reposted on the > Red Hat developer blog: > http://developerblog.redhat.com/2014/09/09/transition-to-multilingual-programming-python/ That's awesome! Thank you Nick. -- Steven ___ Python-Dev mailing list [email protected] https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Proposed schedule for 3.4.2
On 09/08/2014 05:08 AM, Nick Coghlan wrote: On 8 September 2014 14:28, Ned Deily wrote: As I've already discussed with Larry, I think adding a week to the scheduled dates would be preferable. The original dates give pretty short notice and there are a number of open issues that would be good to resolve now in 3.4.2. It would also be good to get Guido's official verdict on PEP 476 (the switch to validating HTTPS by default) in time for 3.4.2. Based on the previous discussion, Alex updated the PEP to suggest "just fix it" for all of 3.5, 3.4.x and 2.7.x (including the httplib SSLContext support backport in the latter case). I think that would be feasible with an rc on the 20th, but challenging if the rc is this coming weekend. Okay, the thread has died down. It seems like pushing back a week will possibly help. So the new dates: 3.4.2 rc 1: September 22, 2014 3.4.2 final: October 6, 2014 //arry/ ___ Python-Dev mailing list [email protected] https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
[Python-Dev] recursive closure
Hello, Can someone explain me why gc(CPython) can not collect recursive closure's cycle reference? There is no __del__ here, why gc can not collect? Thanks a lot. For example: #!/usr/bin/env python import ipdb import gc gc.set_debug(gc.DEBUG_LEAK) def A(): N = [1] def aa(n): if n in N: return 1 else: return n * aa(n-1) x = 33 + aa(10) #ipdb.set_trace() print x if __name__ == '__main__': while xrange(1000): A() -- Best Li Tianqing___ Python-Dev mailing list [email protected] https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] recursive closure
On Thu, Sep 11, 2014 at 12:55 PM, Li Tianqing wrote: > Hello, > Can someone explain me why gc(CPython) can not collect recursive > closure's cycle reference? There is no __del__ here, why gc can not > collect? Can you start by explaining what's not getting collected and what is? Where's the cycle you're looking at? Also, this thread would do better on [email protected] rather than python-dev. ChrisA ___ Python-Dev mailing list [email protected] https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
