Pytz 2013b Fails with PIP 1.4

UPDATE: Pytz is now using a numeric naming convention (i.e. 2013.7) which fixes this bug.

The latest version of PIP only installs stable versions by default, meaning anything with a pre-release version name will be ignored. Unfortunately the Pytz naming convention looks like a beta release (2013b) when it is actually the second release of 2013.

More on this bug can be found here:

For now the workaround is to add the version when installing:

pip install pytz==2013b

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s