mxTools (was Re: why no "do : until"?)

[M.-A. Lemburg]

Simon Brunning wrote:
> 
> > From: Max Møller Rasmussen [SMTP:maxm at normik.dk]
> > From: Oleg Broytmann [mailto:phd at phd.pp.ru]
> > >   Anyone here has any doubts that at least mxDateTime simply MUST be in
> > >the Python core? :)
> > No that would be a great idea, but doesn't the license prevent that?
> 
> As far as I can see, mxDateTime doesn't have restrictions in its license -
> it's mxODBC which does.
> 
> Is this right, Marc?

Right.

But please note that I wouldn't really want mxDateTime to go into
the core: the reason is that the mx Extensions will soon be available
as three packages under a new top-level package name "mx" -- I wouldn't
want to rip mxDateTime out of that context.

BTW, mxODBC v2.0 will then no longer be free for commercial use. I put
a moderate license fee on it to at least produce some funding for mxODBC
and the other mx Extensions  -- the old mxODBC license just didn't
work out, so I had to take this step.
 
mxODBC will still remain free for non-commercial use, e.g. for personal
and non-profit organizations, and as before you get full source code
with it, so you still have all the advantages of being able to adapt
the code to your needs.

mxDateTime and most of the other tools will remain Open Source
software as before.

> *Both* of these are essential to me personally. I also use Marc's additional
> built-ins, but they are really just a nice to have. (*Very* nice, but still
> just nice.)
> 
> So, if this were a democracy, which it isn't, I'd vote for mxDateTime to
> definitely go in, for someone to think about the additional built-ins, and
> for mxODBC to stay separate.
> 
> As it is, though, it's a one-man-one-vote system. Guido is the man, he has
> the vote. So we'll just have to wait and see...
> 
> Cheers,
> Simon Brunning
> TriSystems Ltd.
> sbrunning at trisystems.co.uk
> 
> -----------------------------------------------------------------------
> The information in this email is confidential and may be legally privileged.
> It is intended solely for the addressee. Access to this email by anyone else
> is unauthorised. If you are not the intended recipient, any disclosure,
> copying, distribution, or any action taken or omitted to be taken in
> reliance on it, is prohibited and may be unlawful. TriSystems Ltd. cannot
> accept liability for statements made which are clearly the senders own.

-- 
Marc-Andre Lemburg
______________________________________________________________________
Company:                                        http://www.egenix.com/
Consulting:                                    http://www.lemburg.com/
Python Pages:                           http://www.lemburg.com/python/