Re: Python mx.DateTime
Rick Pasotto(rick@niof.net) is reported to have said:
> On Fri, Dec 28, 2001 at 01:05:23PM -0500, Wayne Topa wrote:
> > I have found an annoying 'feature' of the new mx.DateTime module and
> > wonder if this is from something I am doing incorrectly. Any comments
> > appreciated.
>
> It's printing that because __debug__ is true.
>
> rick@tc:~/Mail$ python
> Python 2.1.1 (#1, Nov 11 2001, 18:19:24)
> [GCC 2.95.4 20011006 (Debian prerelease)] on linux2
> Type "copyright", "credits" or "license" for more information.
> >>> print __debug__
> 1
> >>>
>
> Why *that's* so, I don't know.
>
> (Side note: I needed to import from mx.DateTime -- note the period.)
>
I have spent about 8 hours on this and I wondered if the maintainer
has set the debug flag. Then, after a break, I forgot all about that
point (blush). Invoking as pythonX.X -O fixes the problem.
Strange way to distribute the module. No mention of that in the
change log. Hummm
Correct --> >>> from mx.DateTime import *
was the correct line. I copied the wrong one. :-(
Thanks!!!
--
Windows95 (noun): 32 bit extensions and a graphical shell for a 16 bit
patch to an 8 bit operating system originally coded for a 4 bit
microprocessor, written by a 2 bit company, that can't stand 1 bit of
competition.
_______________________________________________________
Reply to: