parsedatetime

Nothing like someone using your code to really make you want to fix it :)

For the past couple of weeks Darshana has been using, breaking and refactoring parsedatetime. Her changes have really shaken out the weak points and helped expand what the code does. Some of the changes are very Chandler specific but I’ve been trying to merge them into my code-base in as generic a manner as possible. It helps that no one uses this code yet because we have broken the API a number of times :)

Also because of this use I’ve had to get serious about packaging as the code is now listed as a dependency for Chandler and since I’m the build person I have no one to blame but myself for any build/integration issues!

Now that I’ve done some of the dirty work you can get parsedatetime as either a source tarball or a Python egg and the source is available via SVN from code.google.com. I’m not quite ready yet to put it up on Python’s Package Index as that gets a little too much visibility right now and I don’t think I’m ready for a public peer review.

Some of the changes Darshana has made has moved more constant text back into the main code so I know I have to make a round of refactoring to move it back to the consts module - otherwise localization will be impossible. Also in the i18n context I really want to look into having the consts module sense if PyICU is available and use if if so - this will make it more robust (I hope.)


Mentions