Expose `six.moves` API for writing custom moves

[Sridhar Ratnakumar]

I added a xmlrpclib move without changing the six source code like this:

>>> import six.moves
>>> from six._moves import _Module, MovedItems
>>> m = _Module('xmlrpc_client', 'xmlrpclib', 'xmlrpc.client')
>>> setattr(MovedItems, m.name, m)
>>> six.moves.xmlrpc_client
<module 'xmlrpclib' from 'C:\Python27\lib\xmlrpclib.pyc'>

I am not fully confident as to using these internal names (that start with underscore). Wouldn't it be helpful to expose this as a supported API so others could build on top of six.moves?

[Benjamin Peterson (benjaminp)]

I think a better idea would be to add names which are missing. :) six tries to have a pretty minimalistic API, and I don't want to cloud it with non-Python2/3 related things.

[Sridhar Ratnakumar (srid)]

On Mon, Oct 4, 2010 at 12:14 PM, Benjamin Peterson <
<email address hidden>> wrote:

> I think a better idea would be to add names which are missing. :)

Well, the thing is there are so many custom moves that are project-specific.
Apart from xmlrpc_client and urlparse, do you think six can officially
support all of the following moves?
    _Module('xmlrpc_client', 'xmlrpclib', 'xmlrpc.client'),
    _Attribute('HTTPError', 'urllib2', 'urllib.error'),
    _Attribute('URLError', 'urllib2', 'urllib.error'),
    _Attribute('Request', 'urllib2', 'urllib.request'),
    _Attribute('urlopen', 'urllib2', 'urllib.request'),
    _Attribute('urllib_version', 'urllib2', 'urllib.request',
'__version__'),
    _Attribute('urlparse', 'urlparse', 'urllib.parse'),

[Benjamin Peterson (benjaminp)]

This is now implemented in hg.