check pylab before upcoming release

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 wouldn't be surprised if more subtle differences or bugs were introduced by different versions. I understand the argument for this for the bigger packages, but pyparsing isn't that many lines of code, and is a single file. I don't know if the saved disk space and bandwidth is worth the extra maintenance and support effort. I would much prefer to write for a single version of pyparsing that we can verify works.

Cheers,
Mike

OK, I'll move it back into matplotlib then.

···

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
at even minor releases. Worse, given the complexity of the interface, I
wouldn't be surprised if more subtle differences or bugs were introduced by
different versions. I understand the argument for this for the bigger
packages, but pyparsing isn't that many lines of code, and is a single
file. I don't know if the saved disk space and bandwidth is worth the
extra maintenance and support effort. I would much prefer to write for a
single version of pyparsing that we can verify works.

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, pyparsing has changed APIs
at even minor releases. Worse, given the complexity of the interface, I
wouldn't be surprised if more subtle differences or bugs were introduced by
different versions. I understand the argument for this for the bigger
packages, but pyparsing isn't that many lines of code, and is a single
file. I don't know if the saved disk space and bandwidth is worth the
extra maintenance and support effort. I would much prefer to write for a
single version of pyparsing that we can verify works.

OK, I'll move it back into matplotlib then.

Thanks. Hope it isn't too much trouble to undo those changes. (Sorry for the gruff e-mail. I shouldn't e-mail before my morning coffee...)

Cheers,
Mike

--
Michael Droettboom
Science Software Branch
Operations and Engineering Division
Space Telescope Science Institute
Operated by AURA for NASA