#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 | cb0cc8d05f54c07197b01a5ae3f4f61cb7bcb212
Dependencies: #20344 | Stopgaps:
-------------------------------------+-------------------------------------
Comment (by kcrisman):
Okay, finally back to this. I didn't get the mismatch but I did get
#18969. In fact, I seem to still get that problem no matter what I do.
Likely because of this:
{{{
(/Users/.../Library/texmf/tex/generic/sagetex/sagetex.sty
Package: sagetex 2012/01/16 v2.3.3-69dcb0eb93de embedding Sage into LaTeX
docum
ents
}}}
I had to do a lot of work to completely remove that from my system, I'm
not sure why (maybe having several terminals open at once messed something
up, though I've never had that happen before).
Then I finally get the version mismatch, but now the opposite one you get,
I think, which is that I am finally generating using the right SageTeX but
not the right Sage.
{{{
sagetex.VersionError: versions of .sty and .py files do not match.
example.sagetex.sage was generated by sagetex.sty version "2015/08/26
v3.0-92d9f7a", but
is being processed by sagetex.py version "2012/01/16 v2.3.3-69dcb0eb93de".
Please make sure that TeX is using the sagetex.sty
from your current version of Sage; see
http://www.sagemath.org/doc/installation/sagetex.html.
}}}
By the way, this message you referring to being outdated is fixed in
upstream master but not in 3.0, I believe - see comment:28.
Anyway, it seems that I have
{{{
$ ls local/lib/python/site-packages/sage[tab]
sage/ sage_setup/
sage-7.0-py2.7.egg-info sagenb-0.11.7-py2.7.egg/
sage-7.1.beta1-py2.7.egg-info sagetex-2.3.4-py2.7.egg-info
sage-7.1.beta3-py2.7.egg-info sagetex-3.0-py2.7.egg-info
sage-7.1.beta6-py2.7.egg-info sagetex.py
sage-7.2.beta3-py2.7.egg-info sagetex.pyc
sage-7.2.beta4-py2.7.egg-info
}}}
and I think that the extra sagetex.py maybe is the problem? It certainly
is the old one, I checked. But moving this just caused Sage to say it
couldn't import the module sagetex, so it must be in the right place! And
I've already `sage -f` a few times the correct sagetex, and make does
nothing relevant here, apparently, though I tried that too afterwards.
So now I have a non-functioning SageTeX and I can't for the life of me
figure out how to get the right file in that place. And feel like I've
wasted quite a bit of time I really didn't have because of comment:15
asking for help ... if someone has an idea on what I'm doing wrong, I may
have time Tuesday, or just possibly Monday, sorry it can't be earlier.
--
Ticket URL: <http://trac.sagemath.org/ticket/19072#comment:32>
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.
