Re: [sage-devel] Re: Bug or feature - questoin about databindings
Am 10.07.2010 15:04, schrieb William Stein [...] This is standard Python behaviour. A list comprehension doesn't have its own scope, so the p used in the list comprehension overwrites the other p previously declared in the same scope. I agree that this can be annoying, but it's a fact of life in Python programming. ... albiet, a temporary one (!): wst...@redhawk:~$ python3.1 Python 3.1.2 (r312:79147, Apr 15 2010, 15:35:48) [GCC 4.4.3] on linux2 Type help, copyright, credits or license for more information. [i*i for i in range(10)] [0, 1, 4, 9, 16, 25, 36, 49, 64, 81] i Traceback (most recent call last): File stdin, line 1, in module NameError: name 'i' is not defined The point being that in Python 3.x this fact of life is change. Eventually, Sage will switch to Python 3.x. William is there a way to build sage testwise with python 3.x? For example by setting a special path/variable or replace some files? greatz Johannes -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
Re: [sage-devel] Re: Bug or feature - questoin about databindings
On Sat, Jul 10, 2010 at 3:13 PM, Johannes dajo.m...@web.de wrote: Am 10.07.2010 15:04, schrieb William Stein [...] This is standard Python behaviour. A list comprehension doesn't have its own scope, so the p used in the list comprehension overwrites the other p previously declared in the same scope. I agree that this can be annoying, but it's a fact of life in Python programming. ... albiet, a temporary one (!): wst...@redhawk:~$ python3.1 Python 3.1.2 (r312:79147, Apr 15 2010, 15:35:48) [GCC 4.4.3] on linux2 Type help, copyright, credits or license for more information. [i*i for i in range(10)] [0, 1, 4, 9, 16, 25, 36, 49, 64, 81] i Traceback (most recent call last): File stdin, line 1, in module NameError: name 'i' is not defined The point being that in Python 3.x this fact of life is change. Eventually, Sage will switch to Python 3.x. William is there a way to build sage testwise with python 3.x? For example by setting a special path/variable or replace some files? Not yet. But you can try. It won't happen until somebody tries (really hard)... William greatz Johannes -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org -- William Stein Professor of Mathematics University of Washington http://wstein.org -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
[sage-devel] Re: Bug or feature - questoin about databindings
On 7/10/10 6:04 AM, William Stein wrote: Eventually, Sage will switch to Python 3.x. Things are accelerating. On the numpy/scipy list from today: As many of you probably already know, Numpy works fully on Python 3 and Python 2, with a *single code base*, since March. This work is scheduled to be included in the next releases 1.5 and 2.0. Porting Scipy to work on Python 3 has proved to be much less work, and will probably be finished soon. (Ongoing work is here: http:// github.com/cournape/scipy3/commits/py3k , http://github.com/pv/scipy-work/ commits/py3k ) Thanks, Jason -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
Re: [sage-devel] Re: Bug or feature - questoin about databindings
On 07/10/10 07:41 PM, Jason Grout wrote: On 7/10/10 6:04 AM, William Stein wrote: Eventually, Sage will switch to Python 3.x. Things are accelerating. On the numpy/scipy list from today: We could accelerate them even more, by using the -3 flag, and identifying what bits of the Sage library will not work (warnings are issued). Gradually work over time to remove them, and ensure any added code does not contain warnings. Currently, I suspect some new code added to the library will not be compatible - that seems an undesirable situation to let continue. It would be desirable to put an immediate stop to adding code incompatible with Python 3. Dave -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
Re: [sage-devel] Re: Bug or feature - questoin about databindings
On 07/10/10 07:41 PM, Jason Grout wrote: On 7/10/10 6:04 AM, William Stein wrote: Eventually, Sage will switch to Python 3.x. Things are accelerating. On the numpy/scipy list from today: We could accelerate them even more, by using the -3 flag, and identifying what bits of the Sage library will not work (warnings are issued). Gradually work over time to remove them, and ensure any added code does not contain warnings. Currently, I suspect some new code added to the library will not be compatible - that seems an undesirable situation to let continue. It would be desirable to put an immediate stop to adding code that's incompatible with Python 3. Dave -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
