On Fri, 15 Dec 2006 12:24:07 -0800, Nick Alexander <[EMAIL PROTECTED]> wrote:
> I have a file sage/misc/sageinspect.py. I touch it, but sage -b
> reports no changes.
>
> leeto:~/Devel/sage/devel/sage-was nalexand$ touch sage/misc/
> sageinspect.py
> leeto:~/Devel/sage/devel/sage-was nalexand$ sage -b
>
> ----------------------------------------------------------
> sage: Building and installing modified SAGE library files.
>
> running install
> running build
> running build_py
> running build_ext
> running install_lib
> running install_egg_info
> Removing /Users/nalexand/Devel/sage/local/lib/python2.5/site-packages/
> sage-0.0.0-py2.5.egg-info
> Writing /Users/nalexand/Devel/sage/local/lib/python2.5/site-packages/
> sage-0.0.0-py2.5.egg-info
>
> And the file is not in the site-packages directory:
>
> leeto:~/Devel/sage/devel/sage-was nalexand$ ls ~/Devel/sage/local/lib/
> python2.5/site-packages/sage/misc/sageinspect*
> ls: /Users/nalexand/Devel/sage/local/lib/python2.5/site-packages/sage/
> misc/sageinspect*: No such file or directory
>
> It is in build. If I touch it, nothing changes:
>
> leeto:~/Devel/sage/devel/sage-was nalexand$ ls build/lib.macosx-10.3-
> ppc-2.5/sage/misc/
> __init__.py functional.py preparser_ipython.py
> all.py getusage.py profiler.py
> attach.py hg.py proof.py
> banner.py html.py python.py
> benchmark.py interpreter.py sage_eval.py
> bug.py latex.py sagedoc.py
> cache.py log.py sageinspect.py
> cachefunc.py mathml.py sagex.py
> copying.py misc.py sagex_c.so
> darcs.py mrange.py search.so
> db.py multireplace.py sh.py
> defaults.py package.py test.py
> dist.py pager.py trace.py
> file_to_worksheet.py persist.py typecheck.py
> func_persist.py preparser.py viewer.py
> leeto:~/Devel/sage/devel/sage-was nalexand$ touch build/
> lib.macosx-10.3-ppc-2.5/sage/misc/sageinspect.py
> leeto:~/Devel/sage/devel/sage-was nalexand$ sage -b
>
> ----------------------------------------------------------
> sage: Building and installing modified SAGE library files.
>
> running install
> running build
> running build_py
> running build_ext
> running install_lib
> running install_egg_info
> Removing /Users/nalexand/Devel/sage/local/lib/python2.5/site-packages/
> sage-0.0.0-py2.5.egg-info
> Writing /Users/nalexand/Devel/sage/local/lib/python2.5/site-packages/
> sage-0.0.0-py2.5.egg-info
>
> real 0m4.668s
> user 0m1.245s
> sys 0m2.793s
>
> How do I get it to pick up that file?
>
> I did sage -upgrade after adding it (and having it all work), so
> something in the patches must have screwed things up. Maybe I need
> to clean the existing build and start again?
The possible problems include the following:
(1) you're running the wrong version of SAGE, i.e., you should
be running ~/Devel/sage/sage. Are you?
(2) When you upgrade it always switches the current sage branch to main first,
so sage/devel/sage points to sage-main. If so, then "sage -b" only
looks at sage-main. Type "sage -b was" to switch back to the was branch
(which is *not* upgraded -- to upgrade that, type "hg_sage.pull()" from
in SAGE).
(3) Remark -- for .py files you just put them in any directory under
devel/sage/sage
that has __init__.py in it (already) and they are automatically
detected. You don't have to put them under revision control.
William
--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/sage-support
URLs: http://sage.math.washington.edu/sage/ and http://sage.scipy.org/sage/
-~----------~----~----~----~------~----~------~--~---
