[Pypgsql-devel] [ pypgsql-Feature Requests-708393 ] Moving to python2.2 new style classes and datetime

[SourceForge.net <no...@so...>]

Feature Requests item #708393, was opened at 2003-03-23 16:46
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=366528&aid=708393&group_id=16528

Category: None
Group: None
Status: Open
>Priority: 3
Submitted By: Christian Heimes (tiran)
Assigned to: Nobody/Anonymous (nobody)
Summary: Moving to python2.2 new style classes and datetime

Initial Comment:
datetime:
http://www.python.org/dev/doc/devel/lib/module-datetime.html
new style classes:
http://www.python.org/doc/2.2.1/whatsnew/whatsnew22.html

Datetime will be a part of python2.3 and is used in zope3.

new style classes would ease up a lot of code, for example:

class PgInt8(long):
    pass

Christian

----------------------------------------------------------------------

>Comment By: Gerhard Häring (ghaering)
Date: 2003-03-23 19:30

Message:
Logged In: YES 
user_id=163326

First, exploiting new-style classes and other Pyhton 2.3
features are  what pyPgSQL 3.0 is all about.

It will require Python 2.2, but I don't think we'll want to
use the new datetime module from 2.3.

Unfortunately, the pyPgSQL developers are generally short on
time, that's why not that much has been accomplished on the
3.0 front, yet. At least from me ;-)

If you're interested in other plans, you can look in the
TODO file, which is in CVS.

Also note that the current PgInt* classes do range checks.
Just subclassing from long doesn't get us this feature.

I'm still sceptical about the merit of the PgInt* types, but
that's just my personal opinion and better discussed on the
mailing list.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=366528&aid=708393&group_id=16528