-
-
Notifications
You must be signed in to change notification settings - Fork 491
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[reported upstream] Bug in python range #1159
Comments
comment:1
|
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
comment:5
I can't find any issue with this. It works correctly for me in both the Python and Sage environments. |
comment:6
I get
On a 64-bit machine, try
I believe this is a bug in Python, and have reported it here: http://bugs.python.org/issue1533 |
Upstream: Reported upstream. Little or no feedback. |
comment:11
Fixed in upstream Python 2.6.6 / Python 2.7 (see issue 1533 linked to above) and fix will also be in Python 3 releases. This needs an upgrade of the Sage Python from 2.6.4 to 2.6.6. |
comment:12
Alternative fix to upgrade to Python 2.6.6 would be the upgrade to Python 2.7 from ticket #9958 |
comment:13
Fixed by #9958, when it gets merged (upgrade to python 2.7) |
Changed upstream from Reported upstream. Little or no feedback. to Fixed upstream, in a later stable release. |
Reviewer: Jason Grout |
Fixed by #9958.
Upstream: Fixed upstream, in a later stable release.
Component: packages: standard
Reviewer: Jason Grout
Issue created by migration from https://trac.sagemath.org/ticket/1159
The text was updated successfully, but these errors were encountered: