I installed using version 1.3.1 windows binary
"matplotlib-1.3.1.win32-py2.7.exe" from mathplotlib download. Installation
went fine, but when using the package, it says "dateutil" and "pyparsing"
are missing, which are supposed to be bundled according to the installation
instruction. Is this a bug or expected behavior from now on? I did not have
this issue for earlier versions of matplotlib.
My base python is 2.7.8.
If anyone is having the issue, either download the binaries from pythonlibs
mentioned above, or
install from the sources, which I did as follows:
(1) Install setuptools if you don't have it.
Download source from https://pypi.python.org/pypi/setuptools;
Unpack and run 'ez_setup.py install'; or 'python ez_setup.py install'
This will install setuptools.
(2) Install any other package by downloading the source, unpacking, and
running 'setup.py install'
e.g., "dateutil" has been installed this way. https://pypi.python.org/pypi/python-dateutil, same for pyparsing
Hey, even I had similar issue.
Later I learnt python2.7 could support matplotlib version1.0.1 only.
So if you want to upgrade your matplotlib, you first need to upgrade your python.
···
On Thu, Jul 3, 2014 at 7:05 AM, jw <gwgo@…4472…> wrote:
I installed using version 1.3.1 windows binary
“matplotlib-1.3.1.win32-py2.7.exe” from mathplotlib download. Installation
went fine, but when using the package, it says “dateutil” and “pyparsing”
are missing, which are supposed to be bundled according to the installation
instruction. Is this a bug or expected behavior from now on? I did not have
this issue for earlier versions of matplotlib.
My base python is 2.7.8.
If anyone is having the issue, either download the binaries from pythonlibs
mentioned above, or
install from the sources, which I did as follows:
(1) Install setuptools if you don’t have it.
Download source from [https://pypi.python.org/pypi/setuptools](https://pypi.python.org/pypi/setuptools);
Unpack and run 'ez_setup.py install'; or 'python ez_setup.py install'
This will install setuptools.
(2) Install any other package by downloading the source, unpacking, and
running 'setup.py install'
e.g., "dateutil" has been installed this way.
[https://pypi.python.org/pypi/python-dateutil](https://pypi.python.org/pypi/python-dateutil), same for pyparsing
One possibility is that with v1.3, we changed how packaging was done. Unfortunately, this did cause some transitional issues. The best bet is to uninstall all versions of matplotlib, pylab, and mpl_toolkits first, then re-install v1.3.1. Note that waiting for the v1.4 release wouldn’t necessarily solve anything as it is the transition from older versions of matplotlib that is the issue rather than transitioning to newer versions.
Hopefully this helps,
Ben Root
···
On Wed, Jul 2, 2014 at 9:35 PM, jw <gwgo@…4472…> wrote:
I installed using version 1.3.1 windows binary
“matplotlib-1.3.1.win32-py2.7.exe” from mathplotlib download. Installation
went fine, but when using the package, it says “dateutil” and “pyparsing”
are missing, which are supposed to be bundled according to the installation
instruction. Is this a bug or expected behavior from now on? I did not have
this issue for earlier versions of matplotlib.
My base python is 2.7.8.
If anyone is having the issue, either download the binaries from pythonlibs
mentioned above, or
install from the sources, which I did as follows:
(1) Install setuptools if you don’t have it.
Download source from [https://pypi.python.org/pypi/setuptools](https://pypi.python.org/pypi/setuptools);
Unpack and run 'ez_setup.py install'; or 'python ez_setup.py install'
This will install setuptools.
(2) Install any other package by downloading the source, unpacking, and
running 'setup.py install'
e.g., "dateutil" has been installed this way.
[https://pypi.python.org/pypi/python-dateutil](https://pypi.python.org/pypi/python-dateutil), same for pyparsing
I faced the problem of upgrading my matplotlib to 1.3.1 having my python2.7. Its on Fedora am talking about. Its the dmg file available here http://matplotlib.org/downloads.html
When I checked for upgrading from Terminal, it said matplotlib1.0.1 is the latest version.
···
On Fri, Jul 4, 2014 at 10:52 PM, Goyo <goyodiaz@…287…> wrote:
I presume you mean pypi said that the latest version was 1.0.1? PyPi recently (and rightly so) stopped automatically pull eggs from third-party locations (this is a huge security risk). Version 1.0.1 was the last version that was directly hosted on PyPi because the test suite made the package so much bigger after that version.
There was talk about granting “top-tier” projects like matplotlib and basemap special permission to upload larger eggs to PyPi. I don’t know if that has happened yet.
Cheers!
Ben Root
···
On Fri, Jul 4, 2014 at 2:48 PM, Rachana Katkam <katkam.rachana@…287…> wrote:
I faced the problem of upgrading my matplotlib to 1.3.1 having my python2.7. Its on Fedora am talking about. Its the dmg file available here http://matplotlib.org/downloads.html
When I checked for upgrading from Terminal, it said matplotlib1.0.1 is the latest version.
Open source business process management suite built on Java and Eclipse
Turn processes into business applications with Bonita BPM Community Edition
Quickly connect people, data, and systems into organized workflows
Thanks for pointing it to a packaging issue, as matplotlib works very well
after installing the missing packages.
I don't know really the the issue, but I hope it gets sorted out. The
earlier binaries had everything it needed on windows, so very convenient to
users. I think problems like this could really discourage new users to try,
particularly the inexperienced.
In my case, the matplotlib install was a clean install on a new machine,
though I had used it often on other computers. It was installed after Python
2.7.8, numpy, scipy, and Vpython, so the problem had to be packaging rather
than transitional, it'd would seem.
One possibility is that with v1.3, we changed how packaging was done.
Unfortunately, this did cause some transitional issues. The best bet is to
uninstall *all* versions of matplotlib, pylab, and mpl_toolkits first, then
re-install v1.3.1. Note that waiting for the v1.4 release wouldn't
necessarily solve anything as it is the transition *from* older versions of
matplotlib that is the issue rather than transitioning *to* newer versions.