Re: [sage-devel] Re: ssh fail
perhaps adding an invalid ssh key still breaks the communication between git server and trac... Can they still push changes to the git server? On Friday, July 1, 2016 at 12:35:55 AM UTC+1, Viviane Pons wrote: > > Hi, > > I'm with two new sage git users: eviatarbach and avenrias and they seem to > have a similar problem. They have put their ssh key on trac (I've checked), > but it keeps saying "Permission denied (publickey)" when they try > > ssh -T g...@trac.sagemath.org info > > Here is what they get: > > OpenSSH_7.2p2 Ubuntu-4ubuntu1, OpenSSL 1.0.2g-fips 1 Mar 2016 > debug1: Reading configuration data /etc/ssh/ssh_config > debug1: /etc/ssh/ssh_config line 19: Applying options for * > debug1: Connecting to trac.sagemath.org [104.197.143.230] port 22. > debug1: Connection established. > debug1: identity file /home/eviatar/.ssh/id_rsa type 1 > debug1: key_load_public: No such file or directory > debug1: identity file /home/eviatar/.ssh/id_rsa-cert type -1 > debug1: key_load_public: No such file or directory > debug1: identity file /home/eviatar/.ssh/id_dsa type -1 > debug1: key_load_public: No such file or directory > debug1: identity file /home/eviatar/.ssh/id_dsa-cert type -1 > debug1: key_load_public: No such file or directory > debug1: identity file /home/eviatar/.ssh/id_ecdsa type -1 > debug1: key_load_public: No such file or directory > debug1: identity file /home/eviatar/.ssh/id_ecdsa-cert type -1 > debug1: key_load_public: No such file or directory > debug1: identity file /home/eviatar/.ssh/id_ed25519 type -1 > debug1: key_load_public: No such file or directory > debug1: identity file /home/eviatar/.ssh/id_ed25519-cert type -1 > debug1: Enabling compatibility mode for protocol 2.0 > debug1: Local version string SSH-2.0-OpenSSH_7.2p2 Ubuntu-4ubuntu1 > debug1: Remote protocol version 2.0, remote software version > OpenSSH_6.6.1p1 Ubuntu-2ubuntu2.7 > debug1: match: OpenSSH_6.6.1p1 Ubuntu-2ubuntu2.7 pat OpenSSH_6.6.1* compat > 0x0400 > debug1: Authenticating to trac.sagemath.org:22 as 'git' > debug1: SSH2_MSG_KEXINIT sent > debug1: SSH2_MSG_KEXINIT received > debug1: kex: algorithm: curve255...@libssh.org > debug1: kex: host key algorithm: ecdsa-sha2-nistp256 > debug1: kex: server->client cipher: chacha20...@openssh.com > MAC: compression: none > debug1: kex: client->server cipher: chacha20...@openssh.com > MAC: compression: none > debug1: expecting SSH2_MSG_KEX_ECDH_REPLY > debug1: Server host key: ecdsa-sha2-nistp256 > SHA256:PLGYHWgGgFuDw+Xqa8TSHaJ9AZlcXIiaYUdlrNN1sFU > debug1: Host 'trac.sagemath.org' is known and matches the ECDSA host key. > debug1: Found key in /home/eviatar/.ssh/known_hosts:2 > debug1: rekey after 134217728 blocks > debug1: SSH2_MSG_NEWKEYS sent > debug1: expecting SSH2_MSG_NEWKEYS > debug1: rekey after 134217728 blocks > debug1: SSH2_MSG_NEWKEYS received > debug1: SSH2_MSG_SERVICE_ACCEPT received > debug1: Authentications that can continue: publickey > debug1: Next authentication method: publickey > debug1: Offering RSA public key: /home/eviatar/.ssh/id_rsa > debug1: Authentications that can continue: publickey > debug1: Trying private key: /home/eviatar/.ssh/id_dsa > debug1: Trying private key: /home/eviatar/.ssh/id_ecdsa > debug1: Trying private key: /home/eviatar/.ssh/id_ed25519 > debug1: No more authentication methods to try. > > > > 2016-06-29 3:56 GMT-07:00 tara fife >: > >> Thanks everyone, I am able to push changes to trac now. >> >> Tara >> >> -- >> 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.
[sage-devel] Re: trac mails are back on
Just got this error when saving changes to #18889: closeWarning: The change has been saved, but an error occurred while sending notifications: expected string or buffer Important? -- 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: ssh fail
Hi, I'm with two new sage git users: eviatarbach and avenrias and they seem to have a similar problem. They have put their ssh key on trac (I've checked), but it keeps saying "Permission denied (publickey)" when they try ssh -T g...@trac.sagemath.org info Here is what they get: OpenSSH_7.2p2 Ubuntu-4ubuntu1, OpenSSL 1.0.2g-fips 1 Mar 2016 debug1: Reading configuration data /etc/ssh/ssh_config debug1: /etc/ssh/ssh_config line 19: Applying options for * debug1: Connecting to trac.sagemath.org [104.197.143.230] port 22. debug1: Connection established. debug1: identity file /home/eviatar/.ssh/id_rsa type 1 debug1: key_load_public: No such file or directory debug1: identity file /home/eviatar/.ssh/id_rsa-cert type -1 debug1: key_load_public: No such file or directory debug1: identity file /home/eviatar/.ssh/id_dsa type -1 debug1: key_load_public: No such file or directory debug1: identity file /home/eviatar/.ssh/id_dsa-cert type -1 debug1: key_load_public: No such file or directory debug1: identity file /home/eviatar/.ssh/id_ecdsa type -1 debug1: key_load_public: No such file or directory debug1: identity file /home/eviatar/.ssh/id_ecdsa-cert type -1 debug1: key_load_public: No such file or directory debug1: identity file /home/eviatar/.ssh/id_ed25519 type -1 debug1: key_load_public: No such file or directory debug1: identity file /home/eviatar/.ssh/id_ed25519-cert type -1 debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_7.2p2 Ubuntu-4ubuntu1 debug1: Remote protocol version 2.0, remote software version OpenSSH_6.6.1p1 Ubuntu-2ubuntu2.7 debug1: match: OpenSSH_6.6.1p1 Ubuntu-2ubuntu2.7 pat OpenSSH_6.6.1* compat 0x0400 debug1: Authenticating to trac.sagemath.org:22 as 'git' debug1: SSH2_MSG_KEXINIT sent debug1: SSH2_MSG_KEXINIT received debug1: kex: algorithm: curve25519-sha...@libssh.org debug1: kex: host key algorithm: ecdsa-sha2-nistp256 debug1: kex: server->client cipher: chacha20-poly1...@openssh.com MAC: compression: none debug1: kex: client->server cipher: chacha20-poly1...@openssh.com MAC: compression: none debug1: expecting SSH2_MSG_KEX_ECDH_REPLY debug1: Server host key: ecdsa-sha2-nistp256 SHA256:PLGYHWgGgFuDw+Xqa8TSHaJ9AZlcXIiaYUdlrNN1sFU debug1: Host 'trac.sagemath.org' is known and matches the ECDSA host key. debug1: Found key in /home/eviatar/.ssh/known_hosts:2 debug1: rekey after 134217728 blocks debug1: SSH2_MSG_NEWKEYS sent debug1: expecting SSH2_MSG_NEWKEYS debug1: rekey after 134217728 blocks debug1: SSH2_MSG_NEWKEYS received debug1: SSH2_MSG_SERVICE_ACCEPT received debug1: Authentications that can continue: publickey debug1: Next authentication method: publickey debug1: Offering RSA public key: /home/eviatar/.ssh/id_rsa debug1: Authentications that can continue: publickey debug1: Trying private key: /home/eviatar/.ssh/id_dsa debug1: Trying private key: /home/eviatar/.ssh/id_ecdsa debug1: Trying private key: /home/eviatar/.ssh/id_ed25519 debug1: No more authentication methods to try. 2016-06-29 3:56 GMT-07:00 tara fife : > Thanks everyone, I am able to push changes to trac now. > > Tara > > -- > 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: Trac workflow and needs_review
On Thu, Jun 30, 2016 at 8:35 AM, Erik Bray wrote: > On Tue, Jun 28, 2016 at 7:14 PM, leif wrote: >> Erik Bray wrote: >>> While we're tinkering with the workflow, I think we need to change the >>> workflow associated with testing changes. >>> >>> Currently the release manager *closes* a ticket and marks it as >> >> s/currently the release manager/the current release manager/ ;-) > > Yes, but I didn't want to imply "fault" here or anything like that. > Volker does what's best for Volker and that's completely fine. > > The problem is that there aren't any documented procedures (that I > know of!) for how testing of issues, merging, and releases should be > handled. So the correct procedure *is* whatever the current release > manager does. That, I do have a problem with, though it's nobody's > fault. Erik, You are just begging to take a *turn* as release manager... Incidentally, when I stopped being release manager, after several years when I suddenly realized that I wasn't the only person in the world who could do it, we had rotating release managers for a while... which resulted in documenting workflows at the time.I don't want to speak for Volker [*], but I imagine he might enjoy taking a little break? - William [*] who is ridiculously good at release managing Sage, to put it mildly. Doing Sage release management is very, very difficult. -- 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] Re: spkgs assumed for doctesting but not default installed
Hi leif, > Well, it's apparently just that your toolchain isn't using binutils > consistently; usually LLVM's tools get installed as 'llvm-ar' and > 'llvm-ranlib', or they don't get installed into the default PATH. I don't have llvm-ar or llvm-ranlib installed AFAIK (they're in the package llvm which I don't have. I have llvm-libs, lib32-llvm-libs and clang, though. Also locate shows up nothing.). > You may try to reinstall binutils or create appropriate symlinks along > PATH (such that 'ar' and 'ranlib' originate from them), but I have no > idea whether that's at all related to your main problem. "pacman -Qo `which ar`" tells me binutils already owns the main ar (and ranlib). > P.S.: Downgrading GCC of course (in this case at least) also downgrades > libstdc++ (to 6.0.21), so programs and libraries built against the newer > one are borked. If the newer libstdc++ didn't get removed, it's > probably just a matter of symlinking libstdc++.so.6 back to the more > recent one, presumably libstdc++.so.6.0.22 (from GCC 6.1). Oh yeah, that probably explains why llvm expects a GLIBCXX which is not in my current /usr/lib/libstdc++.so.6. I've downgraded llvm and trying a "make distclean && make" again. Best, Johan -- 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: Trac workflow and needs_review
Erik Bray wrote: > On Tue, Jun 28, 2016 at 7:14 PM, leif wrote: >> Erik Bray wrote: >>> While we're tinkering with the workflow, I think we need to change the >>> workflow associated with testing changes. >>> >>> Currently the release manager *closes* a ticket and marks it as >> >> s/currently the release manager/the current release manager/ ;-) > > Yes, but I didn't want to imply "fault" here or anything like that. > Volker does what's best for Volker and that's completely fine. > > The problem is that there aren't any documented procedures (that I > know of!) for how testing of issues, merging, and releases should be > handled. So the correct procedure *is* whatever the current release > manager does. That, I do have a problem with, though it's nobody's > fault. Regarding the release process, there are some (fairly outdated) notes in the Sage wiki, but a lot is simply defined by the actual release manager(s) (and more or less tradition). In the past, the release managers (usually teams) changed more often, also because nobody volunteered (or had the time to do it) for a longer period. >>> "fixed" when merging the change for testing. This really makes no >>> sense--if the tests fail the issue is not "fixed". After >>> "positive_review" can we add a "in testing" status or the like (from >>> which the next stages can be either back to "needs_work" or >>> "resolved". >> >> We had at least one lengthy discussion regarding that in the past (last >> time probably a year ago? -- too lazy to search the thread[s] now, but >> they're certainly worth reading [again]). >> >> Nothing happened since then though, if I'm not mistaken. >> >> But note that the buildbots do test tickets having positive review, some >> also those with "needs review", so with relatively frequent "beta >> releases", it's not all that bad. > > I'm really confused about what the buildbots do or don't do. Or what > the relationship is between patchbot and buildbot (other than the > latter implying that someone is managing a bunch of buildbot instances > somewhere?) My mistake, tickets are automatically tested by our *patchbots*. The buildbots don't do anything by themselves (unless the release manager runs some cron job, say). They are used to test potential (beta/rc/final) releases before releasing, and to build binary distributions of Sage. All of the above testing of course makes up only a fraction of the review process though (hopefully, I mean). People should really read the code, diffs, comments by other reviewers on a ticket, and experiment interactively, otherwise we could automate setting tickets to "positive review" (and merging them) as well... B) IMHO there have been (and will be) /some/ tickets with good reasons to revert them from positive review back to "needs work" or "needs review" (despite their patches applying and their tests -- if any -- passing), i.e., where merging them as is and opening follow-ups (which in fact rarely happens, often not because it wasn't necessary) instead didn't make sense, hence 'in_testing' or whatever seems useful. But the main problem usually is time, namely the time for others to take a look and to eventually intervene between someone setting a ticket to positive review and the ticket getting "finally" merged (into the release managers' trunk). 'in_testing' or 'merge_candidate' could attract (or alert) more people to look at, but the impact of a change (beyond what files get touched -- we don't even have a tool to notify people based on that) also matters. Everyone is allowed to (attempt to) modify any part of Sage, while we don't all live in the same timezone, and most of us don't work full-time on Sage. -leif -- 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] Trac workflow and needs_review
On Tue, Jun 28, 2016 at 10:20 PM, Volker Braun wrote: > On Tuesday, June 28, 2016 at 6:23:18 PM UTC+2, Erik Bray wrote: >> >> Currently the release manager *closes* a ticket and marks it as >> "fixed" when merging the change for testing. > > > No. Tickets are closed *after* tests succeed. I'm just going by what Jeroen told me here: https://trac.sagemath.org/ticket/20423#comment:12 I feel like I've also seen a ticket of mine closed and reopened again for exactly this reason, unless that's changed. > The only race condition is if somebody else reopens positively reviewed > tickets whose tests pass. Arguably that shouldn't be done, since that ticket > is complete. There is always something else to do, just open a new ticket. > Instead of reopening an old ticket to pile on more commits. Agreed here. If it's closed+merged it should remain closed, unless it was just closed by accident. -- 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: Trac workflow and needs_review
On Tue, Jun 28, 2016 at 7:14 PM, leif wrote: > Erik Bray wrote: >> While we're tinkering with the workflow, I think we need to change the >> workflow associated with testing changes. >> >> Currently the release manager *closes* a ticket and marks it as > > s/currently the release manager/the current release manager/ ;-) Yes, but I didn't want to imply "fault" here or anything like that. Volker does what's best for Volker and that's completely fine. The problem is that there aren't any documented procedures (that I know of!) for how testing of issues, merging, and releases should be handled. So the correct procedure *is* whatever the current release manager does. That, I do have a problem with, though it's nobody's fault. >> "fixed" when merging the change for testing. This really makes no >> sense--if the tests fail the issue is not "fixed". After >> "positive_review" can we add a "in testing" status or the like (from >> which the next stages can be either back to "needs_work" or >> "resolved". > > We had at least one lengthy discussion regarding that in the past (last > time probably a year ago? -- too lazy to search the thread[s] now, but > they're certainly worth reading [again]). > > Nothing happened since then though, if I'm not mistaken. > > But note that the buildbots do test tickets having positive review, some > also those with "needs review", so with relatively frequent "beta > releases", it's not all that bad. I'm really confused about what the buildbots do or don't do. Or what the relationship is between patchbot and buildbot (other than the latter implying that someone is managing a bunch of buildbot instances somewhere?) -- 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] python3 again
On Thu, Jun 30, 2016 at 5:18 PM, Frédéric Chapoton wrote:
> I am doing things inside a virtualenv because I do not want to destroy my
> sage installation (which happened once or twice) by trying to make sage with
> python3.
>
> But if there is a better way, I am ready to listen. So far, despite my
> askings, nobody has told me "how to try to build sage using python3" and I
> had to figure things by myself.
I would just make a separate clone of the git repo and build in that
with Python 3 enabled, so you can mess with that all you want without
breaking the sage you use for work (which is what people should do in
general I think)
As things are I don't think it makes a lot of sense to do anything
with virtualenv.
> Le jeudi 30 juin 2016 17:13:13 UTC+2, Erik Bray a écrit :
>>
>> As I wrote in the ticket I'm not exactly sure what you're using a
>> virtualenv for.
>>
>> To be clear, I think it's great to use virtualenv for development in
>> general. But I think this will only confuse things when building
>> SAGE-THE-DISTRIBUTION from scratch since everything should get
>> installed into $SAGE_LOCAL.
>>
>> So I'm not sure what you're doing with a virtualenv or why.
>>
>> On Thu, Jun 30, 2016 at 3:29 PM, Frédéric Chapoton
>> wrote:
>> > Hello everybody,
>> >
>> > I am trying to build sage with python3 (I asked for help here before,
>> > but
>> > got only little).
>> >
>> > It fails, of course (see log below for "make build"). I would like to
>> > understand how.
>> >
>> > I am in a python3 virtualenv, and SAGE_ROOT/local/bin/python launches a
>> > python3
>> >
>> > This python3 complains that it cannot find pkg_resources, as follows
>> > (from
>> > the shell)
>> >
>> > ./local/bin/python -c 'import pkg_resources;
>> > pkg_resources.get_distribution("matplotlib").version'
>> > Traceback (most recent call last):
>> > File "", line 1, in
>> > ImportError: No module named 'pkg_resources'
>> >
>> > but instead it seems to pick the py2 pkg_resources, when called inside
>> > the
>> > sage-env script.
>> >
>> > Any idea ? By the way, please review
>> > https://trac.sagemath.org/ticket/20909
>> > and https://trac.sagemath.org/ticket/20910, which are needed to reach
>> > this
>> > point.
>> >
>> > Frederic
>> >
>> > sage-logger -p 'sage-spkg python2-2.7.10.p2'
>> > '/home/chapoton/sage3/logs/pkgs/python2-2.7.10.p2.log'
>> > [python2-2.7.10.p2] /home/chapoton/sage3/src/bin/sage-env: line 402:
>> > 24023
>> > Aborted (core dumped) "$SAGE_ROOT/local/bin/python" -c
>> > 'import pkg_resources;
>> > pkg_resources.get_distribution("matplotlib").version'
>> > 2> /dev/null
>> > [python2-2.7.10.p2] Found local metadata for python2-2.7.10.p2
>> > [python2-2.7.10.p2] Fatal Python error: Py_Initialize: Unable to get the
>> > locale encoding
>> > [python2-2.7.10.p2] File
>> > "/home/chapoton/sage3/local/lib/python/encodings/__init__.py", line 123
>> > [python2-2.7.10.p2] raise CodecRegistryError,\
>> > [python2-2.7.10.p2] ^
>> > [python2-2.7.10.p2] SyntaxError: invalid syntax
>> > [python2-2.7.10.p2]
>> > [python2-2.7.10.p2] Current thread 0x7f7b54334700 (most recent call
>> > first):
>> > [python2-2.7.10.p2] /home/chapoton/sage3/build/bin/sage-spkg: line 425:
>> > 24057 Aborted (core dumped) sage-download-file
>> > $PKG_NAME_UPSTREAM
>> > Makefile:2432 : la recette pour la cible «
>> > /home/chapoton/sage3/local/var/lib/sage/installed/python2-2.7.10.p2 » a
>> > échouée
>> >
>> > --
>> > 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.
[sage-devel] Re: python3 again
On Thursday, June 30, 2016 at 5:12:50 PM UTC+2, Frédéric Chapoton wrote: > > It is still not very clear to me what SAGE_PYTHON3 (well hidden) is > supposed to achieve. > When building Sage-the-distribution, it builds python3 instead of python2. Anything that uses Sage's own python will then be be using python3. And its a work in progress, as you know. -- 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] python3 again
I am doing things inside a virtualenv because I do not want to destroy my
sage installation (which happened once or twice) by trying to make sage
with python3.
But if there is a better way, I am ready to listen. So far, despite my
askings, nobody has told me "how to try to build sage using python3" and I
had to figure things by myself.
Frederic
Le jeudi 30 juin 2016 17:13:13 UTC+2, Erik Bray a écrit :
>
> As I wrote in the ticket I'm not exactly sure what you're using a
> virtualenv for.
>
> To be clear, I think it's great to use virtualenv for development in
> general. But I think this will only confuse things when building
> SAGE-THE-DISTRIBUTION from scratch since everything should get
> installed into $SAGE_LOCAL.
>
> So I'm not sure what you're doing with a virtualenv or why.
>
> On Thu, Jun 30, 2016 at 3:29 PM, Frédéric Chapoton > wrote:
> > Hello everybody,
> >
> > I am trying to build sage with python3 (I asked for help here before,
> but
> > got only little).
> >
> > It fails, of course (see log below for "make build"). I would like to
> > understand how.
> >
> > I am in a python3 virtualenv, and SAGE_ROOT/local/bin/python launches a
> > python3
> >
> > This python3 complains that it cannot find pkg_resources, as follows
> (from
> > the shell)
> >
> > ./local/bin/python -c 'import pkg_resources;
> > pkg_resources.get_distribution("matplotlib").version'
> > Traceback (most recent call last):
> > File "", line 1, in
> > ImportError: No module named 'pkg_resources'
> >
> > but instead it seems to pick the py2 pkg_resources, when called inside
> the
> > sage-env script.
> >
> > Any idea ? By the way, please review
> https://trac.sagemath.org/ticket/20909
> > and https://trac.sagemath.org/ticket/20910, which are needed to reach
> this
> > point.
> >
> > Frederic
> >
> > sage-logger -p 'sage-spkg python2-2.7.10.p2'
> > '/home/chapoton/sage3/logs/pkgs/python2-2.7.10.p2.log'
> > [python2-2.7.10.p2] /home/chapoton/sage3/src/bin/sage-env: line 402:
> 24023
> > Aborted (core dumped) "$SAGE_ROOT/local/bin/python" -c
> > 'import pkg_resources;
> pkg_resources.get_distribution("matplotlib").version'
> > 2> /dev/null
> > [python2-2.7.10.p2] Found local metadata for python2-2.7.10.p2
> > [python2-2.7.10.p2] Fatal Python error: Py_Initialize: Unable to get the
> > locale encoding
> > [python2-2.7.10.p2] File
> > "/home/chapoton/sage3/local/lib/python/encodings/__init__.py", line 123
> > [python2-2.7.10.p2] raise CodecRegistryError,\
> > [python2-2.7.10.p2] ^
> > [python2-2.7.10.p2] SyntaxError: invalid syntax
> > [python2-2.7.10.p2]
> > [python2-2.7.10.p2] Current thread 0x7f7b54334700 (most recent call
> > first):
> > [python2-2.7.10.p2] /home/chapoton/sage3/build/bin/sage-spkg: line 425:
> > 24057 Aborted (core dumped) sage-download-file
> > $PKG_NAME_UPSTREAM
> > Makefile:2432 : la recette pour la cible «
> > /home/chapoton/sage3/local/var/lib/sage/installed/python2-2.7.10.p2 » a
> > échouée
> >
> > --
> > 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] python3 again
As I wrote in the ticket I'm not exactly sure what you're using a
virtualenv for.
To be clear, I think it's great to use virtualenv for development in
general. But I think this will only confuse things when building
SAGE-THE-DISTRIBUTION from scratch since everything should get
installed into $SAGE_LOCAL.
So I'm not sure what you're doing with a virtualenv or why.
On Thu, Jun 30, 2016 at 3:29 PM, Frédéric Chapoton wrote:
> Hello everybody,
>
> I am trying to build sage with python3 (I asked for help here before, but
> got only little).
>
> It fails, of course (see log below for "make build"). I would like to
> understand how.
>
> I am in a python3 virtualenv, and SAGE_ROOT/local/bin/python launches a
> python3
>
> This python3 complains that it cannot find pkg_resources, as follows (from
> the shell)
>
> ./local/bin/python -c 'import pkg_resources;
> pkg_resources.get_distribution("matplotlib").version'
> Traceback (most recent call last):
> File "", line 1, in
> ImportError: No module named 'pkg_resources'
>
> but instead it seems to pick the py2 pkg_resources, when called inside the
> sage-env script.
>
> Any idea ? By the way, please review https://trac.sagemath.org/ticket/20909
> and https://trac.sagemath.org/ticket/20910, which are needed to reach this
> point.
>
> Frederic
>
> sage-logger -p 'sage-spkg python2-2.7.10.p2'
> '/home/chapoton/sage3/logs/pkgs/python2-2.7.10.p2.log'
> [python2-2.7.10.p2] /home/chapoton/sage3/src/bin/sage-env: line 402: 24023
> Aborted (core dumped) "$SAGE_ROOT/local/bin/python" -c
> 'import pkg_resources; pkg_resources.get_distribution("matplotlib").version'
> 2> /dev/null
> [python2-2.7.10.p2] Found local metadata for python2-2.7.10.p2
> [python2-2.7.10.p2] Fatal Python error: Py_Initialize: Unable to get the
> locale encoding
> [python2-2.7.10.p2] File
> "/home/chapoton/sage3/local/lib/python/encodings/__init__.py", line 123
> [python2-2.7.10.p2] raise CodecRegistryError,\
> [python2-2.7.10.p2] ^
> [python2-2.7.10.p2] SyntaxError: invalid syntax
> [python2-2.7.10.p2]
> [python2-2.7.10.p2] Current thread 0x7f7b54334700 (most recent call
> first):
> [python2-2.7.10.p2] /home/chapoton/sage3/build/bin/sage-spkg: line 425:
> 24057 Aborted (core dumped) sage-download-file
> $PKG_NAME_UPSTREAM
> Makefile:2432 : la recette pour la cible «
> /home/chapoton/sage3/local/var/lib/sage/installed/python2-2.7.10.p2 » a
> échouée
>
> --
> 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: python3 again
Thanks.
It is still not very clear to me what SAGE_PYTHON3 (well hidden) is
supposed to achieve. Am I right to say that if the code of sage and
all its dependencies would work with py3, "export SAGE_PYTHON3=yes" then
"make build" would build a py3 sage ?
I have made a ticket to document SAGE_PYTHON3, please have a look and
enhance it.
https://trac.sagemath.org/ticket/20912
Frederic
Le jeudi 30 juin 2016 16:25:22 UTC+2, Volker Braun a écrit :
>
> It wouldn't surprise me too much if you can' t build python2 inside a
> python 3 venv. Its pretty low on the priority of things to support imho.
> Try building with SAGE_PYTHON3=yes
>
>
>
> On Thursday, June 30, 2016 at 3:29:25 PM UTC+2, Frédéric Chapoton wrote:
>>
>> Hello everybody,
>>
>> I am trying to build sage with python3 (I asked for help here before, but
>> got only little).
>>
>> It fails, of course (see log below for "make build"). I would like to
>> understand how.
>>
>> I am in a python3 virtualenv, and SAGE_ROOT/local/bin/python launches a
>> python3
>>
>> This python3 complains that it cannot find pkg_resources, as follows
>> (from the shell)
>>
>> ./local/bin/python -c 'import pkg_resources;
>> pkg_resources.get_distribution("matplotlib").version'
>> Traceback (most recent call last):
>> File "", line 1, in
>> ImportError: No module named 'pkg_resources'
>>
>> but instead it seems to pick the py2 pkg_resources, when called inside
>> the sage-env script.
>>
>> Any idea ? By the way, please review
>> https://trac.sagemath.org/ticket/20909 and
>> https://trac.sagemath.org/ticket/20910, which are needed to reach this
>> point.
>>
>> Frederic
>>
>> sage-logger -p 'sage-spkg python2-2.7.10.p2'
>> '/home/chapoton/sage3/logs/pkgs/python2-2.7.10.p2.log'
>> [python2-2.7.10.p2] /home/chapoton/sage3/src/bin/sage-env: line 402:
>> 24023 Aborted (core dumped) "$SAGE_ROOT/local/bin/python"
>> -c 'import pkg_resources;
>> pkg_resources.get_distribution("matplotlib").version' 2> /dev/null
>> [python2-2.7.10.p2] Found local metadata for python2-2.7.10.p2
>> [python2-2.7.10.p2] Fatal Python error: Py_Initialize: Unable to get the
>> locale encoding
>> [python2-2.7.10.p2] File
>> "/home/chapoton/sage3/local/lib/python/encodings/__init__.py", line 123
>> [python2-2.7.10.p2] raise CodecRegistryError,\
>> [python2-2.7.10.p2] ^
>> [python2-2.7.10.p2] SyntaxError: invalid syntax
>> [python2-2.7.10.p2]
>> [python2-2.7.10.p2] Current thread 0x7f7b54334700 (most recent call
>> first):
>> [python2-2.7.10.p2] /home/chapoton/sage3/build/bin/sage-spkg: line 425:
>> 24057 Aborted (core dumped) sage-download-file
>> $PKG_NAME_UPSTREAM
>> Makefile:2432 : la recette pour la cible «
>> /home/chapoton/sage3/local/var/lib/sage/installed/python2-2.7.10.p2 » a
>> échouée
>>
>>
--
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: spkgs assumed for doctesting but not default installed
Johan S. H. Rosenkilde wrote: >>> ar: /usr/lib/libstdc++.so.6: version `GLIBCXX_3.4.22' not found (required >>> by /usr/lib/libLLVM-3.8.so) >> >> >> Are you using llvm? As far as I know that doesnt' work, though I haven't >> tried it myself. > > I was baffled about that too. I haven't consciously done anything that > would use llvm. I'm using a fully updated Arch linux, but with gcc > rolled back to 5.3. Then I just cloned the git repo and did 'make'. I > don't seem have any environment variables pointing to llvm either. Well, it's apparently just that your toolchain isn't using binutils consistently; usually LLVM's tools get installed as 'llvm-ar' and 'llvm-ranlib', or they don't get installed into the default PATH. You may try to reinstall binutils or create appropriate symlinks along PATH (such that 'ar' and 'ranlib' originate from them), but I have no idea whether that's at all related to your main problem. If 'ar' etc. fail but that error isn't catched that's of course a bug. -leif P.S.: Downgrading GCC of course (in this case at least) also downgrades libstdc++ (to 6.0.21), so programs and libraries built against the newer one are borked. If the newer libstdc++ didn't get removed, it's probably just a matter of symlinking libstdc++.so.6 back to the more recent one, presumably libstdc++.so.6.0.22 (from GCC 6.1). -- 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: Deprecation warnings are no longer printed?!
Hi, > sage: sage: f1(x) = -1 > sage: sage: f2(x) = 2 > sage: sage: f = Piecewise([[(0,pi/2),f1],[(pi/2,pi),f2]]) > /home/novoselt/sage/src/bin/sage-ipython:1: DeprecationWarning: use > lower-case piecewise instead > See http://trac.sagemath.org/14801 for details. > #!/usr/bin/env python Indeed that also works for me, and many other deprecation warnings. I should have tried that yesterday. I should explain that I'm working on a deprecation warning for the Matrix.I property. I'm baffled because the warning that I added seems to print sometimes and not other times. Consider for instance, the following code run in the Sage shell, after applying #20904: sage: identity_matrix(ZZ, 2).I sage: def a(): sage: return identity_matrix(ZZ, 2).I sage: a() This is the behaviour in the Sage shell and in Jupyter, while the Sage notebook prints a warning both times! I tried writing a small class with a property and deprecating that, but that works correctly for whatever reason. So I don't know if it could have anything to do with the matrix class being Cython or some other feature of it... Any work-around would be appreciated. Best, Johan -- 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: python3 again
It wouldn't surprise me too much if you can' t build python2 inside a
python 3 venv. Its pretty low on the priority of things to support imho.
Try building with SAGE_PYTHON3=yes
On Thursday, June 30, 2016 at 3:29:25 PM UTC+2, Frédéric Chapoton wrote:
>
> Hello everybody,
>
> I am trying to build sage with python3 (I asked for help here before, but
> got only little).
>
> It fails, of course (see log below for "make build"). I would like to
> understand how.
>
> I am in a python3 virtualenv, and SAGE_ROOT/local/bin/python launches a
> python3
>
> This python3 complains that it cannot find pkg_resources, as follows (from
> the shell)
>
> ./local/bin/python -c 'import pkg_resources;
> pkg_resources.get_distribution("matplotlib").version'
> Traceback (most recent call last):
> File "", line 1, in
> ImportError: No module named 'pkg_resources'
>
> but instead it seems to pick the py2 pkg_resources, when called inside the
> sage-env script.
>
> Any idea ? By the way, please review
> https://trac.sagemath.org/ticket/20909 and
> https://trac.sagemath.org/ticket/20910, which are needed to reach this
> point.
>
> Frederic
>
> sage-logger -p 'sage-spkg python2-2.7.10.p2'
> '/home/chapoton/sage3/logs/pkgs/python2-2.7.10.p2.log'
> [python2-2.7.10.p2] /home/chapoton/sage3/src/bin/sage-env: line 402: 24023
> Aborted (core dumped) "$SAGE_ROOT/local/bin/python" -c
> 'import pkg_resources;
> pkg_resources.get_distribution("matplotlib").version' 2> /dev/null
> [python2-2.7.10.p2] Found local metadata for python2-2.7.10.p2
> [python2-2.7.10.p2] Fatal Python error: Py_Initialize: Unable to get the
> locale encoding
> [python2-2.7.10.p2] File
> "/home/chapoton/sage3/local/lib/python/encodings/__init__.py", line 123
> [python2-2.7.10.p2] raise CodecRegistryError,\
> [python2-2.7.10.p2] ^
> [python2-2.7.10.p2] SyntaxError: invalid syntax
> [python2-2.7.10.p2]
> [python2-2.7.10.p2] Current thread 0x7f7b54334700 (most recent call
> first):
> [python2-2.7.10.p2] /home/chapoton/sage3/build/bin/sage-spkg: line 425:
> 24057 Aborted (core dumped) sage-download-file
> $PKG_NAME_UPSTREAM
> Makefile:2432 : la recette pour la cible «
> /home/chapoton/sage3/local/var/lib/sage/installed/python2-2.7.10.p2 » a
> échouée
>
>
--
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] python3 again
Hello everybody,
I am trying to build sage with python3 (I asked for help here before, but
got only little).
It fails, of course (see log below for "make build"). I would like to
understand how.
I am in a python3 virtualenv, and SAGE_ROOT/local/bin/python launches a
python3
This python3 complains that it cannot find pkg_resources, as follows (from
the shell)
./local/bin/python -c 'import pkg_resources;
pkg_resources.get_distribution("matplotlib").version'
Traceback (most recent call last):
File "", line 1, in
ImportError: No module named 'pkg_resources'
but instead it seems to pick the py2 pkg_resources, when called inside the
sage-env script.
Any idea ? By the way, please review https://trac.sagemath.org/ticket/20909
and https://trac.sagemath.org/ticket/20910, which are needed to reach this
point.
Frederic
sage-logger -p 'sage-spkg python2-2.7.10.p2'
'/home/chapoton/sage3/logs/pkgs/python2-2.7.10.p2.log'
[python2-2.7.10.p2] /home/chapoton/sage3/src/bin/sage-env: line 402: 24023
Aborted (core dumped) "$SAGE_ROOT/local/bin/python" -c
'import pkg_resources;
pkg_resources.get_distribution("matplotlib").version' 2> /dev/null
[python2-2.7.10.p2] Found local metadata for python2-2.7.10.p2
[python2-2.7.10.p2] Fatal Python error: Py_Initialize: Unable to get the
locale encoding
[python2-2.7.10.p2] File
"/home/chapoton/sage3/local/lib/python/encodings/__init__.py", line 123
[python2-2.7.10.p2] raise CodecRegistryError,\
[python2-2.7.10.p2] ^
[python2-2.7.10.p2] SyntaxError: invalid syntax
[python2-2.7.10.p2]
[python2-2.7.10.p2] Current thread 0x7f7b54334700 (most recent call
first):
[python2-2.7.10.p2] /home/chapoton/sage3/build/bin/sage-spkg: line 425:
24057 Aborted (core dumped) sage-download-file
$PKG_NAME_UPSTREAM
Makefile:2432 : la recette pour la cible «
/home/chapoton/sage3/local/var/lib/sage/installed/python2-2.7.10.p2 » a
échouée
--
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: spkgs assumed for doctesting but not default installed
>> ar: /usr/lib/libstdc++.so.6: version `GLIBCXX_3.4.22' not found (required >> by /usr/lib/libLLVM-3.8.so) > > > Are you using llvm? As far as I know that doesnt' work, though I haven't > tried it myself. I was baffled about that too. I haven't consciously done anything that would use llvm. I'm using a fully updated Arch linux, but with gcc rolled back to 5.3. Then I just cloned the git repo and did 'make'. I don't seem have any environment variables pointing to llvm either. Best, Johan -- 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: spkgs assumed for doctesting but not default installed
On Thursday, June 30, 2016 at 2:26:47 PM UTC+2, Johan S. R. Nielsen wrote: > > ar: /usr/lib/libstdc++.so.6: version `GLIBCXX_3.4.22' not found (required > by /usr/lib/libLLVM-3.8.so) Are you using llvm? As far as I know that doesnt' work, though I haven't tried it myself. -- 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] Deprecate the use of properties in all public API
I've created #20904 to deprecate the Matrix.I property which is ready for review. This seemed to be the only case that most people agreed was bad. There remains Matrix.T and Matrix.H as well as a handful of other public API properties scattered randomly across Sage. Best, Johan -- 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: spkgs assumed for doctesting but not default installed
> sounds like the first "make" failed... That's not clear to me. The compile of Sage itself seemed to work but then make failed during doc-building. This has happened so often during the years I've worked with Sage, however, that I've learned to ignore it. Inspecting the error now, I see that this time it has to do with the missing jmol-package. Inspecting install.log, I it seems that everything before seems to have compiled. jmol, sympy, etc. are never mentioned once in the install.log. A disturbing thing though is that the following line appears a lot: ar: /usr/lib/libstdc++.so.6: version `GLIBCXX_3.4.22' not found (required by /usr/lib/libLLVM-3.8.so) as well as: ranlib: /usr/lib/libstdc++.so.6: version `GLIBCXX_3.4.22' not found (required by /usr/lib/libLLVM-3.8.so) However, the packages being compiled report that everything went alright afterwards. I don't know what the errors mean. I have the Arch linux package gcc-libs 5.3.0-5 installed. The install.log is huge and I don't know what might be relevant. I've put the whole thing here: http://atuin.dk/install.log.zip Best, Johan -- 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: Errors in an old, massive patch for Skew Polynomials in Sage
it's quite not clear from your post how to reproduce this. The log mentions some git branch; where is this branch? It might also be easier to parse if you take the failing doctest out and produce few lines of Sage code that need to get the error interactively, at Sage prompt (on the git branch in question) On Thursday, June 30, 2016 at 7:11:36 AM UTC+1, Arpit Merchant wrote: > > Hello, > > My GSoC project is to implement Gabidulin codes which require the Skew > Polynomial ticket #13215. While, a lot of the errors have been eliminated, > we are stuck with a couple of nasty ones that are hampering the progress on > the project. I'm attaching a file that has the tracebacks for them. Can > someone please explain what is going wrong and help arrive at a way to > resolve these? > > Thanks in advance. > > Sincerely, > Arpit. > > -- 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: converting frobby into a new-style package
Ready for review now! On Wednesday, June 29, 2016 at 3:20:09 PM UTC+1, Dima Pasechnik wrote: > > This is going to happen on https://trac.sagemath.org/ticket/20905 > > -- 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.
