datetime.datetime. or datetime. ?

Carl Banks pavlovevidence at gmail.com
Sun Oct 11 02:43:01 CEST 2009


On Oct 10, 2:26 am, niklasr <nikla... at gmail.com> wrote:
> On Oct 8, 10:17 pm, Carl Banks <pavlovevide... at gmail.com> wrote:
>
>
>
> > On Oct 8, 3:11 pm, niklasr <nikla... at gmail.com> wrote:
>
> > > On Oct 8, 5:25 pm, "Diez B. Roggisch" <de... at nospam.web.de> 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 integrated code where datetime.datetime.now() refactored to
> > > > > datetime.now()
> > > > > set rather
> > > > > from datetime import datetime, timedelta
> > > > > than
> > > > > import datetime
> > > > > or no matter and completely flexible (then why gae error that
> > > > > datetime.datetime wasn't datetime?)
> > > > > Naturally better not to customize external dependencies but seemingly
> > > > > impossible to use both for a little xmpp project.
> > > > > Thanks with best regards
>
> > > > Some remarks:
>
> > > >   - whitespace is significant. In python. And in posting here.
>
> > > >   - please show us the exact traceback you get, and a minimal example
> > > > that produces it.
>
> > > >   - how to import is mostly a matter of taste, as long as you refrain
> > > > from using "from datetime import *"e
>
> > > > Diez
>
> > > type object 'datetime.datetime' has no attribute 'datetime' Traceback
> > > (most recent call last):
> > > is flexible, both ways worked just that self complying towards more
> > > professional projects naturally feels right. Above error log seemingly
> > > caused by import datetime instead of from datetime import datetime.
> > > Then changed import and cut the first datetime occurance which looks
> > > good but breaks next sync with other. The project is the crowdguru
> > > xmpp chat test reachable via gae app "classifiedsmarket@
> > > {gmail,appspot}" currently importing
> > > from datetime import datetime, timedelta
> > > instead of
> > > import datetime
> > > Many thanks for the help and all further recommendation
> > > code disponible montao.googlecode.com- Hide quoted text -
>
> > When you do this:
>
> >   import datetime
>
> > you have to do this
>
> >   d = datetime.datetime()
>
> > And when you do this:
>
> >   from datetime import datetime
>
> > you have to do this:
>
> >   d = datetime()
>
> > You evidently did this:
>
> >   from datetime import datetime
>
> > then this:
>
> >   d = datetime.datetime()
>
> > which is not allowed.
>
> > If you want to self-comply, I recommend always doing it the first way.
>
> Understood it's a choice and to stay consistent with chosen. If the
> first is recommended, why is second way possible?


Because not everything in Python is a "professional project" that
needs "self-complying".

Also there are occasions where the second way is better.  In a piece
of code that does a lot of math, would you rather write "math.sin(x
+2)" all over the place, or "sin(x+2)"?


Carl Banks



More information about the Python-list mailing list