I have set up a pull request to move the flask_version directory to inside
sagenb.
The documentation can be fixed later, but this should enable anyone to
start working on sagenb dev immediately. I also checked that the newly
generated sagenb tarball installs and works correctly.
I've
There is an easy fix. The main reason why it has broken sagenb development
is because sagenb/sagenb/flask_version is a symbolic link to
sagenb/flask_version - I do not know why it is set up like this. So,
doing the following will allow you to work on sagenb dev - I will assume
that your sage
Hey Basu, thanks! That sounds great.
Can you open a ticket to fix the developer guide with this information (the
last section on sagenb development)? (Suitably generic, of course.)
- kcrisman
On Tuesday, April 8, 2014 10:45:24 AM UTC-4, P Purkayastha wrote:
There is an easy fix. The
Another solution that works is to work with a separate sagenb git
repository and then rename the directory sagenb inside the egg to something
like sagenb_old. Then create a symlink to your development git repository
named sagenb. This is almost the same solution as Basu's.
On Tuesday,
Hello Jonathan,
In my experience, making a symbolic link to the root of the sagenb
directory does not work. Making a symbolic link to the sagenb directory
*inside the sagenb root* also does not work.
My suggestion would be to change the layout of the sagenb root directory
and move
The symbolic link exists for the sole reason that previously you could not
install sagenb as a standard python package (it cared deeply about its
location in the SAGE_ROOT); this was necessary for getting sagenb to
initially work on the git version of Sage. The symbolic link was made (as a
hack)
I have set up a pull request to move the flask_version directory to inside
sagenb.
The documentation can be fixed later, but this should enable anyone to
start working on sagenb dev immediately. I also checked that the newly
generated sagenb tarball installs and works correctly.
- basu.
On
