Re: [sage-devel] Re: new layout breaks sagenb development?
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 merged this. -- 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 http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
Re: [sage-devel] Re: new layout breaks sagenb development?
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 to inside the sagenb/sagenb, instead of having it as
a symbolic link.
- basu.
On Tue, Apr 8, 2014 at 11:21 PM, Jonathan gu...@uwosh.edu wrote:
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, April 8, 2014 10:07:30 AM UTC-5, kcrisman wrote:
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 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 is in ~/sage and sagenb is in ~/sagenb:
$ cd ~/sagenb/sagenb
$ rm flask_version
$ mv ../flask_version .
$ cd ~/sage/local/lib/python/site-packages/sagenb-0.10.8.2-py2.7.egg
$ mv sagenb{,-0.10.8.2}
$ ln -s ~/sagenb/sagenb .
And now, you can continue to work on sagenb dev in ~/sagenb.
- basu.
On Tuesday, April 8, 2014 10:33:03 AM UTC+8, kcrisman wrote:
With the new directory layout, http://www.sagemath.org/doc/
developer/sagenb/index.html no longer makes any sense, and I don't see
any easy way to do any sagenb development without making new (s)pkgs. Is
that correct? Any ideas for making this simpler?
Thanks,
- kcrisman
--
You received this message because you are subscribed to a topic in the
Google Groups sage-devel group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/sage-devel/B7PpXa2VFQs/unsubscribe.
To unsubscribe from this group and all its topics, 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 http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.
--
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 http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.
Re: [sage-devel] Re: new layout breaks sagenb development?
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) because I didn't know what (and didn't want to deal with) other
things might be affected if I actually moved that directory. However, it
should probably be physically moved, and not just linked.
On Tue, Apr 8, 2014 at 8:30 AM, P Purkayastha ppu...@gmail.com wrote:
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 to inside the sagenb/sagenb, instead of having it as
a symbolic link.
- basu.
On Tue, Apr 8, 2014 at 11:21 PM, Jonathan gu...@uwosh.edu wrote:
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, April 8, 2014 10:07:30 AM UTC-5, kcrisman wrote:
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 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 is in ~/sage and sagenb is in ~/sagenb:
$ cd ~/sagenb/sagenb
$ rm flask_version
$ mv ../flask_version .
$ cd ~/sage/local/lib/python/site-packages/sagenb-0.10.8.2-py2.7.egg
$ mv sagenb{,-0.10.8.2}
$ ln -s ~/sagenb/sagenb .
And now, you can continue to work on sagenb dev in ~/sagenb.
- basu.
On Tuesday, April 8, 2014 10:33:03 AM UTC+8, kcrisman wrote:
With the new directory layout, http://www.sagemath.org/doc/
developer/sagenb/index.html no longer makes any sense, and I don't
see any easy way to do any sagenb development without making new (s)pkgs.
Is that correct? Any ideas for making this simpler?
Thanks,
- kcrisman
--
You received this message because you are subscribed to a topic in the
Google Groups sage-devel group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/sage-devel/B7PpXa2VFQs/unsubscribe.
To unsubscribe from this group and all its topics, 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 http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.
--
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 http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.
--
Andrew
--
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 http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.
Re: [sage-devel] Re: new layout breaks sagenb development?
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, Apr 8, 2014 at 11:35 PM, R. Andrew Ohana andrew.oh...@gmail.comwrote:
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) because I didn't know what (and didn't want to deal with) other
things might be affected if I actually moved that directory. However, it
should probably be physically moved, and not just linked.
On Tue, Apr 8, 2014 at 8:30 AM, P Purkayastha ppu...@gmail.com wrote:
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 to inside the sagenb/sagenb, instead of having it as
a symbolic link.
- basu.
On Tue, Apr 8, 2014 at 11:21 PM, Jonathan gu...@uwosh.edu wrote:
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, April 8, 2014 10:07:30 AM UTC-5, kcrisman wrote:
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 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 is in ~/sage and sagenb is in ~/sagenb:
$ cd ~/sagenb/sagenb
$ rm flask_version
$ mv ../flask_version .
$ cd ~/sage/local/lib/python/site-packages/sagenb-0.10.8.2-py2.7.egg
$ mv sagenb{,-0.10.8.2}
$ ln -s ~/sagenb/sagenb .
And now, you can continue to work on sagenb dev in ~/sagenb.
- basu.
On Tuesday, April 8, 2014 10:33:03 AM UTC+8, kcrisman wrote:
With the new directory layout, http://www.sagemath.org/doc/
developer/sagenb/index.html no longer makes any sense, and I don't
see any easy way to do any sagenb development without making new (s)pkgs.
Is that correct? Any ideas for making this simpler?
Thanks,
- kcrisman
--
You received this message because you are subscribed to a topic in the
Google Groups sage-devel group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/sage-devel/B7PpXa2VFQs/unsubscribe.
To unsubscribe from this group and all its topics, 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 http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.
--
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 http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.
--
Andrew
--
You received this message because you are subscribed to a topic in the
Google Groups sage-devel group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/sage-devel/B7PpXa2VFQs/unsubscribe.
To unsubscribe from this group and all its topics, 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 http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.
--
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 http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.
