Hello,
Being somewhat pessimistic, I would say that chances are very small that
sage will be fully python3 compliant by then. For the moment, only 2 or 3
people are actively working on the problem. Erik and Jeroen have apparently
turned their attention to other important matters. There remains on the one
hand many small annoying issues to be taken care of one by one, and on the
other some difficult large-scale issues ("round,ceil,floor in python
semantics" and "graphs sort their vertices" and "modular symbols with
another basis" to just name 3).
What we should do is just go on, and then sage will be as much compatible
as we could. As I already said somewhere, help is welcome.
Frederic
Le lundi 5 novembre 2018 20:12:13 UTC+1, David Roe a écrit :
>
>
>
> On Mon, Nov 5, 2018 at 7:02 AM Samuel Lelièvre <samuel....@gmail.com
> <javascript:>> wrote:
>
>> Dear sage-devel,
>>
>> The freeze period for the next Debian release starts on
>> 12 January 2019, as discussed at
>>
>> https://trac.sagemath.org/ticket/22626#comment:118
>>
>> This conditions what functionality users of Debian and its
>> derivatives (including Ubuntu) will find in Sage for the next
>> two years, if they install from their distribution's package
>> manager.
>>
>> It might make sense for Sage developers to brainstorm on
>> priorities for what needs to be integrated by then.
>>
>> One priority is definitely making progress on updating GAP,
>> either using GAP 4.10 which should be announced any day
>> now and will provide its own LibGAP, or working on our own
>> libGAP based on GAP 4.9.3. Failing that, Sage might end up
>> *not being in the next Debian release at all*, if I understand
>> correctly. That would be a shame, given the number of users
>> of Debian and its derivatives (including Ubuntu).
>>
>> Can you think of other things that should be given high priority?
>>
>
> Another obvious thing is the switch to Python 3, which seems to have been
> making good progress. Perhaps we could have some work sessions on Zulip
> focused on Python 3? Frederic, how feasible would it be to finish the
> transition by mid January if you got some help? I'm happy to work on it
> more than I have been.
> David
>
>
>> Volker, could you give a provisional timeline for the upcoming
>> Sage release? Having a provisional timeline at the start of the
>> release cycle, and an update to this provisional timeline near
>> the end of the release cycle, is helpful for prioritising and for
>> synchronising the Sage-Windows release.
>>
>> Kind regards,
>> Samuel
>>
>> --
>> 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 sage-devel+...@googlegroups.com <javascript:>.
>> To post to this group, send email to sage-...@googlegroups.com
>> <javascript:>.
>> Visit this group at https://groups.google.com/group/sage-devel.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
--
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 sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.
