Is there a conflict of libraries here?
Terry Reedy
tjreedy at udel.edu
Sat Nov 7 21:26:01 EST 2020
More information about the Python-list mailing list
Sat Nov 7 21:26:01 EST 2020
- Previous message (by thread): Is there a conflict of libraries here?
- Next message (by thread): Is there a conflict of libraries here?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 11/6/2020 5:05 PM, Steve wrote: > "Right, because the name "datetime" points to the class datetime in the > module datetime. A module containing an object with the same name as the module is a real pain, a constant mental papercut. I consider datetime.datetime to be a design mistake*. You are the 2nd person in about a month to post the same resulting code problem. * Either the class should have been 'Datetime', capitalized like classes in modules other that builtins generally should be, or the module should have been given a different name. I personally would always rename the module when imported. -- Terry Jan Reedy
- Previous message (by thread): Is there a conflict of libraries here?
- Next message (by thread): Is there a conflict of libraries here?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-list mailing list