This corresponds to the changeset 98:1f3c0d8a2b4a of the Mercurial
repository.
PR: ports/164311
Approved by: pgollucci
Sponsored by: Yakaz (http://www.yakaz.com)
- while here cleanup portexamples installation and relocate screeshot.sh to ${PREFIX}/bin
PR: ports/164921
Submitted by: maintainer, zeising at daemonic.se
version number is not continous; now we use svn version
instead of snapdate.
2. The distfile has been splitted into two files
so that pointyhat can test it (currently distfile
limit is 400MB for single file).
Submitted by: [1] erwin, [2] pfg and pav
Test::Command intends to bridge the gap between the well tested functions and
objects you choose and their usage in your programs. By examining the exit
status, terminating signal, STDOUT and STDERR of your program you can determine
if it is behaving as expected.
This includes testing the various combinations and permutations of options and
arguments as well as the interactions between the various functions and objects
that make up your program.
The various test functions below can accept either a command string or an array
reference for the first argument. If the command is expressed as a string it is
passed to system as is. If the command is expressed as an array reference it is
dereferenced and passed to system as a list.
The final argument for the test functions, $name, is optional. By default the
$name is a concatenation of the test function name, the command string and the
expected value. This construction is generally sufficient for identifying a
failing test, but you may always specify your own $name if desired.
Any of the test functions can be used as instance methods on a Test::Command
object. This is done by dropping the initial $cmd argument and instead using
arrow notation.
WWW: http://search.cpan.org/dist/Test-Command/
- Restrict USE_PYTHON range
- Fix make package when py-distribute or py-setuptools were installed
- Bump PORTREVISION for dependency change
Reported by: kwm [1]
This module implements ISO 8601 date, time and duration parsing. The
implementation follows ISO8601:2004 standard, and implements only date/time
representations mentioned in the standard. If something is not mentioned there,
then it is treated as non existent, and not as an allowed option.
For instance, ISO8601:2004 never mentions 2 digit years. So, it is not intended
by this module to support 2 digit years. (while it may still be valid as ISO
date, because it is not explicitly forbidden.) Another example is, when no time
zone information is given for a time, then it should be interpreted as local
time, and not UTC.
As this module maps ISO 8601 dates/times to standard Python data types, like
date, time, datetime and timedelta, it is not possible to convert all possible
ISO 8601 dates/times. For instance, dates before 0001-01-01 are not allowed by
the Python date and datetime classes. Additionally fractional seconds are
limited to microseconds. That means if the parser finds for instance nanoseconds
it will round it to microseconds.
WWW: http://cheeseshop.python.org/pypi/isodate
