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

Move RecursivelyEnumeratedSet_forest code to sage/sets/recursively_enumerated_set.pyx, remove deprecated classes SearchForest, TransitiveIdeal, TransitiveIdealGraded #16351

Closed
seblabbe opened this issue May 13, 2014 · 40 comments

Comments

@seblabbe
Copy link
Contributor

Move the code of SearchForest from sage/combinat/backtrack.py to sage/sets/recursively_enumerated_set.pyx into a class named RecursivelyEnumeratedSet_forest.

This is a follow up of #6637.

CC: @tscrim @slel

Component: combinatorics

Author: Matthias Koeppe

Branch: 908acba

Reviewer: Vincent Delecroix

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

@seblabbe seblabbe added this to the sage-6.3 milestone May 13, 2014
@sagetrac-vbraun-spam sagetrac-vbraun-spam mannequin modified the milestones: sage-6.3, sage-6.4 Aug 10, 2014
@hivert
Copy link

hivert commented Dec 14, 2015

@hivert
Copy link

hivert commented Dec 14, 2015

Commit: 2effaf7

@hivert
Copy link

hivert commented Dec 14, 2015

comment:3

I just added some old doc from Nathann and myself which is worth being integrated when cleaning this up.


Last 10 new commits:

7a33037Work in progress on the DOC
168ceaeAdded architecture picture for map_reduce
366fc17More Doc
6c12752Tested timeout option
493bb52Done the doc of Map/Reduce
2534f12Moved map/reduce to sage/parallel
e5b7477Merge 6.10.rc1 + fixed conflict
82fd1e4Fixed links according to deprecation/rebase
68b6530Removed TODO in doc
2effaf7Revert "Removed TODO in doc"

@tscrim
Copy link
Collaborator

tscrim commented Jan 2, 2016

Dependencies: #13580

@tscrim
Copy link
Collaborator

tscrim commented Jan 2, 2016

comment:4

I would like to squeeze out some more speed of the SearchForest code, so I'm interested in this. I made #13580 a dependency since that is likely a lot closer than this is to getting into Sage. If you disagree, then we can reverse the order of the dependencies and I'd do the review once this is ready.

@tscrim tscrim modified the milestones: sage-6.4, sage-7.0 Jan 2, 2016
@seblabbe
Copy link
Contributor Author

seblabbe commented Apr 8, 2016

comment:5

The actual branch contains many commits from the #13580, so I can't see what is the goal of the branch put here and how it is related to this ticket.

@sagetrac-git
Copy link
Mannequin

sagetrac-git mannequin commented Apr 8, 2016

Changed commit from 2effaf7 to 1bf8c97

@sagetrac-git
Copy link
Mannequin

sagetrac-git mannequin commented Apr 8, 2016

Branch pushed to git repo; I updated commit sha1. Last 10 new commits:

f984165Fixed the doc
a5f4d67Improved doc for map-reduce
569de0dMerge branch 'develop' into t/13580/map_reduce
b07dfe2Doc of the two implementationsof ActiveTaskCounter
beebcbc#13580: Added comment on timing in the doc
58eca2e#13580: Removed comment which is now in the doc
1badd8a#13580: Renamed ActiveTaskCounter(Posix)
46cbab913580: Fixed doctests to pass on Darwin
134c1fa13580: doc rereading
1bf8c97Merge branch 'u/hivert/move_searchforest_code_to_sage_sets_recursively_enumerated_set_pyx' of git://trac.sagemath.org/sage into t/13580/map_reduce

@hivert
Copy link

hivert commented Apr 8, 2016

comment:7

Replying to @seblabbe:

The actual branch contains many commits from the #13580, so I can't see what is the goal of the branch put here and how it is related to this ticket.

I just rebased this ticket on top of #13580 the code contains only an explanation of what SearchForest does with a nice picture from Nathann, Nicolas and nyself. It should be integrated during the move and the documentation cleanup.

@tscrim
Copy link
Collaborator

tscrim commented Apr 8, 2016

comment:8

Something else that we should do while-we-are-at-it, we should consider using collections.deque since it supports fast popping from both ends (list can become really slow when popping at the front, but deque is still twice as slow popping at the front).

@nthiery
Copy link
Contributor

nthiery commented Jan 13, 2017

comment:9

Now that #13580 is in, the current branch contains just a small
self-contained documentation improvement. It seems worth and easy to
integrate soon, but somehow unrelated to this ticket, right?

Shall we create a separate ticket for that documentation chunk?

And refocus this one on moving the SearchForest code to
sage/sets/recursively_enumerated_set.pyx (more than by just a single
alias)?

@seblabbe
Copy link
Contributor Author

comment:10

Replying to @nthiery:

Now that #13580 is in, the current branch contains just a small
self-contained documentation improvement. It seems worth and easy to
integrate soon, but somehow unrelated to this ticket, right?

Shall we create a separate ticket for that documentation chunk?

Please yes.

And refocus this one on moving the SearchForest code to
sage/sets/recursively_enumerated_set.pyx (more than by just a single
alias)?

Yes.

@mkoeppe mkoeppe modified the milestones: sage-7.0, sage-9.2 Jun 17, 2020
@mkoeppe
Copy link
Member

mkoeppe commented Jun 17, 2020

comment:12

Replying to @seblabbe:

Replying to @nthiery:

Now that #13580 is in, the current branch contains just a small
self-contained documentation improvement. It seems worth and easy to
integrate soon, but somehow unrelated to this ticket, right?

