Dropping python-optik?

[Mihai Ibanescu]

On Tue, Jun 08, 2004 at 11:47:21AM -0400, Elliot Lee wrote:
> On Tue, 8 Jun 2004, Mihai Ibanescu wrote:
> 
> > As of python 2.3, Optik is included in the mainline python (although it's
> > called optparse now).
> >
> > Fedora currently ships python 2.3.3 (2.3.4 in rawhide), so we may consider
> > dropping the python-optik package.
> > 
> > If we are to do this, the main python package would have to obsolete
> > python-optik and have a virtual provides for python-optik; but then again,
> > if your script worked with optik it would have to adjust its imports to use
> > optparse instead. So it's quite messy.
> > 
> > Any preference on how to handle this? Drop the package and deal with the mess?
> > Keep the package and deal with the mess? :-)
> 
> I would prefer to drop python-optik - it sounds like backwards compat is
> the only real reason not to. To handle backwards compat, in the main
> python package you could add a simple 'optik.py' that just does 'from
> optparse import *' or somesuch.

That would actually work - with a nice deprecation warning on import.
I guess as long as we keep the fake optik.py we'll also have the python
package provide python-optik = 1.4.1.

I'll go for it unless I hear it's a bad idea.

Cheers,
Misa