summaryrefslogtreecommitdiff
path: root/time/py-mxDateTime
AgeCommit message (Collapse)AuthorFilesLines
2017-04-10Updated time/py-mxDateTime to 3.2.9mef3-11/+17
----------------------------------- (Changes to 3.2.9 is unknown) Changes from 3.2.6 to 3.2.8 Protected delta.strftime() against segfaults on Windows, which only allows day values <= 31 and segfaults for higher values. Thanks to Frank Boje for reporting this problem.
2017-01-01Add python-3.6 to incompatible versions.wiz1-2/+2
2016-07-09Remove python33: adapt all packages that refer to it.wiz1-2/+2
2015-12-05Extend PYTHON_VERSIONS_INCOMPATIBLE to 35adam1-2/+2
2015-11-02Add SHA512 digests for distfiles for time categoryagc1-1/+2
Problems found with mismatching existing digests for: distfiles/asclock-classic-1.0.tar.gz distfiles/asclock-gtk-2.1.10beta.tar.gz distfiles/asclock-xlib-2.0.11.tar.gz distfiles/emiclock-2.0.2.tar.gz Otherwise, existing SHA1 digests verified and found to be the same on the machine holding the existing distfiles (morden). All existing SHA1 digests retained for now as an audit trail.
2014-12-31Improve EGG_NAME default to work for packages with '-' in their name.wiz1-2/+1
Remove now unnecessary overrides in various packages.
2014-05-09Mark packages that are not ready for python-3.3 also not ready for 3.4,wiz1-2/+2
until proven otherwise.
2014-01-20Update to 3.2.7. Changes not found.wiz3-11/+48
Set LICENSE. Fix interpreter path in installed files.
2012-10-08Drop PKG_DESTDIR_SUPPORT setting, "user-destdir" is default these days.asau1-3/+1
2012-06-03Update to 3.2.4:wiz3-18/+17
Changes from 3.2.3 to 3.2.4 Fixed a possible double deallocation in the mxDateTime C API import helper. Thanks to Daniele Varrazzo for reporting this. Changes from 3.2.2 to 3.2.3 Fixed a possible segfault when using the .pydate(), .pydatetime() and .pytime() methods. Thanks to Daniel Szoska for reporting this. Changes from 3.2.1 to 3.2.2 mxDateTime seconds rounding is now more careful to not show 60.00 or 61.00 as second value. mxDateTime will now correctly work with numeric arrays (numpy) again. Thanks to Christian Marquardt for reporting the problem. mxDateTime's DateTimeFromAbsDateTime() now accepts leap second values (86400.0 - <86401.0) as well. Thanks to Christian Marquardt for reporting the problem. mxDateTime range errors did not always format the wrong value. Made mxDateTime compile again on Python 2.1 and 2.2. Changes from 3.2.0 to 3.2.1 Fixed a segfault when comparing DateTime/DateTimeDelta with None objects. Thanks to Mark Matthews for reporting this. Changes from 3.1.2 to 3.2.0 Added new .rebuild() methods to both DateTime and DateTimeDelta objects, making it easier creating new objects from existing ones by just replacing some of the parameters (akin to the mxURL .rebuild() method). Greatly enhanced the interoperability with the Python datetime module objects: Added support for handling mixed type operations with datetime.time objects. Added new constructor methods to DateTime and DateTimeDelta objects which aid in combining them with Python datetime module objects: .pytime(), .pytimedelta(), .pydatetime() and .pydate() as appropriate. Added support for Python datetime module objects to the generic mxDateTime constructors DateTimeFrom(), DateFrom(), DateTimeDeltaFrom() (and their aliases). The Python datetime module's C API is now loaded on demand whenever mxDateTime needs to work with PyDateTime objects. mxDateTime was updated to use mixed type number slots, a feature which was added to Python in version 2.1 (by the author of mxDateTime, Marc-André Lemburg). This has made working with DateTime and DateTimeDelta objects and other date/time types a lot more orbust. mxDateTime's gmtime() now also works for ticks values beyond 2038 on 32-bit platforms that implement a POSIX confirm gmtime(), but cannot handle post 2038 dates due to data type restrictions, e.g. older 32-bit Linux platforms. As side-effect, this also speeds up the gmtime() implementation on all platforms with POSIX conform date/time handling. mxDateTime will try to use the most accurate clock available on the system for now(). For most POSIX systems, this is a nanosecond resolution clock. A new global now_resolution allows checking the resolution reported by the system. The performance of now() was enhanced by directly interfacing to the various platform C APIs. Changed: mxDateTime will now format the seconds value in the repr() and the str() output rounded to two decimal places. In previous versions, it used to truncate the fraction after two decimal places. Known problem: mxDateTime doesn't build on FreeBSD with Python 2.7 and 2.7.1. This is a known problem with Python 2.7 and will be fixed in Python 2.7.2. See http://bugs.python.org/issue10547 for details. DateTimeFrom() now accepts a defaultdate parameter when parsing strings or keyword-only arguments. defaultdate provides the defaults to assume when pars of the date/time are not given. It defaults to today(). DateFrom() will now only parse the date parts of a string and only accept date-related keyword arguments. Fixed a bug in the mxDateTime parser that triggered with some ISO formats using second fractions. Thanks to Francesco Pierfederici for bringing this to our attention. Added support for more US AM/PM date formats such as "5:08pm" (without space), "5:08 p.m." (with additional dots) to the mxDateTime parser. Thanks to Tom at TicketStumbler for bringing this to our attention. Changed C API: mxDateTime now uses C longs for years internally and in the C API. Note that the published C API has changed because of this: mxDateTime.DateTime_FromDateAndTime() now expects a long as year instead of an int. This change will require a recompile of the applications using the mxDateTime C API, but should only be noticeable on 64-bit platforms. Added new C API DateTime_FromAbsDateTime to the mxDateTime C API. Added version number to C API object: Due to the changes in the C API, the name of the C API object "mxDateTimeAPI" was changed to "mxDateTimeAPI2", so that applications relying on the old API don't import the changed API by accident. Added optional calendar parameter to DateTimeFromAbsDateTime(). This allows creating DateTime instances with a given calendar. Default is to use the Gregorian calendar. Added BST to mx.DateTime.Timezone. Fixed problem with now() resolution on Windows. It now provides millisecond resolution again. Fixed a bug in mx.DateTime.DateTimeFromAbsDateTime() which caused an endless loop on 64-bit platforms for very large year values. Fixed Debian bug#494792: Incorrect subtraction with regular Python datetime. This was actually a side-effect of the coercion logic previously used in mxDateTime and not really a bug. The new mixed type number slot implementations made it possible to Darko Zurman for pointing this out. Removed left-over debug code which caused the builtin strptime() never to get used. Thanks to Alok Singhal for this one. Fixed a bug in the mxDateTime .ticks() method which causes it to raise an error for vahe Epoch.
2012-05-07Set BUILDLINK_ABI_DEPENDS correctly (with +=, not ?=)dholland1-2/+2
It turns out there were a lot of these.
2011-01-11update to 3.1.3drochner4-157/+117
changes: misc fixes and improvements
2009-07-06with is a reserved word for Python 2.6, so avoid it.joerg2-1/+126
2009-06-14Remove @dirrm entries from PLISTsjoerg1-28/+1
2009-05-30update master site.zafer1-2/+2
2009-03-20Simply and speed up buildlink3.mk files and processing.joerg1-13/+6
This changes the buildlink3.mk files to use an include guard for the recursive include. The use of BUILDLINK_DEPTH, BUILDLINK_DEPENDS, BUILDLINK_PACKAGES and BUILDLINK_ORDER is handled by a single new variable BUILDLINK_TREE. Each buildlink3.mk file adds a pair of enter/exit marker, which can be used to reconstruct the tree and to determine first level includes. Avoiding := for large variables (BUILDLINK_ORDER) speeds up parse time as += has linear complexity. The include guard reduces system time by avoiding reading files over and over again. For complex packages this reduces both %user and %sys time to half of the former time.
2009-03-20Include pyversion.mk include the protected part of the buildlink3.mkjoerg1-3/+3
files, not over and over again.
2009-03-05Remove PYBINMODULE. All it did was mark some packages as not availablejoerg1-2/+1
on some platforms that lacked shared library support in the past. The list hasn't been maintained at all and the gain is very limited, so just get rid of it.
2009-02-09Remove Python 2.1 support.joerg1-2/+1
2008-06-12Add DESTDIR support.joerg1-1/+3
2008-04-25Update PYTHON_VERSIONS_COMPATIBLEjoerg1-2/+2
- assume that Python 2.4 and 2.5 are compatible and allow checking for fallout. - remove PYTHON_VERSIONS_COMPATIBLE that are obsoleted by the 2.3+ default. Modify the others to deal with the removals.
2008-04-15enable python25abs1-2/+2
2006-07-08Change the format of BUILDLINK_ORDER to contain depth information as well,jlam1-2/+2
and add a new helper target and script, "show-buildlink3", that outputs a listing of the buildlink3.mk files included as well as the depth at which they are included. For example, "make show-buildlink3" in fonts/Xft2 displays: zlib fontconfig iconv zlib freetype2 expat freetype2 Xrender renderproto
2006-07-08Track information in a new variable BUILDLINK_ORDER that informs usjlam1-1/+2
of the order in which buildlink3.mk files are (recursively) included by a package Makefile.
2006-06-02Doesn't work with distutils in Python 2.0, so mark 2.1+.joerg1-1/+2
2006-04-12Aligned the last line of the buildlink3.mk files with the first line, sorillig1-2/+2
that they look nicer.
2006-04-06Over 1200 files touched but no revisions bumped :)reed1-3/+3
RECOMMENDED is removed. It becomes ABI_DEPENDS. BUILDLINK_RECOMMENDED.foo becomes BUILDLINK_ABI_DEPENDS.foo. BUILDLINK_DEPENDS.foo becomes BUILDLINK_API_DEPENDS.foo. BUILDLINK_DEPENDS does not change. IGNORE_RECOMMENDED (which defaulted to "no") becomes USE_ABI_DEPENDS which defaults to "yes". Added to obsolete.mk checking for IGNORE_RECOMMENDED. I did not manually go through and fix any aesthetic tab/spacing issues. I have tested the above patch on DragonFly building and packaging subversion and pkglint and their many dependencies. I have also tested USE_ABI_DEPENDS=no on my NetBSD workstation (where I have used IGNORE_RECOMMENDED for a long time). I have been an active user of IGNORE_RECOMMENDED since it was available. As suggested, I removed the documentation sentences suggesting bumping for "security" issues. As discussed on tech-pkg. I will commit to revbump, pkglint, pkg_install, createbuildlink separately. Note that if you use wip, it will fail! I will commit to pkgsrc-wip later (within day).
2006-03-04Point MAINTAINER to pkgsrc-users@NetBSD.org in the case where nojlam1-2/+2
developer is officially maintaining the package. The rationale for changing this from "tech-pkg" to "pkgsrc-users" is that it implies that any user can try to maintain the package (by submitting patches to the mailing list). Since the folks most likely to care about the package are the folks that want to use it or are already using it, this would leverage the energy of users who aren't developers.
2006-02-05Recursive revision bump / recommended bump for gettext ABI change.joerg2-2/+4
2005-04-11Remove USE_BUILDLINK3 and NO_BUILDLINK; these are no longer used.tv1-2/+1
2005-02-23Add RMD160 checksums.wiz1-1/+2
2004-12-27Upgrade to 2.0.6darcy2-6/+6
2004-07-22add python as categoryrecht1-2/+2
ok'd a while back at pkgsrcCon by agc and wiz
2004-05-17Garbage collect BUILDLINK_PKGBASE.<pkg> from buildlink3: it is not anymoreseb1-2/+1
used since revision 1.139 of mk/buildlink3/bsd.buildlink3.mk.
2004-05-08Unused.wiz1-26/+0
2004-03-29Add a BUILDLINK_PKGBASE.<pkg> definition where it's not equal to <pkg>,jlam1-1/+2
e.g. "BUILDLINK_PKGBASE.gtk?= gtk+". This is mandated by the example buildlink[23].mk files in bsd.buildlink[23].mk.
2004-03-18Fix serious bug where BUILDLINK_PACKAGES wasn't being ordered properlyjlam1-3/+1
by moving the inclusion of buildlink3.mk files outside of the protected region. This bug would be seen by users that have set PREFER_PKGSRC or PREFER_NATIVE to non-default values. BUILDLINK_PACKAGES should be ordered so that for any package in the list, that package doesn't depend on any packages to the left of it in the list. This ordering property is used to check for builtin packages in the correct order. The problem was that including a buildlink3.mk file for <pkg> correctly ensured that <pkg> was removed from BUILDLINK_PACKAGES and appended to the end. However, since the inclusion of any other buildlink3.mk files within that buildlink3.mk was in a region that was protected against multiple inclusion, those dependencies weren't also moved to the end of BUILDLINK_PACKAGES.
2004-03-16If the ${PKGBASE} of a package doesn't match the token passed tojlam1-1/+2
BUILDLINK_PACKAGES, then set BUILDLINK_PKGBASE.<pkg> explicitly so that we can map from <pkg> to BUILDLINK_PKGBASE.<pkg>.
2004-03-06Conform to template in revision 1.101 of bsd.buildlink3.mk.jlam1-7/+8
2004-03-04D'oh! Fix typo: Only add the dir not the actual header..recht1-2/+2
2004-03-04add path to mxDateTime's headers to BUILDLINK_INCDIRSrecht1-1/+3
2004-03-04bl3ifyrecht2-2/+22
Patch provided by Michal Pasternak in PR 24664 (with fixes by me).
2003-09-09Update to 2.0.5.recht2-6/+6
The new version includes patches needed to compile the packages under Python 2.3.
2003-07-17s/netbsd.org/NetBSD.org/grant1-2/+2
2003-06-02Use tech-pkg@ in favor of packages@ as MAINTAINER for orphaned packages.jschauma1-2/+2
Should anybody feel like they could be the maintainer for any of thewe packages, please adjust.
2002-10-25buildlink some header files which are needed by psycopgdrochner1-1/+14
2002-10-24-update to 2.0.4 (from 1.3.0... there are too many changes to list,drochner4-97/+390
compatibility is maintained afaict, except an additional "mx" prefix in the namespace -make it a "distutils" pkg, so it works with Python-2.2.x -license change - now freely redistibutable
2002-10-19Undo enabling on python2.2.jlam1-2/+2
2002-10-19Add inclusion guards and use foo-[0-9]* instead of foo-*.jlam1-2/+7
2002-10-19Use buildlink2.jlam1-6/+10
generated by cgit v1.2.3 (git 2.39.1) at 2024-05-19 13:41:09 +0000