User:Tobiasco/Python projects and date formats
Jump to navigation
Jump to search
For the Django failure with storing date formats see: User:Tobiasco/UTC is the wrong way
2009-10-27
Parts of an email to webmaster@python.org
surfing http://www.python.org/doc/versions/ 27 June 2009 http://www.python.org/doc/3.1/ Oct 27, 2009 http://www.python.org/doc/3.1/whatsnew/3.1.html October 27, 2009 brings three different date formats. I think people will never manage to be consistent except if they use ISO 8601 the international date format. YYYY-MM-DD I read Python tries to have clear (beauty) code. Maybe that should be applied to the website too? Proposing usage of ISO 8601 at python.org I also have in mind that sites related to python may follow. One could easier convince them, by saying look, python.org does it like that too. Let's all join. E.g. http://www.djangoproject.com/weblog/ August 19, 2009 http://code.djangoproject.com/wiki/RecentChanges 10/27/09
Parts of another email from the same day
http://pypi.python.org/pypi 2009-10-27 is already YYYY-MM-DD http://mail.python.org/pipermail/advocacy/2009-October/thread.html offers one more variant: Thu Oct 8 15:49:27 CEST 2009
2009-10-28
Parts of an email to webmaster@python.org
found one more format: http://python.org/ Sun, 25 Oct 2009 22:17:00 -0500
2011-01-25
Parts of an email to http://wiki.python.org/moin/ChrisMcDonough, which was the user given in "last modified by" http://wiki.python.org/moin/WebFrameworks?action=info
On http://wiki.python.org/moin/WebFrameworks I suggest to change Tipfy (0.5.6 Available on 30-Jun-2010) ->2010-06-30 Spark (0.2.1 Released 2006-9-15) -> 2006-09-15 Wasp (2.00 Released 2007.07) -> 2007-07 web2py Version 1.87.3 (2010-Oct-13) -> 2010-10-13
2012-07-04
Parts of an email to Veit Schiele
you are given as contact for several pypi pages named http://pypi.python.org/pypi/vs.<name> The pages use four different date formats, and only one uses a single ISO 8601 format, namely YYYY-MM-DD, exclusively. http://www.python.org/dev/peps/pep-0020/ "There should be one-- and preferably only one --obvious way to do it." I suggest to switch all to YYYY-MM-DD to improve internal consistency. ---------- YYYY-MM-DD http://pypi.python.org/pypi/vs.dashboardmanager 0.3.4 (2011-03-30) ---------- DD.MM.YYYY, YYYY-MM-DD + YYYY-MM-DD (upload section) http://pypi.python.org/pypi/vs.genericsetup.ldap 1.2 (2011-06-16) 1.1.1 (2010/10/25) http://pypi.python.org/pypi/vs.event 0.3.0 - (2011-12-05) 0.2.19 - (2009/11/10) ---------- DD.MM.YYYY + YYYY-MM-DD (upload section) http://pypi.python.org/pypi/vs.jquerybookmarks/ 0.1.5 (02.06.2012) ---------- DD/MM/YYYY + YYYY-MM-DD (upload section) http://pypi.python.org/pypi/vs.contentpopup/ 0.2.4 (17/04/2012) ---------- YYYY/MM/DD + YYYY-MM-DD (upload section) http://pypi.python.org/pypi/vs.tdi/ 0.3.2 (19.03.2012) http://pypi.python.org/pypi/vs.flexigridsearch 1.0.0 (2011/06/09) http://pypi.python.org/pypi/vs.org 1.0.9 (2012/03/30)