Re: [sage-devel] NTL error with conda sage
Yes, that's the expected output, but for me sage crashes with,
sage: matrix(ZZ,3,[1..9]).hermite_form(algorithm='ntl') ## line 1883 ##
halt 2
**
On Fri, Sep 27, 2019 at 6:59 PM François Bissey
wrote:
> Is this what you expect to happen but doesn’t?
> fbissey@moonloop ~ $ sage
> ┌┐
> │ SageMath version 8.9.rc0, Release Date: 2019-09-11 │
> │ Using Python 2.7.15. Type "help()" for help. │
> └┘
> ┏┓
> ┃ Warning: this is a prerelease version, and it may be unstable. ┃
> ┗┛
> sage: matrix(ZZ,3,[1..9]).hermite_form(algorithm='ntl')
> ---
> ValueErrorTraceback (most recent call last)
> in ()
> > 1
> matrix(ZZ,Integer(3),(ellipsis_range(Integer(1),Ellipsis,Integer(9.hermite_form(algorithm='ntl')
>
> /usr/lib64/python2.7/site-packages/sage/matrix/matrix_integer_dense.pyx in
> sage.matrix.matrix_integer_dense.Matrix_integer_dense.echelon_form
> (/dev/shm/portage/sci-mathematics/sage-/work/sage-/src-python2_7/build/cythonized/sage/matrix/matrix_integer_dense.c:17896)()
>2033 w1 = v.HNF(D=D)
>2034 except RuntimeError: # HNF may fail if a nxm matrix
> has rank < m
> -> 2035 raise ValueError("ntl only computes HNF for square
> matrices of full rank.")
>2036
>2037 if include_zero_rows:
>
> ValueError: ntl only computes HNF for square matrices of full rank.
>
> > On 28/09/2019, at 11:26 AM, Isuru Fernando wrote:
> >
> > Hi,
> >
> > Running
> >
> > matrix(ZZ,3,[1..9]).hermite_form(algorithm='ntl')
> >
> > in sage from conda results in the process exiting with "halt 2" as
> opposed to catching the NTL LogicError (child class of std::runtime_error)
> and raising a python exception.
> >
> > Any ideas on why this is?
> >
> > Isuru
> >
> > --
> > 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 view this discussion on the web visit
> https://groups.google.com/d/msgid/sage-devel/CA%2B01voOV3ZeEGpiaUr-zxq81%3DqrhMxF9A-jokYDH2%3Dk%3DNEYYLg%40mail.gmail.com
> .
>
> --
> 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 view this discussion on the web visit
> https://groups.google.com/d/msgid/sage-devel/303A29DE-F105-40CD-ACEC-B6115AF8D90A%40gmail.com
> .
>
--
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 view this discussion on the web visit
https://groups.google.com/d/msgid/sage-devel/CA%2B01voOf2Br_CLvJfWsRcr%3DptP0sVfOai8Ybs84nuRzjDruHGw%40mail.gmail.com.
[sage-devel] Re: How to recover from total git screwup?
On Saturday, September 28, 2019 at 3:17:55 AM UTC+9, Simon King wrote: > > Hi! > > At some point I was advised to use "git worktree" to have one py2 and > one py3 installation sharing the same git repository. Till one hour ago, > it worked fine. > > Now, if I understand correctly, in my py2 worktree, I was on the develop > branch. There was one branch "foobar" (not its real name) that meanwhile > is fully merged, so that I thought it was safe to do "git branch -d > foobar". > However, it seems that my py3 worktree was on that now deleted branch. > > I am not totally sure if that's what was happening. Would git really > allow the "git branch -d" operation when another worktree is on that > branch? > If you were at foobar in py3 worktree and at develop in py2 worktree, no. > In any case, my bash history shows that at some point I did > "git branch -d foobar", and when I am in the py3 worktree, I now get > $ git log > fatal: your current branch 'foobar' does not have any commits yet > > Indeed, all files in the Sage tree are untracked, in the py3 worktree. > And that's why "git checkout develop" won't work (it tells me to commit > are stash first). > > Can you please tell me how to recover from that mess? Why not just add a new shiny py3 worktree and move your untracked files from the old py3 worktree to the new one? -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/502164bf-f987-487a-b649-e1355144347d%40googlegroups.com.
Re: [sage-devel] NTL error with conda sage
Is this what you expect to happen but doesn’t?
fbissey@moonloop ~ $ sage
┌┐
│ SageMath version 8.9.rc0, Release Date: 2019-09-11 │
│ Using Python 2.7.15. Type "help()" for help. │
└┘
┏┓
┃ Warning: this is a prerelease version, and it may be unstable. ┃
┗┛
sage: matrix(ZZ,3,[1..9]).hermite_form(algorithm='ntl')
---
ValueErrorTraceback (most recent call last)
in ()
> 1
matrix(ZZ,Integer(3),(ellipsis_range(Integer(1),Ellipsis,Integer(9.hermite_form(algorithm='ntl')
/usr/lib64/python2.7/site-packages/sage/matrix/matrix_integer_dense.pyx in
sage.matrix.matrix_integer_dense.Matrix_integer_dense.echelon_form
(/dev/shm/portage/sci-mathematics/sage-/work/sage-/src-python2_7/build/cythonized/sage/matrix/matrix_integer_dense.c:17896)()
2033 w1 = v.HNF(D=D)
2034 except RuntimeError: # HNF may fail if a nxm matrix has
rank < m
-> 2035 raise ValueError("ntl only computes HNF for square
matrices of full rank.")
2036
2037 if include_zero_rows:
ValueError: ntl only computes HNF for square matrices of full rank.
> On 28/09/2019, at 11:26 AM, Isuru Fernando wrote:
>
> Hi,
>
> Running
>
> matrix(ZZ,3,[1..9]).hermite_form(algorithm='ntl')
>
> in sage from conda results in the process exiting with "halt 2" as opposed to
> catching the NTL LogicError (child class of std::runtime_error) and raising a
> python exception.
>
> Any ideas on why this is?
>
> Isuru
>
> --
> 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 view this discussion on the web visit
> https://groups.google.com/d/msgid/sage-devel/CA%2B01voOV3ZeEGpiaUr-zxq81%3DqrhMxF9A-jokYDH2%3Dk%3DNEYYLg%40mail.gmail.com.
--
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 view this discussion on the web visit
https://groups.google.com/d/msgid/sage-devel/303A29DE-F105-40CD-ACEC-B6115AF8D90A%40gmail.com.
[sage-devel] NTL error with conda sage
Hi, Running matrix(ZZ,3,[1..9]).hermite_form(algorithm='ntl') in sage from conda results in the process exiting with "halt 2" as opposed to catching the NTL LogicError (child class of std::runtime_error) and raising a python exception. Any ideas on why this is? Isuru -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/CA%2B01voOV3ZeEGpiaUr-zxq81%3DqrhMxF9A-jokYDH2%3Dk%3DNEYYLg%40mail.gmail.com.
[sage-devel] Re: How to recover from total git screwup?
On 2019-09-27, Simon King wrote: > Indeed, all files in the Sage tree are untracked, in the py3 worktree. > And that's why "git checkout develop" won't work (it tells me to commit > are stash first). > > Can you please tell me how to recover from that mess? Perhaps "git checkout -f " in the py3 worktree? Or would that do more harm than good? Certainly "git stash" is not a serious option, as this would be a copy of the whole Sage sources (namely the diff between a branch with an empty commit history and the Sage sources). Best regards, Simon -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/qmlsne%24316%241%40blaine.gmane.org.
[sage-devel] Re: Machine Learning people apparently built a symbolic integrator
Thanks for sharing! This looks very promising. I hope we have it in Sage some day. Eric. Le vendredi 27 septembre 2019 17:06:31 UTC+2, Dima Pasechnik a écrit : > > https://openreview.net/pdf?id=S1eZYeHFDS > > I wish they had code available... > -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/090c84e2-956e-4a7c-8ec7-eb68f5f1c0e7%40googlegroups.com.
[sage-devel] How to recover from total git screwup?
Hi! At some point I was advised to use "git worktree" to have one py2 and one py3 installation sharing the same git repository. Till one hour ago, it worked fine. Now, if I understand correctly, in my py2 worktree, I was on the develop branch. There was one branch "foobar" (not its real name) that meanwhile is fully merged, so that I thought it was safe to do "git branch -d foobar". However, it seems that my py3 worktree was on that now deleted branch. I am not totally sure if that's what was happening. Would git really allow the "git branch -d" operation when another worktree is on that branch? In any case, my bash history shows that at some point I did "git branch -d foobar", and when I am in the py3 worktree, I now get $ git log fatal: your current branch 'foobar' does not have any commits yet Indeed, all files in the Sage tree are untracked, in the py3 worktree. And that's why "git checkout develop" won't work (it tells me to commit are stash first). Can you please tell me how to recover from that mess? Best regards, Simon -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/qmljo4%245v23%241%40blaine.gmane.org.
[sage-devel] Package installation/uninstallation confusion
I have been testing new versions of Simon King's p-group cohomology package. The current version doesn't work with Python 3, and he has been working (#28414) to fix this. My workflow: 1. check out his git branch 2. run ./sage -f -c p_group_cohomology 3. report any issues 4. check out develop branch Here is the problem: if step 2 works (which it has been recently), then `build/make/Makefile` gets modified, adding p_group_cohomology to the list of installed packages. When I switch back to the develop branch, then (since I am using a Python 3 build of Sage), Sage doesn't build any more, because it tries to build the broken version of the p_group_cohomology package. So then I do - "make p_group_cohomology-clean" but this does not change `build/make/Makefile` and so it does not fix the problem. I can either edit the Makefile by hand or rerun ./configure. So here are some questions: - Is "sage -i PKG" or "sage -f PKG" the preferred way to install an optional package? That's what our Developer's Guide says. Or should I be using "make PKG", which does not modify "build/make/Makefile"? - Assuming I should keep using "sage -f PKG", should there be an analogous command which uninstalls and then rebuilds the Makefile? Or should "make PKG-clean" itself rebuild the Makefile? -- John -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/8580c565-d127-4b91-ac16-c8ab7514%40googlegroups.com.
[sage-devel] Machine Learning people apparently built a symbolic integrator
https://openreview.net/pdf?id=S1eZYeHFDS I wish they had code available... -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/CAAWYfq0aTCMuuvhCijAax-uEARuxfhzVnfwgbp09guDMZ4LYuQ%40mail.gmail.com.
Re: [sage-devel] is patchbot.sagemath.org down?
Thanks for reporting, i restarted the services, seems OK now. Thierry On Fri, Sep 27, 2019 at 04:21:59AM -0700, mmarco wrote: > I get an Internal Server Error when I try to access the patchbot. In > particular, I can't see patchbot reports for any ticket. > > To make sure that it is not a problem with my network: does anybody else > experience the same? > > -- > 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 view this discussion on the web visit > https://groups.google.com/d/msgid/sage-devel/5a16d06f-ff2e-4c07-8843-8304c384e9e2%40googlegroups.com. -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/20190927112738.hcre25oumtgzn2v4%40metelu.net.
[sage-devel] is patchbot.sagemath.org down?
I get an Internal Server Error when I try to access the patchbot. In particular, I can't see patchbot reports for any ticket. To make sure that it is not a problem with my network: does anybody else experience the same? -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/5a16d06f-ff2e-4c07-8843-8304c384e9e2%40googlegroups.com.
Re: [sage-devel] Re: UniqueRepresentation inheritance and __classcall__
Indeed it seems to be documented. Why is this not in the online documentation? S. * Travis Scrimshaw [2019-09-26 17:59:38]: There is also an example of this inheritance and discussion in one of the sage.structure.unique_representation examples. Best, Travis On Friday, September 27, 2019 at 10:57:52 AM UTC+10, Travis Scrimshaw wrote: The prototype does, now I have to implement the real thing. Is there any way to add this info to the documentation? It took me a lot of trial and error to figure out how to do what I wanted. S. Definitely. The topical place would be in sage.misc.classcall_metaclass, since that is the module that implements the __classcall__ mechanism. That's also the documentation you find when you google "__classcall__" (once you convince google you don't want the results for __call__). This is actually documented. The problem is the ClasscallMetaclass.__call__ is not in the online documentation (in some sense, Google does know better :P). Best, Travis -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/ef937635-dbf2-4e7e-ab85-6ef5c8a24335%40googlegroups.com. -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/20190927104200.GM22409%40strabo.
[sage-devel] NEWOBJ isn't a type object
Hi!
Trying to make my group cohomology package work in both py2 and py3, I
already thought it was done, but I found that a pickle created with py3
cannot be read by py2. It would of course be possible to argue that people
are unlikely to unpickle a py3 pickle with py2, and since unpickling a
py2 pickle with py3 seems to work, we shouldn't care.
But just in case I wanted to ask if you know of an easy fix.
According to explain_pickle, the following happens:
sage: pg_RESL_sparse_unpickle_class =
unpickle_global('pGroupCohomology.resolution', 'RESL_sparse_unpickle_class')
sage: si1 = unpickle_newobj(pg_RESL_sparse_unpickle_class, ())
Traceback (most recent call last):
...
UnpicklingError: NEWOBJ class argument isn't a type object
What does that error mean? In fact, the class IS a type:
sage: from pGroupCohomology.resolution import RESL_sparse_unpickle_class
sage: isinstance(_, type)
True
Best regards,
Simon
--
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 view this discussion on the web visit
https://groups.google.com/d/msgid/sage-devel/qmko8k%24jhk%241%40blaine.gmane.org.
