#19072: upgrade SageTeX to version 3.0
-------------------------------------+-------------------------------------
Reporter: ddrake | Owner:
Type: defect | Status: needs_review
Priority: blocker | Milestone: sage-7.2
Component: packages: | Resolution:
standard | Merged in:
Keywords: | Reviewers:
Authors: Dan Drake | Work issues:
Report Upstream: N/A | Commit:
Branch: public/19072 | bd2f050f6aa23a3e759f6e48a7a0f5ae9aeab552
Dependencies: #20344 | Stopgaps:
-------------------------------------+-------------------------------------
Comment (by kcrisman):
>
> > is being processed by sagetex.py version "2012/01/16
v2.3.3-69dcb0eb93de".
> this is old version, an up to date version of Sage should have v.2.3.4.
>
Then I am ''really'' confused.
> it's not "extra", it's the right one; however, it must be the same as in
`local/lib/python2.7/site-packages/sage`. This is because
`local/lib/python` is a symbolic link to `local/lib/python2.7`.
> (or at least it should be - if it is not then your installation must be
seriously
> broken, and `make distclean` is the only way out, IMHO...)
Yes yes, I just was too lazy to type the 2.7 when tab-completing.
However,
{{{
__version__ = """
[2012/01/16 v2.3.3-69dcb0eb93de embedding Sage into LaTeX documents]
""".strip()
}}}
so indeed I still have 2.3.3 in there and not 2.3.4, which I don't
understand.
>
> You can see what `sage -f sagetex` is doing by inspecting
`logs/pkgs/sagetex-*`.
> For me, I see the following lines there:
> {{{
> copying build/lib/sagetex.py -> <mysageroot>/local/lib/python2.7/site-
packages
> byte-compiling <mysageroot>/local/lib/python2.7/site-packages/sagetex.py
to sagetex.pyc
> }}}
>
No! Unfortunately not.
{{{
Found local metadata for sagetex-3.0
Using cached file /Users/.../sage/upstream/sagetex-3.0.tar.gz
sagetex-3.0
====================================================
Setting up build directory for sagetex-3.0
Finished set up
****************************************************
Host system:
Darwin gc04855.home 11.4.2 Darwin Kernel Version 11.4.2: Thu Aug 23
16:25:48 PDT 2012; root:xnu-1699.32.7~1/RELEASE_X86_64 x86_64
****************************************************
C compiler: gcc
C compiler version:
Using built-in specs.
COLLECT_GCC=/Users/.../sage/local/bin/gcc
COLLECT_LTO_WRAPPER=/Users/.../sage/local/libexec/gcc/x86_64-apple-
darwin11.4.2/4.9.3/lto-wrapper
Target: x86_64-apple-darwin11.4.2
Configured with: ../src/configure
--prefix=/Users/karl.crisman/Downloads/sage/local --with-local-
prefix=/Users/.../sage/local --wit$
Thread model: posix
gcc version 4.9.3 (GCC)
****************************************************
running install
running build
running build_py
creating build
creating build/lib
copying sagetex.py -> build/lib
running install_lib
running install_data
running install_egg_info
Removing /Users/.../sage/local/lib/python2.7/site-
packages/sagetex-3.0-py2.7.egg-info
Writing /Users/.../sage/local/lib/python2.7/site-
packages/sagetex-3.0-py2.7.egg-info
}}}
So as you can see, for some reason it's not copying anything into
`SAGE_ROOT/local/lib/python2.7/site-packages. Huh. Any ideas? I don't
want to waste time trying stuff if you have a better idea - I don't think
that your latest commit would do anything related to this, though, it
would only clear out old stuff.
--
Ticket URL: <http://trac.sagemath.org/ticket/19072#comment:39>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica,
and MATLAB
--
You received this message because you are subscribed to the Google Groups
"sage-trac" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/sage-trac.
For more options, visit https://groups.google.com/d/optout.
