[sage-devel] Re: zn_poly status?

2018-09-07 Thread Antonio Rojas


El viernes, 7 de septiembre de 2018, 15:53:43 (UTC+2), Erik Bray escribió:
>
> Hi all, 
>
> Does anyone know what that current status is of the upstream zn_poly 
> package?  According to its website 
> http://cims.nyu.edu/~harvey/zn_poly/ it is "no longer maintained", 
> though it has been re-released under a BSD-compatible license. 
>
>
Given that the library has been unmaintained for years, has someone looked 
into whether its functionality can be provided by some other library 
nowadays? 

-- 
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.


Re: [sage-devel] zn_poly status?

2018-09-07 Thread Erik Bray
On Fri, Sep 7, 2018 at 6:59 PM Timo Kaufmann  wrote:
>
> Great! Please let us know on sage-packaging once you put out a new release 
> and switch sage over.

Yes, definitely.  I will also update the relevant SPKG.txt.

-- 
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.


Re: [sage-devel] zn_poly status?

2018-09-07 Thread Timo Kaufmann
Great! Please let us know on sage-packaging once you put out a new release 
and switch sage over.

-- 
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.


Re: [sage-devel] zn_poly status?

2018-09-07 Thread Erik Bray
On Fri, Sep 7, 2018 at 4:13 PM David Roe  wrote:
>
> I've CCed David Harvey, but I think that creating a github repo for it sounds 
> great.
> David

Thanks!  Pending some response from David Harvey, I've just gone ahead
and done it:

https://gitlab.com/sagemath/zn_poly

All previous releases of zn_poly can be found in the repository's
tags.  I've gone ahead and incorporated all the existing patches from
Sage, the patch I need for Cygwin, and a couple other small patches
for now.

Will also add some documentation updates a bit later if and when a
release is made from this repository.



