You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
in WinPython-64bit-3.4.4.1Qt5/$_OUTDIR/python-3.4.4.amd64/Lib/site-packages/matplotlib/mpl-data/matplotlibrc
there is: #text.usetex : False # use latex for all text handling. The following fonts
Would you see it as good to add this hint somewhere in the docs?
Also maybe for WinPython?
Hmm, that would indicate that latex isn't supposed to be used. Perhaps the
full traceback of the original exception and the code to reproduce the
problem?
I should point out that WinPython is a bit weird. What they do is package
various projects from their master branch at arbitrary times. So, while it
gives you near-bleeding-edge versions of various projects, it may also
include bugs that never made it out in a release. This can make debugging
difficult.
Hmm, that would indicate that latex isn't supposed to be used. Perhaps the full traceback of the original exception and the code to reproduce the problem?
No, but about the default value in the rc file, i.e. where to check if someone gets the same error.
Something like: If PDF save does not work, check the rc setting usetex in file...
I should point out that WinPython is a bit weird. What they do is package various projects from their master branch at arbitrary times.
This can make debugging difficult.
I am using it because run into the dependency circle with anaconda. But yes, will convince IT dept. to reinstall that distro.
I think you are missing the point of what I am saying. First, I am not
suggesting that WinPython should be reinstalled. Reinstalling it may or may
not solve your problem. I only point out that it is a bleeding edge distro,
so it has inherent problems. Second, what you are encountering seems to be
a bug of some sort. What you are suggesting as a documentation change isn't
correct. Having usetex=True somewhere and missing latex would cause
problems for any output format, not just PDFs.
Have you found a place where usetex was set to True? So far, all I have
seen is that it is False. If there is no place where usetex is True, then
there is a bug. It would help immensely to have the full traceback of the
exception, and example code that produces your problem.
I should point out that WinPython is a bit weird. What they do is package
various projects from their master branch at arbitrary times.
This can make debugging difficult.
I am using it because run into the dependency circle with anaconda. But
yes, will convince IT dept. to reinstall that distro.
—
Reply to this email directly or view it on GitHub #6104 (comment)
.
I think you are missing the point of what I am saying. First, I am not suggesting that WinPython should >be reinstalled. Reinstalling it may or may not solve your problem.
Sorry, I was not explicit enough. I meant reinstall Anaconda some time.
Have you found a place where usetex was set to True?
Only the line cited above.
It would help immensely to have the full traceback of the
exception, and example code that produces your problem.
I think you are missing the point of what I am saying. First, I am not
suggesting that WinPython should >be reinstalled. Reinstalling it may or
may not solve your problem.
Sorry, I was not explicit enough. I meant reinstall Anaconda some time.
Have you found a place where usetex was set to True?
Only the line cited above.
It would help immensely to have the full traceback of the
exception, and example code that produces your problem.
I think you are missing the point of what I am saying. First, I am not
suggesting that WinPython should >be reinstalled. Reinstalling it may or
may not solve your problem.
Sorry, I was not explicit enough. I meant reinstall Anaconda some time.
Have you found a place where usetex was set to True?
Only the line cited above.
It would help immensely to have the full traceback of the
exception, and example code that produces your problem.
Activity
WeatherGod commentedon Mar 3, 2016
It should not be required unless there are settings that turns it on. Do
you set "usetex=True" anywhere? Perhaps it is in your matplotlibrc file?
On Thu, Mar 3, 2016 at 10:48 AM, DaCoEx notifications@github.com wrote:
dacoex commentedon Mar 3, 2016
Thanks for the reply.
I am using WinPython
in
WinPython-64bit-3.4.4.1Qt5/$_OUTDIR/python-3.4.4.amd64/Lib/site-packages/matplotlib/mpl-data/matplotlibrcthere is:
#text.usetex : False # use latex for all text handling. The following fontsWould you see it as good to add this hint somewhere in the docs?
Also maybe for WinPython?
WeatherGod commentedon Mar 3, 2016
Hmm, that would indicate that latex isn't supposed to be used. Perhaps the
full traceback of the original exception and the code to reproduce the
problem?
I should point out that WinPython is a bit weird. What they do is package
various projects from their master branch at arbitrary times. So, while it
gives you near-bleeding-edge versions of various projects, it may also
include bugs that never made it out in a release. This can make debugging
difficult.
On Thu, Mar 3, 2016 at 1:22 PM, DaCoEx notifications@github.com wrote:
dacoex commentedon Mar 3, 2016
Something like:
If PDF save does not work, check the rc setting usetex in file...
dacoex commentedon Mar 3, 2016
I am using it because run into the dependency circle with anaconda. But yes, will convince IT dept. to reinstall that distro.
WeatherGod commentedon Mar 3, 2016
I think you are missing the point of what I am saying. First, I am not
suggesting that WinPython should be reinstalled. Reinstalling it may or may
not solve your problem. I only point out that it is a bleeding edge distro,
so it has inherent problems. Second, what you are encountering seems to be
a bug of some sort. What you are suggesting as a documentation change isn't
correct. Having usetex=True somewhere and missing latex would cause
problems for any output format, not just PDFs.
Have you found a place where usetex was set to True? So far, all I have
seen is that it is False. If there is no place where usetex is True, then
there is a bug. It would help immensely to have the full traceback of the
exception, and example code that produces your problem.
On Thu, Mar 3, 2016 at 1:44 PM, DaCoEx notifications@github.com wrote:
dacoex commentedon Mar 3, 2016
Sorry, I was not explicit enough. I meant reinstall Anaconda some time.
Only the line cited above.
I run this code:
pylab_examples example code: multipage_pdf.py — Matplotlib 1.5.1 ...
WeatherGod commentedon Mar 3, 2016
The line you point out was commented out. Where was it explicitly set to
True?
On Thu, Mar 3, 2016 at 2:01 PM, DaCoEx notifications@github.com wrote:
WeatherGod commentedon Mar 3, 2016
Ah-ha! That example explicitly sets usetex to True:
plt.rc('text', usetex=True)
On Thu, Mar 3, 2016 at 2:12 PM, Benjamin Root ben.v.root@gmail.com wrote:
dacoex commentedon Mar 3, 2016
OK, you are right. with
plt.rc('text', usetex=False)
works nicely.
In case this happens to others, a hint could be added to:
http://matplotlib.org/api/backend_pdf_api.html
Sorry for this confusion and for wasting your time. And thanks for your help.
WeatherGod commentedon Mar 3, 2016
The hint could be added to the comments for the example. This has nothing
to do with the pdf backend.
It wasn't a waste of time. It revealed a bad assumption in some of our
examples.
On Thu, Mar 3, 2016 at 3:16 PM, DaCoEx notifications@github.com wrote:
simplified, added comment on usetex
dacoex commentedon Mar 4, 2016
OK, as consequence of your last comment I change the example.
added comment on "usetex=False" to ainde debugging when latex not ava…
added comment on "usetex=False" to ainde debugging when latex not ava…
QuLogic commentedon May 22, 2016
Fixed by #6119.