Re: [sage-devel] Why is absolute_import a method of designs ?

2017-05-04 Thread Vincent Delecroix
On 04/05/2017 16:31, david.coud...@inria.fr wrote: So the problem is already addressed. solves the issue. Did you open a ticket? No. Thank you. #22948 needs review. Thank you. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe

Re: [sage-devel] Why is absolute_import a method of designs ?

2017-05-04 Thread David . Coudert
So the problem is already addressed. solves the issue. Did you open a ticket? > No. Thank you. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to

Re: [sage-devel] Why is absolute_import a method of designs ?

2017-05-04 Thread Vincent Delecroix
Indeed, {{{ --- a/src/sage/combinat/designs/design_catalog.py +++ b/src/sage/combinat/designs/design_catalog.py @@ -123,4 +123,4 @@ deprecated_callable_import(17034, ("This function will soon be removed. Use the designs.orthogonal_arrays.* functions instead")) #

Re: [sage-devel] Why is absolute_import a method of designs ?

2017-05-04 Thread Vincent Delecroix
I thought that this would not appear in tab completion. absolute_import comes from lines such as from __future__ import absolute_import that are aimed to simplify the transition to Python 3. You can see that it is everywhere sage: sage.combinat.ribbon_tableau.absolute_import

[sage-devel] Why is absolute_import a method of designs ?

2017-05-04 Thread David . Coudert
designs. shows absolute_import and we have sage: designs.absolute_import _Feature((2, 5, 0, 'alpha', 1), (3, 0, 0, 'alpha', 0), 16384) I don't understand what's going on. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from