> On Fri, Sep 7, 2018 at 9:53 AM Erik Bray  wrote:
>>
>> Hi all,
>>
>> Does anyone know what that current status is of the upstream zn_poly
>> package?  According to its website
>> http://cims.nyu.edu/~harvey/zn_poly/ it is "no longer maintained",
>> though it has been re-released under a BSD-compatible license.
>>
>> Since its last upstream release the package for it in Sage has
>> accumulated a number of patches as well, and I believe I may need to
>> add one more patch to it for building properly on Cygwin :(  See
>> https://trac.sagemath.org/ticket/26050
>>
>> If it's alright, I would propose creating a new repository for it
>> under the sagemath gitlab organization (or GitHub) which would become
>> the new "upstream" for zn_poly.  Then we can merge in all these
>> patches; maybe even implement a new, more standard build system (I
>> would be happy to do this).  In fact the current "build system" is
>> going to have problems long-term, as it currently consists primarily
>> of a Python script that will not work, as written, on Python 3.
>>
>> --
>> 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.
>
> --
> 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.

-- 
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.


Re: [sage-devel] Re: zn_poly status?

2018-09-07 Thread Erik Bray
On Fri, Sep 7, 2018 at 6:27 PM Timo Kaufmann  wrote:
>
>
>
> Am Freitag, 7. September 2018 17:56:04 UTC+2 schrieb Erik Bray:
>>
>> On Fri, Sep 7, 2018 at 5:29 PM Timo Kaufmann  wrote:
>> >
>> > For what its worth, we currently don't apply any patches in nix and at 
>> > least the sage doctests pass. A more standard build would still be nice 
>> > though.  And since upstream is officially dead, I think giving it a new 
>> > home would be very good. +1 from me.
>>
>> Most of the patches are build-related and test-related fixes, many of
>> which seem to stem from issues on OSX.
>
>
> We build it on OSX too. We only run `make check` though, not `make test`. I 
> can't verify if that would pass on darwin since I don't own a mac.

Well, a lot of these patches are pretty old too.  Who knows if they're
still really relevant.  Most of them seem harmless enough so I've gone
ahead and applied them.  I also applied the patches I need to build
correctly on Cygwin.

A bit later I will work on autotoolizing it, but in the short term I
might go ahead and make a release based on the patches applied above,
as I really need it for the Cygwin fixes which are a release blocker.


>>
>>
>>
>> > Am Freitag, 7. September 2018 15:53:43 UTC+2 schrieb Erik Bray:
>> >>
>> >> Hi all,
>> >>
>> >> Does anyone know what that current status is of the upstream zn_poly
>> >> package?  According to its website
>> >> http://cims.nyu.edu/~harvey/zn_poly/ it is "no longer maintained",
>> >> though it has been re-released under a BSD-compatible license.
>> >>
>> >> Since its last upstream release the package for it in Sage has
>> >> accumulated a number of patches as well, and I believe I may need to
>> >> add one more patch to it for building properly on Cygwin :(  See
>> >> https://trac.sagemath.org/ticket/26050
>> >>
>> >> If it's alright, I would propose creating a new repository for it
>> >> under the sagemath gitlab organization (or GitHub) which would become
>> >> the new "upstream" for zn_poly.  Then we can merge in all these
>> >> patches; maybe even implement a new, more standard build system (I
>> >> would be happy to do this).  In fact the current "build system" is
>> >> going to have problems long-term, as it currently consists primarily
>> >> of a Python script that will not work, as written, on Python 3.
>> >
>> > --
>> > 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.
>> > To post to this group, send email to sage-...@googlegroups.com.
>> > 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.

-- 
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.


Re: [sage-devel] Re: zn_poly status?

2018-09-07 Thread Timo Kaufmann


Am Freitag, 7. September 2018 17:56:04 UTC+2 schrieb Erik Bray:
>
> On Fri, Sep 7, 2018 at 5:29 PM Timo Kaufmann  > wrote: 
> > 
> > For what its worth, we currently don't apply any patches in nix and at 
> least the sage doctests pass. A more standard build would still be nice 
> though.  And since upstream is officially dead, I think giving it a new 
> home would be very good. +1 from me. 
>
> Most of the patches are build-related and test-related fixes, many of 
> which seem to stem from issues on OSX. 
>

We build it on OSX too. We only run `make check` though, not `make test`. I 
can't verify if that would pass on darwin since I don't own a mac. 

>
>
> > Am Freitag, 7. September 2018 15:53:43 UTC+2 schrieb Erik Bray: 
> >> 
> >> Hi all, 
> >> 
> >> Does anyone know what that current status is of the upstream zn_poly 
> >> package?  According to its website 
> >> http://cims.nyu.edu/~harvey/zn_poly/ it is "no longer maintained", 
> >> though it has been re-released under a BSD-compatible license. 
> >> 
> >> Since its last upstream release the package for it in Sage has 
> >> accumulated a number of patches as well, and I believe I may need to 
> >> add one more patch to it for building properly on Cygwin :(  See 
> >> https://trac.sagemath.org/ticket/26050 
> >> 
> >> If it's alright, I would propose creating a new repository for it 
> >> under the sagemath gitlab organization (or GitHub) which would become 
> >> the new "upstream" for zn_poly.  Then we can merge in all these 
> >> patches; maybe even implement a new, more standard build system (I 
> >> would be happy to do this).  In fact the current "build system" is 
> >> going to have problems long-term, as it currently consists primarily 
> >> of a Python script that will not work, as written, on Python 3. 
> > 
> > -- 
> > 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 . 
> > To post to this group, send email to sage-...@googlegroups.com 
> . 
> > 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.


Re: [sage-devel] Re: zn_poly status?

2018-09-07 Thread Erik Bray
On Fri, Sep 7, 2018 at 5:29 PM Timo Kaufmann  wrote:
>
> For what its worth, we currently don't apply any patches in nix and at least 
> the sage doctests pass. A more standard build would still be nice though.  
> And since upstream is officially dead, I think giving it a new home would be 
> very good. +1 from me.

Most of the patches are build-related and test-related fixes, many of
which seem to stem from issues on OSX.


> Am Freitag, 7. September 2018 15:53:43 UTC+2 schrieb Erik Bray:
>>
>> Hi all,
>>
>> Does anyone know what that current status is of the upstream zn_poly
>> package?  According to its website
>> http://cims.nyu.edu/~harvey/zn_poly/ it is "no longer maintained",
>> though it has been re-released under a BSD-compatible license.
>>
>> Since its last upstream release the package for it in Sage has
>> accumulated a number of patches as well, and I believe I may need to
>> add one more patch to it for building properly on Cygwin :(  See
>> https://trac.sagemath.org/ticket/26050
>>
>> If it's alright, I would propose creating a new repository for it
>> under the sagemath gitlab organization (or GitHub) which would become
>> the new "upstream" for zn_poly.  Then we can merge in all these
>> patches; maybe even implement a new, more standard build system (I
>> would be happy to do this).  In fact the current "build system" is
>> going to have problems long-term, as it currently consists primarily
>> of a Python script that will not work, as written, on Python 3.
>
> --
> 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.

-- 
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.


[sage-devel] Re: zn_poly status?

2018-09-07 Thread Timo Kaufmann
For what its worth, we currently don't apply any patches in nix and at 
least the sage doctests pass. A more standard build would still be nice 
though.  And since upstream is officially dead, I think giving it a new 
home would be very good. +1 from me.

Am Freitag, 7. September 2018 15:53:43 UTC+2 schrieb Erik Bray:
>
> Hi all, 
>
> Does anyone know what that current status is of the upstream zn_poly 
> package?  According to its website 
> http://cims.nyu.edu/~harvey/zn_poly/ it is "no longer maintained", 
> though it has been re-released under a BSD-compatible license. 
>
> Since its last upstream release the package for it in Sage has 
> accumulated a number of patches as well, and I believe I may need to 
> add one more patch to it for building properly on Cygwin :(  See 
> https://trac.sagemath.org/ticket/26050 
>
> If it's alright, I would propose creating a new repository for it 
> under the sagemath gitlab organization (or GitHub) which would become 
> the new "upstream" for zn_poly.  Then we can merge in all these 
> patches; maybe even implement a new, more standard build system (I 
> would be happy to do this).  In fact the current "build system" is 
> going to have problems long-term, as it currently consists primarily 
> of a Python script that will not work, as written, on Python 3. 
>

-- 
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.


Re: [sage-devel] Discussion about Sage packaging status

2018-09-07 Thread William Stein
On Fri, Sep 7, 2018 at 5:04 AM, Samuel Lelièvre
 wrote:
> Dear sage-devel,
>
> A tentative "status of Sage packaging and distribution" posted on the
> sage-packaging mailing list is resulting in an interesting discussion at:
>
> https://groups.google.com/d/topic/sage-packaging/ZJmJZi1Tawo/discussion
>
> Pointing to it here so that anybody interested in the subject can join
> that mailing list if they haven't yet, or just follow the discussion.

Thanks for posting.  I didn't even know about the sage-packaging mailing list!

William

>
> 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+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.



-- 
William (http://wstein.org)

-- 
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.


Re: [sage-devel] zn_poly status?

2018-09-07 Thread Vincent Delecroix

gitlab sounds even better :-)

Le 07/09/2018 à 10:13, David Roe a écrit :

I've CCed David Harvey, but I think that creating a github repo for it
sounds great.
David

On Fri, Sep 7, 2018 at 9:53 AM Erik Bray  wrote:


Hi all,

Does anyone know what that current status is of the upstream zn_poly
package?  According to its website
http://cims.nyu.edu/~harvey/zn_poly/ it is "no longer maintained",
though it has been re-released under a BSD-compatible license.

Since its last upstream release the package for it in Sage has
accumulated a number of patches as well, and I believe I may need to
add one more patch to it for building properly on Cygwin :(  See
https://trac.sagemath.org/ticket/26050

If it's alright, I would propose creating a new repository for it
under the sagemath gitlab organization (or GitHub) which would become
the new "upstream" for zn_poly.  Then we can merge in all these
patches; maybe even implement a new, more standard build system (I
would be happy to do this).  In fact the current "build system" is
going to have problems long-term, as it currently consists primarily
of a Python script that will not work, as written, on Python 3.

--
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.





--
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.


Re: [sage-devel] zn_poly status?

2018-09-07 Thread David Roe
I've CCed David Harvey, but I think that creating a github repo for it
sounds great.
David

On Fri, Sep 7, 2018 at 9:53 AM Erik Bray  wrote:

> Hi all,
>
> Does anyone know what that current status is of the upstream zn_poly
> package?  According to its website
> http://cims.nyu.edu/~harvey/zn_poly/ it is "no longer maintained",
> though it has been re-released under a BSD-compatible license.
>
> Since its last upstream release the package for it in Sage has
> accumulated a number of patches as well, and I believe I may need to
> add one more patch to it for building properly on Cygwin :(  See
> https://trac.sagemath.org/ticket/26050
>
> If it's alright, I would propose creating a new repository for it
> under the sagemath gitlab organization (or GitHub) which would become
> the new "upstream" for zn_poly.  Then we can merge in all these
> patches; maybe even implement a new, more standard build system (I
> would be happy to do this).  In fact the current "build system" is
> going to have problems long-term, as it currently consists primarily
> of a Python script that will not work, as written, on Python 3.
>
> --
> 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.
>

-- 
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.


[sage-devel] zn_poly status?

2018-09-07 Thread Erik Bray
Hi all,

Does anyone know what that current status is of the upstream zn_poly
package?  According to its website
http://cims.nyu.edu/~harvey/zn_poly/ it is "no longer maintained",
though it has been re-released under a BSD-compatible license.

Since its last upstream release the package for it in Sage has
accumulated a number of patches as well, and I believe I may need to
add one more patch to it for building properly on Cygwin :(  See
https://trac.sagemath.org/ticket/26050

If it's alright, I would propose creating a new repository for it
under the sagemath gitlab organization (or GitHub) which would become
the new "upstream" for zn_poly.  Then we can merge in all these
patches; maybe even implement a new, more standard build system (I
would be happy to do this).  In fact the current "build system" is
going to have problems long-term, as it currently consists primarily
of a Python script that will not work, as written, on Python 3.

-- 
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.


Re: [sage-devel] Re: Py3, sorting vertices of graph

2018-09-07 Thread Erik Bray
On Thu, Sep 6, 2018 at 11:40 AM David Coudert  wrote:
>
> Comparisons like u < v are used in many places in the code of graphs.
> We can try to use hash(u) < hash(v) instead, but this is certainly not the 
> smartest solution.

I have a long-outstanding proposal for a SafeSortable utility that
would help with these cases.  I would prefer a solution like this
(with the exact details negotiable):
https://trac.sagemath.org/ticket/25981

-- 
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.


[sage-devel] Discussion about Sage packaging status

2018-09-07 Thread Samuel Lelièvre
Dear sage-devel,

A tentative "status of Sage packaging and distribution" posted on the
sage-packaging mailing list is resulting in an interesting discussion at:

https://groups.google.com/d/topic/sage-packaging/ZJmJZi1Tawo/discussion

Pointing to it here so that anybody interested in the subject can join
that mailing list if they haven't yet, or just follow the discussion.

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+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.