[Max M]
> ...
> First of, it should be possible to easily convert between the
> datetime objects.
Why? All the conversions people asked for when the module was being
designed were implemented.
> And eg. the date object doesn't have a datetime() method. Which
> it could easily have.
But not a *s
Max M wrote:
> Serge Orlov wrote:
>> Max M wrote:
>
>> Yes, you did. datetime.timetuple is those who want *time module*
>> format, you should use datetime.data, datetime.time, datetime.year
>> and so on... As they say, if the only tool you have is timetuple, everything
>> looks like tuple Try this
Serge Orlov wrote:
Max M wrote:
Yes, you did. datetime.timetuple is those who want *time module* format, you should use datetime.data, datetime.time, datetime.year
and so on...
As they say, if the only tool you have is timetuple, everything looks like tuple
Try this:
dt = datetime(2005, 1, 1,
Max M wrote:
> # -*- coding: latin-1 -*-
>
> """
>
> I am currently using the datetime package, but I find that the design
> is oddly
> asymmetric. I would like to know why. Or perhaps I have misunderstood
> how it should be used?
Yes, you did. datetime.timetuple is those who want *time module* fo
