On Sat, Jun 29, 2013 at 2:18 PM, Nathaniel Smith wrote:
> pip *will* nuke old
> versions for you, and thus gives you a better chance of importing the
> code that was actually shipped.
>
Thanks Nathaniel, I didn't realise pip could snarf a local checkout.
That's good to know.
--
Damon McDouga
On Sat, Jun 29, 2013 at 4:10 PM, Benjamin Root wrote:
> Perhaps it would be a good idea to exercise the mpl toolkits with this
> since it is more likely for them to do more esoteric things with axes.
> Don't forget Base map and possibly cartopy and pandas.
>
Thanks Ben. I already did some playi
Perhaps it would be a good idea to exercise the mpl toolkits with this
since it is more likely for them to do more esoteric things with axes.
Don't forget Base map and possibly cartopy and pandas.
Cheers!
Ben Root
On Jun 28, 2013 5:20 PM, "Nelle Varoquaux"
wrote:
> Hello pythonistas,
>
> We've j
On Sat, Jun 29, 2013 at 8:13 PM, Damon McDougall
wrote:
> To reiterate, remember that you'll need to nuke your previous local install.
> Installing over an existing mpl distribution will cause problems. This is
> because `python setup.py install` will not remove the old axes.py for you.
NB th
On Fri, Jun 28, 2013 at 5:20 PM, Nelle Varoquaux
wrote:
> Hello pythonistas,
>
> We've just finished refactoring the axes module at the scipy sprint, and
> before merging we would like to inform developers of the changes. The axes
> module contained more than 9k loc, and a few classes. It used to
Hello pythonistas,
We've just finished refactoring the axes module at the scipy sprint, and
before merging we would like to inform developers of the changes. The axes
module contained more than 9k loc, and a few classes. It used to be a file.
Now, it became a folder called "axes". This module con
