On May 11, 2010, at 10:56 AM, kcrisman <kcris...@gmail.com> wrote:
>
>
> On May 11, 11:22 am, Jason Grout <jason-s...@creativetrax.com> wrote:
>> On 05/11/2010 01:45 AM, Tim Joseph Dumol wrote:
>>
>>
>>
>>
>>
>>> On Tue, May 11, 2010 at 5:47 AM, Jason Grout
>>> <jason-s...@creativetrax.com <mailto:jason-s...@creativetrax.com>> wrote:
>>
>>> On 05/10/2010 01:27 PM, Tim Joseph Dumol wrote:
>>
>>> Hi,
>>
>>> The latest sagenb package is included in Sage 4.4.1
>>> (sagenb-0.8.p0.spkg). Then, extract and install it, then develop
>>> as usual.
>>
>>> $ tar -xvf sagenb-0.8.p0.splg
>>> $ cd sagenb-0.8.p0/src/sagenb/
>>> $ sage -python setup.py install && sage -python setup.py develop
>>
>>> `setup.py develop` allows you to develop on the package without
>>> needing
>>> to reinstall the package or rebuild Sage.
>>
>>> What is the possibility of just copying the repository to the
>>> site-packages/sagenb directory? Then someone could just go into
>>> that directory ($SAGE_ROOT/local/lib/python2.6/site-packages/...)
>>> and start making changes, check the log, etc.
>>
>>> It's rather non-standard to do work directly in site-packages/*. I'd be
>>> much more comfortable with copying the repository to something like
>>> $SAGE_ROOT/devel/sagenb/ or something like that, and running `$sage
>>> -python setup.py install && sage -python setup.py develop` on package
>>> install. It would be trivial to create an hg_sagenb class wrapper once
>>> that's done. I'd love to hear other people's opinion on this.
>>
>> +1 to making a directory in devel that contains the notebook code so
>> that the development process is much more standardized (e.g., go to a
>> directory in devel and work with normal mercurial commands).
>>
>
> Yes, this is exactly the kind of thing I had in mind. Things that are
> really just for Sage should be part of the standard Sage devel
> process. (Now we just need an hg_pynac to make it complete...)
> Thanks for considering it!
>
> - kcrisman
The notebook is *not* just for sage.
There is a pynac hg repo in the pynac spkg.
Anyway, best is a more supported way to automate the 3 lines Tim posted above,
e.g.,
sage -i --devel pkg_name
would install and setup the given package in a way for doing development.
>
> --
> To post to this group, send an email to sage-devel@googlegroups.com
> To unsubscribe from this group, send an email to
> sage-devel+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/sage-devel
> URL: http://www.sagemath.org
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sage-devel+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org