Shall we create a separate ticket for that documentation chunk?

Please yes.

This is now #29882.

@mkoeppe
Copy link
Member

mkoeppe commented Jun 17, 2020

Changed commit from 1bf8c97 to none

@mkoeppe
Copy link
Member

mkoeppe commented Jun 17, 2020

@mkoeppe
Copy link
Member

mkoeppe commented Jun 17, 2020

Changed dependencies from #13580 to none

@mkoeppe
Copy link
Member

mkoeppe commented Jun 17, 2020

@mkoeppe
Copy link
Member

mkoeppe commented Jun 17, 2020

comment:15

Moved it, now need to clean up some lazy_import business


New commits:

7e1c6d2WIP
143604dWIP: Move SearchForest code to sage/sets/recursively_enumerated_set.pyx

@mkoeppe
Copy link
Member

mkoeppe commented Jun 17, 2020

Commit: 143604d

@sagetrac-git
Copy link
Mannequin

sagetrac-git mannequin commented Jun 17, 2020

Branch pushed to git repo; I updated commit sha1. This was a forced push. New commits:

364d7b3Move SearchForest code to sage/sets/recursively_enumerated_set.pyx
68f7bd5sage.combinat.integer_vectors_mod_permgroup: Update to use RecursivelyEnumeratedSet_forest
1764ca4Update remaining uses of SearchForest to use RecursivelyEnumeratedSet_forest

@mkoeppe
Copy link
Member

mkoeppe commented Jun 17, 2020

Author: Matthias Koeppe

@mkoeppe
Copy link
Member

mkoeppe commented Jun 17, 2020

comment:18

Also, I added a lazy_import for SearchForest but it seems that SearchForest was already deprecated -- perhaps now it can be removed completely?

@mkoeppe
Copy link
Member

mkoeppe commented Jun 17, 2020

comment:19

(deprecation in #6637, 6 years ago)

@sagetrac-git
Copy link
Mannequin

sagetrac-git mannequin commented Jun 17, 2020

Changed commit from 1764ca4 to 1ac0a09

@sagetrac-git
Copy link
Mannequin

sagetrac-git mannequin commented Jun 17, 2020

Branch pushed to git repo; I updated commit sha1. New commits:

1ac0a09sage.combinat.backtrack: Remove deprecated class SearchForest

@mkoeppe
Copy link
Member

mkoeppe commented Jun 17, 2020

comment:21

Also TransitiveIdeal and TransitiveIdealGraded were deprecated in #6637.

@sagetrac-git
Copy link
Mannequin

sagetrac-git mannequin commented Jun 17, 2020

Branch pushed to git repo; I updated commit sha1. New commits:

908acbasage.combinat.backtrack: Remove deprecated classes TransitiveIdeal and TransitiveIdealGraded

@sagetrac-git
Copy link
Mannequin

sagetrac-git mannequin commented Jun 17, 2020

Changed commit from 1ac0a09 to 908acba

@mkoeppe mkoeppe changed the title Move SearchForest code to sage/sets/recursively_enumerated_set.pyx Move RecursivelyEnumeratedSet_forest code to sage/sets/recursively_enumerated_set.pyx, removed deprecated classes SearchForest, TransitiveIdeal, TransitiveIdealGraded Jun 17, 2020
@videlec
Copy link
Contributor

videlec commented Jun 17, 2020

comment:24

It seems to me that with your changes SearchForest does not exist anymore. If so, you must add a lazy import with deprecation warning in backtrack.py. The SearchForest was documented as a deprecated class but was not making any deprecation warning when used.

@mkoeppe
Copy link
Member

mkoeppe commented Jun 17, 2020

comment:25

That's right, these deprecated classes are deleted.

The deprecation happened in #6637 and announced on the ticket, I guess before deprecation warnings were invented?

@videlec
Copy link
Contributor

videlec commented Jun 17, 2020

Reviewer: Vincent Delecroix

@videlec
Copy link
Contributor

videlec commented Jun 17, 2020

comment:26

This is somehow annoying. Let us hope that nobody uses it in her code.

@mkoeppe
Copy link
Member

mkoeppe commented Jun 17, 2020

comment:27

Thanks!

@slel slel changed the title Move RecursivelyEnumeratedSet_forest code to sage/sets/recursively_enumerated_set.pyx, removed deprecated classes SearchForest, TransitiveIdeal, TransitiveIdealGraded Move RecursivelyEnumeratedSet_forest code to sage/sets/recursively_enumerated_set.pyx, remove deprecated classes SearchForest, TransitiveIdeal, TransitiveIdealGraded Jun 18, 2020
@slel
Copy link
Member

slel commented Jun 18, 2020

comment:29

In the same general area, any interest in #22184 and #27537 anyone?

@vbraun
Copy link
Member

vbraun commented Jun 22, 2020

@seblabbe
Copy link
Contributor Author

comment:31

Thanks for finishing this task.I feel ashame I never finished it myself.

As a further todo, I think it will be nice to have

-class RecursivelyEnumeratedSet_forest(Parent):
+class RecursivelyEnumeratedSet_forest(RecursivelyEnumeratedSet_generic):

There are few methods like to_digraph from the generic class that I like to use but are currently not available for the forest type.

@seblabbe
Copy link
Contributor Author

Changed commit from 908acba to none

@seblabbe
Copy link
Contributor Author

comment:32

A follow-up ticket is here: #30238

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

8 participants