Re: [sage-support] Re: Removing packages and different versions of python

[Jean-Florent Raymond]

Thanks, that answers my questions!

Le 15/04/2022 à 20:00, Matthias Koeppe a écrit :

On Friday, April 15, 2022 at 12:39:23 AM UTC-7 Jean-Florent Raymond wrote:


In order to test something I would like to remove from my sage install a
python package that I installed (and updated) some time ago.

First question:
How can I remove a package installed with "sage -i"? I found
instructions in the doc to install packages, but nothing to remove them.
Is "sage -i" the same as "sage -pip install" (and "pip install" in a
"sage -sh" session), so I can simply do "sage -pip uninstall"?



To uninstall a package SPKG, use either "make SPKG-clean" or "make
SPKG-uninstall" - depending on the package source type (see
https://doc.sagemath.org/html/en/developer/packaging.html#package-source-types).
(We are in the process of unifying this -
https://trac.sagemath.org/ticket/29097)

When checking if there remain some files named after this package after

the "sage -pip uninstall" command, I can see that the package is still
installed in:

sage/local/lib/python3.7/site-packages/
sage/local/lib/python3.9/site-packages/

I guess because I installed it when the python version of my sage
install was 3.7 or 3.9 (currently it is 3.10.3).


I don't think there is a reason to keep this, hence my second question :

how to remove this given that I don't have python3.7 or python3.9
anymore in sage-sh ? Can I just rm everything in
sage/local/lib/python3.7 and sage/local/lib/python3.9?



Yes, you can safely "rm" it.
  


Last question: what does "spkg" mean :) ?



I think it just means "Sage package".
  


Is it just any package that
can be installed to use with Sage, some of which are standard python
(pip-installable) packages and some with different install scripts?



Yes.



--
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-support/b34e8687-012a-195c-fbd4-e9bb21a47824%40uca.fr.

[sage-support] Removing packages and different versions of python

[Jean-Florent Raymond]

Hello,

In order to test something I would like to remove from my sage install a 
python package that I installed (and updated) some time ago.


First question:
How can I remove a package installed with "sage -i"? I found 
instructions in the doc to install packages, but nothing to remove them.
Is "sage -i" the same as "sage -pip install" (and "pip install" in a 
"sage -sh" session), so I can simply do "sage -pip uninstall"?


When checking if there remain some files named after this package after 
the "sage -pip uninstall" command, I can see that the package is still 
installed in:


sage/local/lib/python3.7/site-packages/
sage/local/lib/python3.9/site-packages/

I guess because I installed it when the python version of my sage 
install was 3.7 or 3.9 (currently it is 3.10.3).
I don't think there is a reason to keep this, hence my second question : 
how to remove this given that I don't have python3.7 or python3.9 
anymore in sage-sh ? Can I just rm everything in 
sage/local/lib/python3.7 and sage/local/lib/python3.9?


Last question: what does "spkg" mean :) ? Is it just any package that 
can be installed to use with Sage, some of which are standard python 
(pip-installable) packages and some with different install scripts?


Best,
Jean-Florent.

--
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-support/e7d502b6-d8a7-16ae-7882-f56d57996298%40uca.fr.

Re: [sage-support] List all shortest paths between two vertices in a graph

[Jean-Florent Raymond]

Hello,

The function shortest_simple_paths returns an iterator with paths sorted
by increasing length. Therefore if you only want paths of minimum
length, you can iterate over the result of shortest_simple_paths and
stop as soon as you encounter a longer path. That way you do not iterate
over all the (possibly many) irrelevant longer paths and, depending on
how shortest_simple_paths is implemented, you might even avoid to
compute them.

Something like that:

def shortest_paths_really(G, u, v):
"""Return all the shortest simple paths between u and v"""

uv_paths = G.shortest_simple_paths(u, v)
first_path = next(uv_paths) # a shortest path
dist = len(first_path)
yield first_path
for path in uv_paths:
if len(path) > dist:
# no need to go further: paths are too long for now on
return
yield path

It is not obvious that doing so is much faster than your solution: it
depends on the implementation of shortest_simple_paths, which I did not
look.
You can convince yourself that it saves some time at least by looking at
a graph where two vertices have few shortest paths and many longer paths
connecting them. For instance in graphs.CircularLadderGraph(n) there are
only two shortest paths connecting vertices 1 and n but exponentially
many of longer length.

sage: n = 10
sage: G = graphs.CircularLadderGraph(n)
sage: u, v = 1, n
sage: %timeit list(shortest_paths_really(G, u, v))
35.9 µs ± 159 ns per loop (mean ± std. dev. of 7 runs, 1 loops each)
sage: %timeit list(filter(lambda x: len(x) ==  1+G.distance(u, v),
G.shortest_simple_paths(u, v)))
66.6 ms ± 180 µs per loop (mean ± std. dev. of 7 runs, 10 loops each)


Jean-Florent.

Le 24/08/2021 à 01:39, Beth Claire a écrit :
> Hi,
> Given an undirected graph G, and two vertices u and v of G, I want to list 
> all paths from u to v with a length of d_G(u,v).  The built-in function 
> shortest_simple_paths 
> ,
>  
> despite its name, seems to list *all* simple paths from u to v.  One option 
> is to filter the output of shortest_simple_paths by length, e.g.
> list(filter(lambda x: len(x)== 
> 1+G.distance(u,v)),G.shortest_simple_paths(u,v)))
> 
> However, this is extremely inefficient, since it tells sage to generate all 
> simple paths and then discards most of them.  Is there a better way to get 
> this information?
> 
> Thanks,
> Beth
> 

-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-support/d0df352f-a07b-c854-ea78-0234b2006ae9%40uca.fr.

Re: [sage-support] fails to get graph_editor() to work

[Jean-Florent Raymond]

Actually the problem came from ipycanvas
(https://github.com/martinRenou/ipycanvas/issues/117 ) and not sage.
Downgrading to version 0.4.7 ( sage -pip install ipycanvas==0.4.7 )
solved the problem.

Le 31/08/2020 à 09:50, Dima Pasechnik a écrit :
> On Mon, 31 Aug 2020, 08:29 Jean-Florent Raymond, 
> wrote:
> 
>> Thanks for reporting this.
>> On my machine it works with the version of sage I was using at the
>> beginning of summer (version 9.2.beta1, release date: 2020-06-13) but
>> fails when I compile the latest version from develop.
>> I will investigate and try to fix this problem.
>>
> 
> a bunch of Jupyter-related packages has been updated since.
> 
>>
>>
>> Le 31/08/2020 à 00:15, pong a écrit :
>>> Thanks, sage --python setup.py install works for me as well!
>>>
>>> However, when I try the code in the README
>>>
>>> from phitigra import EditableGraph
>>> eg = EditableGraph(graphs.RandomGNP(10, 0.5))
>>> eg.show()
>>>
>>> It gives a static picture of a graph. But I can't click to create new
>> nodes
>>> nor drag any node with a mouse.
>>> On Sunday, August 30, 2020 at 2:13:55 PM UTC-7 dim...@gmail.com wrote:
>>>
>>>> On Sun, Aug 30, 2020 at 10:03 PM pong  wrote:
>>>>>
>>>>> Hi Jean-Florent,
>>>>>
>>>>> I did exactly just that (see attachment) but it complains about the
>> need
>>>> of at least one requirement to install.
>>>>> Please advise.
>>>>
>>>> how about just doing
>>>>
>>>> sage --python setup.py install
>>>>
>>>> in the root directory of phitigra ?
>>>> it works for me.
>>>>>
>>>>> On Sunday, August 30, 2020 at 12:25:11 AM UTC-7 Jean-Florent Raymond
>>>> wrote:
>>>>>>
>>>>>> Hello,
>>>>>>
>>>>>> Yes, the directory where to run
>>>>>> sage -pip install --upgrade --no-index -v .
>>>>>> is the directory of the just cloned project (default: phitigra).
>>>>>> There is no need to add 'phitigra' to the command line: pip will guess
>>>>>> alone what to install from this directory.
>>>>>>
>>>>>> Jean-Florent.
>>>>>>
>>>>>> Le 30/08/2020 à 02:35, pong a écrit :
>>>>>>> Thanks you. I clone the project but confused what to do next. In the
>>>>>>> README, it saids
>>>>>>>
>>>>>>> Change to the root directory and run:
>>>>>>> $ sage -pip install --upgrade --no-index -v .
>>>>>>>
>>>>>>> which root directory are we talking about? the phitigra directory?
>>>>>>> Also should it be sage -pip install phitigra --upgrade -no-index -v?
>>>>>>>
>>>>>>> In any case, I couldn't get it install so I must be doing something
>>>> wrong.
>>>>>>> Please help.
>>>>>>>
>>>>>>> On Saturday, August 29, 2020 at 2:11:12 AM UTC-7 Jean-Florent
>> Raymond
>>>> wrote:
>>>>>>>
>>>>>>>> Hello,
>>>>>>>>
>>>>>>>> I recently started developing a replacement to graph_editor for the
>>>>>>>> jupyter notebook, using ipywidgets and ipycanvas.
>>>>>>>> You can find it at the following address :
>>>>>>>> https://gitlab.limos.fr/jfraymon/phitigra
>>>>>>>>
>>>>>>>> This is still work in progress but the basic editor (adding removing
>>>>>>>> vertices and edges, displaying the graph, etc.) works.
>>>>>>>> One feature that this editor will have is that changes made to the
>>>> graph
>>>>>>>> outside of the editor will be automatically updated in the editor.
>>>> This
>>>>>>>> will for instance allow to display step by step the computation
>> done
>>>> by
>>>>>>>> a function (for teaching, or debugging, or ...).
>>>>>>>>
>>>>>>>> Any feedback is welcome.
>>>>>>>>
>>>>>>>> Jean-Florent.
>>>>>>>>
>>>>>>>> Le 29/08/2020 à 08:27, pong a écrit :
>>>>>>>>> I see. Is there a substitute

Re: [sage-support] fails to get graph_editor() to work

[Jean-Florent Raymond]

Thanks for reporting this.
On my machine it works with the version of sage I was using at the
beginning of summer (version 9.2.beta1, release date: 2020-06-13) but
fails when I compile the latest version from develop.
I will investigate and try to fix this problem.


Le 31/08/2020 à 00:15, pong a écrit :
> Thanks, sage --python setup.py install works for me as well!
> 
> However, when I try the code in the README
> 
> from phitigra import EditableGraph 
> eg = EditableGraph(graphs.RandomGNP(10, 0.5)) 
> eg.show()
> 
> It gives a static picture of a graph. But I can't click to create new nodes 
> nor drag any node with a mouse.
> On Sunday, August 30, 2020 at 2:13:55 PM UTC-7 dim...@gmail.com wrote:
> 
>> On Sun, Aug 30, 2020 at 10:03 PM pong  wrote:
>>>
>>> Hi Jean-Florent,
>>>
>>> I did exactly just that (see attachment) but it complains about the need 
>> of at least one requirement to install.
>>> Please advise.
>>
>> how about just doing
>>
>> sage --python setup.py install
>>
>> in the root directory of phitigra ?
>> it works for me.
>>>
>>> On Sunday, August 30, 2020 at 12:25:11 AM UTC-7 Jean-Florent Raymond 
>> wrote:
>>>>
>>>> Hello,
>>>>
>>>> Yes, the directory where to run
>>>> sage -pip install --upgrade --no-index -v .
>>>> is the directory of the just cloned project (default: phitigra).
>>>> There is no need to add 'phitigra' to the command line: pip will guess
>>>> alone what to install from this directory.
>>>>
>>>> Jean-Florent.
>>>>
>>>> Le 30/08/2020 à 02:35, pong a écrit :
>>>>> Thanks you. I clone the project but confused what to do next. In the
>>>>> README, it saids
>>>>>
>>>>> Change to the root directory and run:
>>>>> $ sage -pip install --upgrade --no-index -v .
>>>>>
>>>>> which root directory are we talking about? the phitigra directory?
>>>>> Also should it be sage -pip install phitigra --upgrade -no-index -v?
>>>>>
>>>>> In any case, I couldn't get it install so I must be doing something 
>> wrong.
>>>>> Please help.
>>>>>
>>>>> On Saturday, August 29, 2020 at 2:11:12 AM UTC-7 Jean-Florent Raymond 
>> wrote:
>>>>>
>>>>>> Hello,
>>>>>>
>>>>>> I recently started developing a replacement to graph_editor for the
>>>>>> jupyter notebook, using ipywidgets and ipycanvas.
>>>>>> You can find it at the following address :
>>>>>> https://gitlab.limos.fr/jfraymon/phitigra
>>>>>>
>>>>>> This is still work in progress but the basic editor (adding removing
>>>>>> vertices and edges, displaying the graph, etc.) works.
>>>>>> One feature that this editor will have is that changes made to the 
>> graph
>>>>>> outside of the editor will be automatically updated in the editor. 
>> This
>>>>>> will for instance allow to display step by step the computation done 
>> by
>>>>>> a function (for teaching, or debugging, or ...).
>>>>>>
>>>>>> Any feedback is welcome.
>>>>>>
>>>>>> Jean-Florent.
>>>>>>
>>>>>> Le 29/08/2020 à 08:27, pong a écrit :
>>>>>>> I see. Is there a substitute for graph_editor()? It's fairly 
>> convenient.
>>>>>>>
>>>>>>> On Thursday, August 27, 2020 at 8:48:32 AM UTC-7 dim...@gmail.com 
>> wrote:
>>>>>>>
>>>>>>>> On Thu, Aug 27, 2020 at 4:45 PM pong  wrote:
>>>>>>>>
>>>>>>>>>
>>>>>>>>> Running sagemath 9.1 from a jupyter notebook
>>>>>>>>>
>>>>>>>>> When calling graph_editor() got the following error message.
>>>>>>>>> How can I make the module 'sagenb' works again?
>>>>>>>>>
>>>>>>>>
>>>>>>>> sagenb does not work with Python 3. You'd need Sage 9.1 (or 
>> earlier)
>>>>>> built
>>>>>>>> with Python2 in order to be able to use sagenb.
>>>>>>>>
>>>>>>>> And sagenb will be definitely gone in 9.2, which won't support 
>> Python 2.
>>>>>>>

Re: [sage-support] fails to get graph_editor() to work

[Jean-Florent Raymond]

Hello,

Yes, the directory where to run
sage -pip install --upgrade --no-index -v .
is the directory of the just cloned project (default: phitigra).
There is no need to add 'phitigra' to the command line: pip will guess
alone what to install from this directory.

Jean-Florent.

Le 30/08/2020 à 02:35, pong a écrit :
> Thanks you. I clone the project but confused what to do next. In the 
> README, it saids
> 
> Change to the root directory and run:
> $ sage -pip install --upgrade --no-index -v .
> 
> which root directory are we talking about? the phitigra directory?
> Also should it be sage -pip install phitigra --upgrade -no-index -v?
> 
> In any case, I couldn't get it install so I must be doing something wrong. 
> Please help.
> 
> On Saturday, August 29, 2020 at 2:11:12 AM UTC-7 Jean-Florent Raymond wrote:
> 
>> Hello,
>>
>> I recently started developing a replacement to graph_editor for the
>> jupyter notebook, using ipywidgets and ipycanvas.
>> You can find it at the following address :
>> https://gitlab.limos.fr/jfraymon/phitigra
>>
>> This is still work in progress but the basic editor (adding removing
>> vertices and edges, displaying the graph, etc.) works.
>> One feature that this editor will have is that changes made to the graph
>> outside of the editor will be automatically updated in the editor. This
>> will for instance allow to display step by step the computation done by
>> a function (for teaching, or debugging, or ...).
>>
>> Any feedback is welcome.
>>
>> Jean-Florent.
>>
>> Le 29/08/2020 à 08:27, pong a écrit :
>>> I see. Is there a substitute for graph_editor()? It's fairly convenient.
>>>
>>> On Thursday, August 27, 2020 at 8:48:32 AM UTC-7 dim...@gmail.com wrote:
>>>
>>>> On Thu, Aug 27, 2020 at 4:45 PM pong  wrote:
>>>>
>>>>>
>>>>> Running sagemath 9.1 from a jupyter notebook
>>>>>
>>>>> When calling graph_editor() got the following error message.
>>>>> How can I make the module 'sagenb' works again?
>>>>>
>>>>
>>>> sagenb does not work with Python 3. You'd need Sage 9.1 (or earlier) 
>> built 
>>>> with Python2 in order to be able to use sagenb.
>>>>
>>>> And sagenb will be definitely gone in 9.2, which won't support Python 2.
>>>>
>>>> HTH
>>>> Dima
>>>>
>>>>>
>>>>> [image: ge.png]
>>>>>
>>>>> -- 
>>>>> You received this message because you are subscribed to the Google 
>> Groups 
>>>>> "sage-support" group.
>>>>> To unsubscribe from this group and stop receiving emails from it, send 
>> an 
>>>>> email to sage-support...@googlegroups.com.
>>>>> To view this discussion on the web visit 
>>>>>
>> https://groups.google.com/d/msgid/sage-support/772c9f8f-e27f-4485-8add-ca97d51290bbn%40googlegroups.com
>>  
>>>>> <
>> https://groups.google.com/d/msgid/sage-support/772c9f8f-e27f-4485-8add-ca97d51290bbn%40googlegroups.com?utm_medium=email_source=footer
>>>
>>>>> .
>>>>>
>>>>
>>>
>>
> 

-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-support/187962dc-302a-2527-f183-0f42c25e652c%40uca.fr.

Re: [sage-support] fails to get graph_editor() to work

[Jean-Florent Raymond]

Hello,

I recently started developing a replacement to graph_editor for the
jupyter notebook, using ipywidgets and ipycanvas.
You can find it at the following address :
https://gitlab.limos.fr/jfraymon/phitigra

This is still work in progress but the basic editor (adding removing
vertices and edges, displaying the graph, etc.) works.
One feature that this editor will have is that changes made to the graph
outside of the editor will be automatically updated in the editor. This
will for instance allow to display step by step the computation done by
a function (for teaching, or debugging, or ...).

Any feedback is welcome.

Jean-Florent.

Le 29/08/2020 à 08:27, pong a écrit :
> I see. Is there a substitute for graph_editor()? It's fairly convenient.
> 
> On Thursday, August 27, 2020 at 8:48:32 AM UTC-7 dim...@gmail.com wrote:
> 
>> On Thu, Aug 27, 2020 at 4:45 PM pong  wrote:
>>
>>>
>>> Running sagemath 9.1 from a jupyter notebook
>>>
>>> When calling graph_editor() got the following error message.
>>> How can I make the module 'sagenb' works again?
>>>
>>
>> sagenb does not work with Python 3. You'd need Sage 9.1 (or earlier) built 
>> with Python2 in order to be able to use sagenb.
>>
>> And sagenb will be definitely gone in 9.2, which won't support Python 2.
>>
>> HTH
>> Dima
>>
>>>
>>> [image: ge.png]
>>>
>>> -- 
>>> You received this message because you are subscribed to the Google Groups 
>>> "sage-support" group.
>>> To unsubscribe from this group and stop receiving emails from it, send an 
>>> email to sage-support...@googlegroups.com.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/sage-support/772c9f8f-e27f-4485-8add-ca97d51290bbn%40googlegroups.com
>>>  
>>> 
>>> .
>>>
>>
> 

-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-support/b3eeea4c-5474-d294-1544-b2b89f872044%40uca.fr.

Re: [sage-support] How to search a usage of a specific function?

[Jean-Florent Raymond]

Hello,

To show the description of a function, you can type the name of the
function followed by a question mark ("Mod?" in your case) and press
Enter. If you want to show the source of the function, you can do the
same thing with two question marks instead ("Mod??").


Le 13/05/2020 à 15:35, GZ D a écrit :
> For example, I want to search the usage of the function called *Mod*, and 
> what should I do if I want to know the usage and the related description of 
> this function？
> 

-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-support/8d9f41f3-271d-dae6-3809-8c769db6c052%40uca.fr.

Re: [sage-support] Sage Crash Report

[Jean-Florent Raymond]

Hello,

Did you try to rebuild since the upgrade?
If you upgraded a package that sage needs, then sage might complain that
it cannot find the version it was used to.

It seems to be the case with libntl according to the crash report you
attached:
ImportError: libntl.so.35: cannot open shared object file: No such file
or directory



Le 23/04/2020 à 15:10, Soufiane Lakhlifi a écrit :
> Hello,
> 
> Here is the report of a crash that happened while trying to lunch sage:
> 
> -Operating system: Ubuntu 20.04 beta, upgraded from 19.10.
> -Sage (8.9) was build  from the source under Ubuntu 19.10 and by following
>  the instructions in this page
> http://doc.sagemath.org/html/en/installation/source.html.
>  No special flags were used except to change the build directory.
> -The crash happened by lunching sage (with no arguments) from the terminal,
>  it is worth noting that the crash happened just after I upgraded my Ubuntu
> from
>  19.10 to 20.10.
> 
> Best regards,
> Soufiane Lakhlifi.
> Zone contenant les pièces jointes
> 

-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-support/31ae06a6-0ace-d577-6d46-ce5e16ca7073%40uca.fr.

Re: [sage-support] building docs with sphinx-1.8.5 fails with existing _static

[Jean-Florent Raymond]

Hello,

A workaround is to run "make" after "make doc-clean".
It worked for me.

Source:
https://groups.google.com/forum/?utm_medium=email_source=footer#!msg/sage-devel/RHMEHCTp_pU/12BWV897AgAJ

Related: https://github.com/sphinx-doc/sphinx/issues/7407

Best regards,

Jean-Florent.

Le 23/04/2020 à 13:20, 'Reimundo Heluani' via sage-support a écrit :
> 
> Hello, I posted this on ask.sagemath.org
> 
> https://ask.sagemath.org/question/50925/building-docs-with-sphinx-185/
> 
> On my own git branch, after the last pull I hit this error on "sage
> --docbuild refernce html" even after a "make doc-clean".
> 
> This looks like what's described in this ticket
> https://trac.sagemath.org/ticket/26451 but this is already applied in my
> branch
> 
> The link _static on
> local/share/doc/sage/html/en/reference/references/_static points to a
> non-existing directory ../_static
> 
> After a "make doc-clean" it gets erased but it is recreated on the run
> of "sage --docbuild"
> 
> This is $ uname -a
> Linux rye 5.6.3-arch1-1 #1 SMP PREEMPT Wed, 08 Apr 2020 07:47:16 +
> x86_64 GNU/Linux
> 
> on my own sage git which is very much up to date
> 
> sage: version()
> 'SageMath version 9.1.beta8, Release Date: 2020-03-18'
> 
> The log of the error is
> 
> # Sphinx version: 1.8.5
> # Python version: 3.7.3 (CPython)
> # Docutils version: 0.14 # Jinja2 version: 2.10
> # Last messages:
> #   linking _static directory.
> #   copying extra files...
> #   done
> #   dumping search index in English (code: en) ...
> #   done
> #   dumping object inventory...
> #   done
> #   build succeeded, 1295 warnings.
> #   #   The HTML pages are in
> local/share/doc/sage/html/en/reference/references.
> # Loaded extensions:
> #   sphinx.ext.mathjax (1.8.5) from
> /home/user/Documents/code/sage/sage/local/lib/python3.7/site-packages/sphinx/ext/mathjax.py
> 
> #   alabaster (0.7.12) from
> /home/user/Documents/code/sage/sage/local/lib/python3.7/site-packages/alabaster/__init__.py
> 
> #   inventory_builder (unknown version) from
> /home/user/Documents/code/sage/sage/src/sage_setup/docbuild/ext/inventory_builder.py
> 
> #   multidocs (unknown version) from
> /home/user/Documents/code/sage/sage/src/sage_setup/docbuild/ext/multidocs.py
> 
> #   sage_autodoc (1.8.5) from
> /home/user/Documents/code/sage/sage/src/sage_setup/docbuild/ext/sage_autodoc.py
> 
> #   sphinx.ext.graphviz (1.8.5) from
> /home/user/Documents/code/sage/sage/local/lib/python3.7/site-packages/sphinx/ext/graphviz.py
> 
> #   sphinx.ext.inheritance_diagram (1.8.5) from
> /home/user/Documents/code/sage/sage/local/lib/python3.7/site-packages/sphinx/ext/inheritance_diagram.py
> 
> #   sphinx.ext.todo (1.8.5) from
> /home/user/Documents/code/sage/sage/local/lib/python3.7/site-packages/sphinx/ext/todo.py
> 
> #   sphinx.ext.extlinks (1.8.5) from
> /home/user/Documents/code/sage/sage/local/lib/python3.7/site-packages/sphinx/ext/extlinks.py
> 
> #   IPython.sphinxext.ipython_directive (unknown version) from
> /home/user/Documents/code/sage/sage/local/lib/python3.7/site-packages/IPython/sphinxext/ipython_directive.py
> 
> #   matplotlib.sphinxext.plot_directive (unknown version) from
> /home/user/Documents/code/sage/sage/local/lib/python3.7/site-packages/matplotlib/sphinxext/plot_directive.py
> 
> Traceback (most recent call last):
>   File
> "/home/user/Documents/code/sage/sage/local/lib/python3.7/site-packages/sphinx/cmd/build.py",
> line 304, in build_main
>     app.build(args.force_all, filenames)
>   File
> "/home/user/Documents/code/sage/sage/local/lib/python3.7/site-packages/sphinx/application.py",
> line 369, in build
>     self.emit('build-finished', None)
>   File
> "/home/user/Documents/code/sage/sage/local/lib/python3.7/site-packages/sphinx/application.py",
> line 510, in emit
>     return self.events.emit(event, self, *args)
>   File
> "/home/user/Documents/code/sage/sage/local/lib/python3.7/site-packages/sphinx/events.py",
> line 80, in emit
>     results.append(callback(*args))
>   File
> "/home/user/Documents/code/sage/sage/local/lib/python3.7/site-packages/sphinx/ext/graphviz.py",
> line 414, in on_build_finished
>     copy_asset(src, dst)
>   File
> "/home/user/Documents/code/sage/sage/local/lib/python3.7/site-packages/sphinx/util/fileutil.py",
> line 81, in copy_asset
>     ensuredir(destination)
>   File
> "/home/user/Documents/code/sage/sage/local/lib/python3.7/site-packages/sphinx/util/osutil.py",
> line 90, in ensuredir
>     os.makedirs(path)
>   File "/home/user/Documents/code/sage/sage/local/lib/python3.7/os.py",
> line 221, in makedirs
>     mkdir(name, mode)
> FileExistsError: [Errno 17] File exists:
> '/home/user/Documents/code/sage/sage/local/share/doc/sage/html/en/reference/references/_static'
> 
> 
> 
> I appreciate any help.
> 
> Thanks,
> 
> R.
> 

-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to