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.