Da ich schon seit Langem immer fleißig die .csv files zu den Rechnungen herunterladen hab ich schnell folgendes Python Script geschrieben das mir die Zählarbeit erleichtert (und Schreikrämpfe in Excel verhindert).

Als kleinen Bonus zählt es auch (etwas inexakt fürchte ich) die Homezone Minuten, daraus kann man ablesen was das Verlieren von Genion für Auswirkungen hat.

# parses .csv files from o2 germany billing
# counts talked minutes ('sprache' in 'ART') and sms sent ('sms' in 'TARIFGRUPPE')
# ignores international minutes/sms
import csv
import glob
import string

# <config>
mypath = '*.csv' # e.g. './mybills/*.csv'
mydelimiter = '|' # '|' aka "pipe" is default with o2
# </config>

if __name__ == "__main__":
files = glob.glob(mypath)
assert len(files) > 0, "Error! No Files found (check path)"

totalminutes = 0
totalsms = 0
totalhomezone = 0
for file in files:
csvfile = open(file)
reader = csv.DictReader(csvfile,delimiter=mydelimiter)
smscount = 0
timecount = dict(hours=0,minutes=0,seconds=0)
homezonecount = 0
for row in reader:
if 'sprache' in string.lower(row['ART']):
(h,m,s) = string.split(row['DAUER'], ':')
timecount['hours'] += int(h)
timecount['minutes'] += int(m)
timecount['seconds'] += int(s)
if 'homezone' in string.lower(row['TARIFGRUPPE']):
homezonecount += int(m) + (int(h)*60) + (int(s)/60)
if 'sms' in string.lower(row['TARIFGRUPPE']):
smscount = smscount + 1
minutes = timecount['minutes'] + (timecount['hours']*60) + (timecount['seconds']/60)
totalminutes += minutes
totalsms += smscount
totalhomezone += homezonecount
print(file+' '+str(minutes)+' Minutes '+str(smscount)+' SMS ('+str(homezonecount)+' Minutes in Homezone)')
assert minutes >= homezonecount, "Error! More minutes in homezone than total?"
# the cool .format prints only work in python 2.6 ...
#print('Total  :{0:4} Minutes and {1:4} SMS in {2} Months ({3:4} Minutes in Homezone)'.format(totalminutes,totalsms,len(files),totalhomezone))
#print('Average:{0:4} Minutes and {1:4} SMS per Month'.format(totalminutes/len(files),totalsms/len(files)))
# ... and since that isn't in debian stable yet... i added "old" prints
print('Total   '+str(totalminutes)+' Minutes '+str(totalsms)+' SMS in '+str(len(files))+' Months ('+str(totalhomezone)+' Minutes in Homezone)')
print('Average '+str(totalminutes/len(files))+' Minutes '+str(totalsms/len(files))+' SMS per Month')

<?xml version="1.0"?>
<xsl:stylesheet version="1.0"
  xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
  <!--
    ! Small XSLT prog that calculates the faculty of one or more
    ! numbers by recursively calling a named template
    ! numbers are expected to be in a tree:
    ! <nums><num>1</num><num>2</num>...</nums>
   -->

  <xsl:output method="text"/>

  <xsl:template match="num">
      <xsl:text>fak(</xsl:text>
      <xsl:value-of select="."/>
      <xsl:text>) is </xsl:text>
      <xsl:call-template name="fak">
          <xsl:with-param name="number" select="."/>
      </xsl:call-template>
  </xsl:template>

  <xsl:template name="fak">
      <xsl:param name="number"/>
      <xsl:choose>
          <xsl:when test="$number = 1">
              <xsl:value-of select="$number"/>
          </xsl:when>
          <xsl:otherwise>
              <xsl:variable name="recursefak">
                  <xsl:call-template name="fak">
                      <xsl:with-param name="number" select="$number - 1"/>
                  </xsl:call-template>
              </xsl:variable>
              <xsl:value-of select="$number * $recursefak"/>
          </xsl:otherwise>
      </xsl:choose>
  </xsl:template>
</xsl:stylesheet>

Expected XML looks like this (with DTD even! ;P):

<?xml version="1.0" ?>
<!DOCTYPE numbers [
  <!ELEMENT nums (num+)>
  <!ELEMENT num (#PCDATA)>
]>
<nums>
  <num>3</num>
  <num>12</num>
</nums>

If you create a DateTime object like this (in the current stable version of php, 5.2.3):

<?php
$oDateTest = new DateTime("@0", new DateTimeZone(date_default_timezone_get()));
echo "tz: ".$oDateTest->getTimezone()->getName()."\n";
echo "date: ". $oDateTest->format("Y-m-d H:i:s")."\n";
?>

It will be in the default timezone (‘Europe/Berlin’ in my case) but say the date is 1970-01-01 00:00. This is wrong. The Unix timestamp “0″ stands for that exact date, but in another timezone: UTC. It should be 01:00 in Berlin.

This bug was reported multiple times, but with sometimes confusing bug reports. But someone had managed to submit a clear bug report with code to reproduce the behaviour (PHP Bug 43003) and the php developers acknowledged the bug and issued a fix that i verified to be (at least) in the following snapshots: php5.2-200803111530 and php5.3-200803111530.

Sadly, this fix is at best “unintuitive”, maybe it even qualifies as “still broken”. The above code gives the following output in these snapshots:

tz: +00:00
date: 1970-01-01 00:00:00

So, the DateTime object now knows that UNIX timestamps always are given in UTC and sets it’s timezone accordingly. But is this what it should do in this case? I – the programmer – clearly stated i wanted the DateTime object to be in my default timezone! Even if i explicitly give the timezone as ‘Europe/Berlin’ during construction, the object’s timezone still is UTC afterwards.

So instead of knowing that i have to manually set the DateTime to UTC, then back to my desired timezone when working with an UNIX timestamp i now have to know that a DateTime will be in UTC after setting it up with a UNIX timestamp. Personally i hate having to know things, IMHO it’s a sign of weak design. The API has to be clear, i don’t give a rat’s backside about the inner workings and struggles of the objects i use.

We went from this:

// FIXME: DateTime issue... needs the conversion to and from UTC...
$oDateTest = new DateTime("@0", new DateTimeZone('UTC'));
$oDateTest->setTimezone(new DateTimeZone("Europe/Berlin"));

To this:

// FIXME: DateTime issue... will always be UTC afterwards...
$oDateTest = new DateTime("@0", new DateTimeZone('Europe/Berlin')); // or UTC, or what/ever....
$oDateTest->setTimezone(new DateTimeZone("Europe/Berlin"));

Is this better or worse?