Eric Firing wrote:
> A new mpl release is coming soon. One of the changes is that there is a
> new matplotlib.pyplot module that has only the plotting parts of the
> pylab interface. The pylab module still imports from oldnumeric, so it
> still has the old Numeric-style upper case types (Float
Darren Dale wrote:
> On Friday 09 November 2007 07:25:09 am Michael Droettboom wrote:
>> Darren wrote:
>> * Use the system pyparsing, if available. If not, install pyparsing like we
>> do with pytz and dateutil. matplotlib.pyparsing is gone.
>>
>> That seems like a bad idea. In my experience, pypa
On Friday 09 November 2007 07:25:09 am Michael Droettboom wrote:
> Darren wrote:
> * Use the system pyparsing, if available. If not, install pyparsing like we
> do with pytz and dateutil. matplotlib.pyparsing is gone.
>
> That seems like a bad idea. In my experience, pyparsing has changed APIs
> a
Darren wrote:
* Use the system pyparsing, if available. If not, install pyparsing like we do
with pytz and dateutil. matplotlib.pyparsing is gone.
That seems like a bad idea. In my experience, pyparsing has changed APIs at
even minor releases. Worse, given the complexity of the interface, I wo
A new mpl release is coming soon. One of the changes is that there is a
new matplotlib.pyplot module that has only the plotting parts of the
pylab interface. The pylab module still imports from oldnumeric, so it
still has the old Numeric-style upper case types (Float64 instead of
float64, etc