[XML-SIG] Python package name

[Fred L. Drake, Jr.]

Martin v. Loewis writes:
 > To my knowledge, there has been no decision yet. There was a criterion
 > in the spirit '''if xml-sig does not manage to update PyXML, we will
 > change the package name in Python 2'''. Now, I have updated the
 > current PyXML to operate on top of 2.0b1 (pending synchronization with
 > Lars' approved patches), and I plan to release PyXML 0.6 within days.
 > That voids the precondition of above criterion.

  I was just talking to Guido about this matter.  Our current intent
is to add a version check to Lib/xml/__init__.py, so that we don't
override the base class with a PyXML package that's too old.
  I propose adding a constant version_info to xml/__init__.py in the
PyXML package.  The value should have a similar structure to the
sys.version_info in Python.  This can be used for the check.
  Martin, how quickly do you think you can have a PyXML package ready?
Can it be done in time for 2.0b2 (26 Sept.)?  I'd like to make the
change to Lib/xml/__init__.py to make it require the new package:

try:
    import _xmlplus
except ImportError:
    pass
else:
    if _xmlplus.version_info > (0, 6):
        import sys
        sys.modules[__name__] = _xmlplus

 > The BDFL may still decide to rename the package, on grounds of the
 > current add-on approach being a hack and the renaming being a
 > technical more clean solution. I think everybody's opinion on this
 > matter is clear, as well, so it's a good time to make a decision :-)

  I think the only real solution will be to fix the import machinery
to be more Java-like, allowing multiple directories to provides parts
of a shared package space without having to resort to really evil
hackery.


  -Fred

-- 
Fred L. Drake, Jr.  <fdrake at beopen.com>
BeOpen PythonLabs Team Member