Skip to content
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

Python3 : Test ticket for range() #16081

Closed
wluebbe mannequin opened this issue Apr 7, 2014 · 23 comments
Closed

Python3 : Test ticket for range() #16081

wluebbe mannequin opened this issue Apr 7, 2014 · 23 comments

Comments

@wluebbe
Copy link
Mannequin

wluebbe mannequin commented Apr 7, 2014

This ticket is used for doctesting the Python 3 compatibility of range(). It is not a real ticket and should not be merged.

Python 3 preparation: "xrange()" is gone and "range()" becomes an iterator

The tool 2to3 renames xrange() to range() and wraps existing range() usages with list().

But the code has to depend on the Python version!

There are 293 effected modules.

This ticket is tracked as a dependency of meta-ticket ticket:16052.

Depends on #16457

Component: python3

Issue created by migration from https://trac.sagemath.org/ticket/16081

@wluebbe wluebbe mannequin added this to the sage-6.2 milestone Apr 7, 2014
@wluebbe wluebbe mannequin added c: distribution and removed t: bug labels Apr 7, 2014
@sagetrac-vbraun-spam sagetrac-vbraun-spam mannequin modified the milestones: sage-6.2, sage-6.3 May 6, 2014
@a-andre
Copy link

a-andre commented Jun 7, 2014

Dependencies: #16457

@a-andre
Copy link

a-andre commented Jun 7, 2014

comment:3

I moved most of the renaming part to #16457.

@sagetrac-vbraun-spam sagetrac-vbraun-spam mannequin modified the milestones: sage-6.3, sage-6.4 Aug 10, 2014
@fchapoton
Copy link
Contributor

comment:6

see #21375 for a step in this direction

@fchapoton
Copy link
Contributor

comment:7

see #21460 for another small step

@fchapoton fchapoton modified the milestones: sage-6.4, sage-7.4 Sep 21, 2016
@fchapoton
Copy link
Contributor

comment:9

see #21677 for another step

@fchapoton
Copy link
Contributor

comment:12

sorry, I did a wrong move here, this is probably not yet ready to be closed

@fchapoton fchapoton added this to the sage-7.6 milestone Jan 17, 2017
@fchapoton
Copy link
Contributor

Branch: u/chapoton/test_branch_for_range

@fchapoton
Copy link
Contributor

Commit: 505ce41

@fchapoton
Copy link
Contributor

comment:13

here is a branch, NOT TO BE MERGED, to let the patchbots run and detect remaining problems


New commits:

505ce41py3 : test branch for range !!! DO NOT MERGE !!!

@fchapoton
Copy link
Contributor

comment:19

next iteration in #22779

@fchapoton
Copy link
Contributor

comment:20

next step in #22816

@fchapoton
Copy link
Contributor

comment:21

next step in #22972

@Etn40ff
Copy link
Contributor

Etn40ff commented May 31, 2017

comment:22

Matrices here #23107

@fchapoton
Copy link
Contributor

comment:23

I have just run the patchbot. There is still a lot of things to be done here.

@fchapoton
Copy link
Contributor

comment:24

next in #24249

@fchapoton
Copy link
Contributor

comment:25

next step in #24569

@embray
Copy link
Contributor

embray commented Feb 23, 2018

comment:26

Going ahead and closing (unless you disagree) since it's not a real change to commit. There aren't too many range-related issues remaining (and those that do remain are mostly in classes/functions that should accept range objects as arguments but currently don't).

@fchapoton
Copy link
Contributor

Changed commit from 505ce41 to none

@fchapoton
Copy link
Contributor

Changed branch from u/chapoton/test_branch_for_range to none

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants