Re: [sage-devel] Re: new layout breaks sagenb development?

2014-08-21 Thread kcrisman
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. > >

Re: [sage-devel] Re: new layout breaks sagenb development?

2014-04-08 Thread P Purkayastha
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 Tue

Re: [sage-devel] Re: new layout breaks sagenb development?

2014-04-08 Thread R. Andrew Ohana
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) be

Re: [sage-devel] Re: new layout breaks sagenb development?

2014-04-08 Thread P Purkayastha
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 flask_version