[sage-devel] Re: Developing sage-based code out of tree

2016-06-08 Thread leif
Erik Bray wrote: > On Tue, Jun 7, 2016 at 12:04 PM, Nathan Dunfield wrote: >>> While this might work for simple projects, this won't work when you need >>> the metadata that cythonize() adds. For example, anything using >>> cysignals really must use cythonize(), it won't work otherwise. >> >> >> J

Re: [sage-devel] Re: Developing sage-based code out of tree

2016-06-07 Thread Nathan Dunfield
> > That made me think that sage fails to set everything required to let > "--user" work properly (I noticed installation path names containing > ".../.sage/..." so at least it was trying something distinct from what > python would do in a standard config.) > Hmmm, I install Python packages in

Re: [sage-devel] Re: Developing sage-based code out of tree

2016-06-07 Thread Nils Bruin
On Tuesday, June 7, 2016 at 8:18:04 AM UTC-7, William wrote: > > The standard way to build in place but have things written to a search > path is > > python setup.py develop --user > > Yes, initially I tried a version of that (perhaps with "install" rather than "develop"), but it didn't w

Re: [sage-devel] Re: Developing sage-based code out of tree

2016-06-07 Thread Erik Bray
On Tue, Jun 7, 2016 at 11:17 AM, William Stein wrote: > On Tue, Jun 7, 2016 at 11:14 AM, Nils Bruin wrote: >> On Sunday, June 5, 2016 at 12:59:57 PM UTC-7, Nils Bruin wrote: >>> >>> The problem arose specifically when I was looking at >>> https://github.com/abelfunctions/abelfunctions which packa

Re: [sage-devel] Re: Developing sage-based code out of tree

2016-06-07 Thread William Stein
On Tue, Jun 7, 2016 at 11:14 AM, Nils Bruin wrote: > On Sunday, June 5, 2016 at 12:59:57 PM UTC-7, Nils Bruin wrote: >> >> The problem arose specifically when I was looking at >> https://github.com/abelfunctions/abelfunctions which packages itself as an >> spkg. Obviously, I didn't want to install

[sage-devel] Re: Developing sage-based code out of tree

2016-06-07 Thread Nils Bruin
On Sunday, June 5, 2016 at 12:59:57 PM UTC-7, Nils Bruin wrote: > > The problem arose specifically when I was looking at > https://github.com/abelfunctions/abelfunctions which packages itself as > an spkg. Obviously, I didn't want to install this (when trying it out!) in > a system-wide sage, bu

[sage-devel] Re: Developing sage-based code out of tree

2016-06-05 Thread Volker Braun
Make a python package with a setup.py that cythonizes your own code and installs it as nils_module. To use it, use something like "from nils_module.all import *". Ideally you'd be able to create a new virtualenv from sage's python but that doesn't work right now. On Sunday, June 5, 2016 at 3: