So, I was working from a completely fresh virtualenv, installing a package
that had a matplotlib dependency. As it happens to be, the dependencies in
this package lists matplotlib prior to numpy, so matplotlib got processed
first. For whatever reason, while processing matplotlib, it didn't seem to
Unfortunately, this is a known bug in setuptools. It has no concept of
"build time" dependencies, so it probably computed all of the
dependencies correctly, but it doesn't install them in the correct order
-- it just assumes that as long as everything gets installed it will
work when it's fina
There is setup_requires, and from the documentation that I see, I wonder if
listing NumPy in both build_requires and install_requires invokes a special
handling to install setup requirements in the same place as install
requirements?
Ben
This thread from h5py may be relevant (https://github.com/h5py/h5py/pull/356).
Tom
On Fri, Sep 20, 2013 at 9:41 AM, Benjamin Root wrote:
> There is setup_requires, and from the documentation that I see, I wonder
> if listing NumPy in both build_requires and install_requires invokes a
> specia
On 09/20/2013 10:41 AM, Benjamin Root wrote:
There is setup_requires, and from the documentation that I see, I
wonder if listing NumPy in both build_requires and install_requires
invokes a special handling to install setup requirements in the same
place as install requirements?
Ben
Wow --
See #2445.
On 09/20/2013 11:03 AM, Michael Droettboom wrote:
On 09/20/2013 10:41 AM, Benjamin Root wrote:
There is setup_requires, and from the documentation that I see, I
wonder if listing NumPy in both build_requires and install_requires
invokes a special handling to install setup requiremen
Hello
While working on my multi-figure-backend I found an error in DialogLineprops
If you transform the example
matplotlib/examples/user_interfaces/lineprops_dialog_gtk.py
to use the Gtk3 backend you get with a nice error
Traceback (most recent call last):
File
"/home/fariza/workspace/matplot
