Home
minitage, python and UCS
While upgrading my gentoo based laptop after 8monthes of lazy abandonness in profit of exiting projects, i saw that the gentoo's python was forced to use UCS==4.
What an heck while dealing with the 'minitage env' file which mix the system and project environment resulting in a mixin of the system and project python.
Normally, there are no problem, unless your pythons come with different UCS flavors.
Cool thing is that those errors are not silent, and you see them if you are hitted by this flaw :
minitage & ohloh gives us minitage.ohloh
I refreshed a little the ohloh minitage's related page to have some marketing analysis around minitage basecode.
For this, i wanted to add all repositories, what a heck for 200 repos...
Time to create minitage.ohloh to create the repositories for me using some fake browser ;-).
This package uses lxml (XPath), zope.testbrowser (fake browser) and urllib (some handmade http requests) to make the work done.
Python and oldies or ValueError: year=1876 is before 1900; the datetime strftime() methods require year >= 1900
Calling strftime on a date/datetime instance on py24/py26 will raise a value error like this:
>>> from datetime import date
>>> date(1800,1,1).strftime('%d%m%Y')
Traceback (most recent call last):
File "", line 1, in
ValueError: year=1800 is before 1900; the datetime strftime() methods require year >= 1900 Quite annoying heh ?
There is a bug related on the python bugtracker here : http://bugs.python.org/issue1777412
Recent blog posts
- minitage, python and UCS
- minitage & ohloh gives us minitage.ohloh
- Python and oldies or ValueError: year=1876 is before 1900; the datetime strftime() methods require year >= 1900
- little minitage.core improvments
- Snowleopard revival
- Webservers flooding minitage
- hudson deployment made easy
- A more simple editorial process in Plone: Classic CMS + InPlace Topic view
- A more simple editorial process in Plone: Classic CMS + InPlace Topic view
- Personal reminder about Drupal's settings.php
