Hi Kwankyu,
On 2019-09-27, Kwankyu Lee wrote:
>> 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.
Then what e
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
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 w
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. │
└
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 mes
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 w
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 sub
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) tha
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. chec
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
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 p
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 G
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 a
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 p
14 matches
Mail list logo
