On Sunday, February 3, 2019 at 7:23:52 PM UTC-6, Simon King wrote:
>
> Hi Nathan, 
>
> On 2019-02-04, Nathan Dunfield <nat...@dunfield.info <javascript:>> 
> wrote: 
> > On Sage 8.6 with Python 2, the following command produces the expected 
> > result (namely, a sage.interfaces.gap.GapElement): 
> > 
> > sage: gap('0') 
> > 0 
> > 
> > whereas in Sage 8.6 with Python 3 I get the following error: 
>
> Works for me. In Sage 8.7.beta1 with Python 3.6.6, I get 
>   sage: gap(0) 
>   0 
>   sage: gap('0') 
>   0 
>

I just tried the git tip, which is Sage 8.7.beta2, and get the same error 
as before.  The main error seems to be:

FileNotFoundError: [Errno 2] No such file or directory: 
'/home/sage/.sage/gap/gap-workspace-0x1bd17f6665cc701c'

It is the indeed the case that there is no file gap-workspace* in 
$HOME/.sage/gap, in fact, there is no directory $HOME/.sage/gap at all!  If 
I do "libgap(0)", which does work, then a file 
$HOME/.sage/gap/libgap-workspace-* is created.

This is on a complete clean Docker image [1], so possibly the reason it 
works for you but not me is that you have a gap-workspace file left over 
from a previous version?  On the other hand, I tried copying over a 
gap-workspace file from the Python 2 version of Sage and that didn't help. 
So perhaps the error is coming when it tries to create the file or 
something.

Essentially the only difference between [1] and my usual Docker image [2] 
is that I specify the config flag "python3" during the Sage build process.

Best,

Nathan

[1] https://bitbucket.org/t3m/sagedocker/src/default/sage-py3/
[2] https://hub.docker.com/r/computop/sage

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

Reply via email to