Re: datetime.datetime. or datetime. ?

2009-10-11 Thread niklasr
On Oct 10, 8:43 pm, Carl Banks wrote: > On Oct 10, 2:26 am, niklasr wrote: > > > > > On Oct 8, 10:17 pm, Carl Banks wrote: > > > > On Oct 8, 3:11 pm, niklasr wrote: > > > > > On Oct 8, 5:25 pm, "Diez B. Roggisch" wrote: > > > > > > NiklasRTZ schrieb: > > > > > > > Hello, my basic question is w

Re: datetime.datetime. or datetime. ?

2009-10-10 Thread Carl Banks
On Oct 10, 2:26 am, niklasr wrote: > On Oct 8, 10:17 pm, Carl Banks wrote: > > > > > On Oct 8, 3:11 pm, niklasr wrote: > > > > On Oct 8, 5:25 pm, "Diez B. Roggisch" wrote: > > > > > NiklasRTZ schrieb: > > > > > > Hello, my basic question is which recommendation is after slight > > > > > restruc

Re: datetime.datetime. or datetime. ?

2009-10-10 Thread niklasr
On Oct 8, 8:33 pm, "Gabriel Genellina" wrote: > En Thu, 08 Oct 2009 19:11:04 -0300, niklasr escribió: > > > On Oct 8, 5:25 pm, "Diez B. Roggisch" wrote: > >> NiklasRTZ schrieb: > >> > Hello, my basic question is which recommendation is after slight > >> > restructuring datetime.datetime to datet

Re: datetime.datetime. or datetime. ?

2009-10-10 Thread niklasr
On Oct 8, 10:17 pm, Carl Banks wrote: > On Oct 8, 3:11 pm, niklasr wrote: > > > > > On Oct 8, 5:25 pm, "Diez B. Roggisch" wrote: > > > > NiklasRTZ schrieb: > > > > > Hello, my basic question is which recommendation is after slight > > > > restructuring datetime.datetime to datetime > > > > Both

Re: datetime.datetime. or datetime. ?

2009-10-10 Thread niklasr
On Oct 8, 7:34 pm, "Diez B. Roggisch" wrote: > niklasr schrieb: > > > > > On Oct 8, 5:25 pm, "Diez B. Roggisch" wrote: > >> NiklasRTZ schrieb: > > >>> Hello, my basic question is which recommendation is after slight > >>> restructuring datetime.datetime to datetime > >>> Both works but only one s

Re: datetime.datetime. or datetime. ?

2009-10-08 Thread Carl Banks
On Oct 8, 3:11 pm, niklasr wrote: > On Oct 8, 5:25 pm, "Diez B. Roggisch" wrote: > > > > > > > NiklasRTZ schrieb: > > > > Hello, my basic question is which recommendation is after slight > > > restructuring datetime.datetime to datetime > > > Both works but only one should be chosen probably adju

Re: datetime.datetime. or datetime. ?

2009-10-08 Thread Gabriel Genellina
En Thu, 08 Oct 2009 19:11:04 -0300, niklasr escribió: On Oct 8, 5:25 pm, "Diez B. Roggisch" wrote: NiklasRTZ schrieb: > Hello, my basic question is which recommendation is after slight > restructuring datetime.datetime to datetime - how to import is mostly a matter of taste, as long as

Re: datetime.datetime. or datetime. ?

2009-10-08 Thread Diez B. Roggisch
niklasr schrieb: On Oct 8, 5:25 pm, "Diez B. Roggisch" wrote: NiklasRTZ schrieb: Hello, my basic question is which recommendation is after slight restructuring datetime.datetime to datetime Both works but only one should be chosen probably adjust my package to comply to dependencies. Spec int

Re: datetime.datetime. or datetime. ?

2009-10-08 Thread niklasr
On Oct 8, 5:25 pm, "Diez B. Roggisch" wrote: > NiklasRTZ schrieb: > > > Hello, my basic question is which recommendation is after slight > > restructuring datetime.datetime to datetime > > Both works but only one should be chosen probably adjust my package to > > comply to dependencies. > > Spec i

Re: datetime.datetime. or datetime. ?

2009-10-08 Thread Diez B. Roggisch
NiklasRTZ schrieb: Hello, my basic question is which recommendation is after slight restructuring datetime.datetime to datetime Both works but only one should be chosen probably adjust my package to comply to dependencies. Spec integrated code where datetime.datetime.now() refactored to datetime.

datetime.datetime. or datetime. ?

2009-10-08 Thread NiklasRTZ
Hello, my basic question is which recommendation is after slight restructuring datetime.datetime to datetime Both works but only one should be chosen probably adjust my package to comply to dependencies. Spec integrated code where datetime.datetime.now() refactored to datetime.now() set rather from