On Thu, Jul 12, 2001 at 02:05:57PM -0500, Ian Bicking wrote:
> Chuck Esterbrook <[EMAIL PROTECTED]> wrote:
> > At 12:37 AM 7/12/2001 -0500, Ian Bicking wrote:
> > >Chuck Esterbrook <[EMAIL PROTECTED]> wrote:
> > > > Also: MiddleKit assumes that if you have DateTime, it is in the mx
> > > package,
> > > > as in:
> > > > from mx import DateTime
> > >
> > >On my Debian system it installs mxDateTime directly in the path, as in
> > > import DateTime
> > >mx doesn't exist at all.
> >
> > But is that an older mxDateTime or is that the latest 2.0.1?
> >
> > http://www.lemburg.com/files/python/eGenix-mx-Extensions.html#Download-mxBASE
>
> Seems to be 1.3.0. Debian has a mxdatetime package, not a general mx
> package.
>
> All it should take is a
>
> try:
> from mx import DateTime
> except ImportError:
> import DateTime
>
> I think the DateTime name is only used by mx.
The "mx" utilities were repackaged this year or last year. They used to be
mxDateTime etc. as separate packages. Now they are all in one bug bundle,
as subpackages of mx, maintained by eGenix.com. On my system, with a
home-installed Python and mx, only "from mx import DateTime" works.
--
-Mike (Iron) Orr, [EMAIL PROTECTED] (if mail problems: [EMAIL PROTECTED])
http://iron.cx/ English * Esperanto * Russkiy * Deutsch * Espan~ol
_______________________________________________
Webware-discuss mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/webware-discuss
