[issue26640] xmlrpc.server imports xmlrpc.client

Brett Cannon added the comment: Yes because the location of the object is based on where it's defined, not where you got it from. While I get the motivation to be a little cleaner in the xmlrpc package, "practicality beats purity" here in that the reorg isn't worth it at this point in the fac

[issue26640] xmlrpc.server imports xmlrpc.client

ProgVal added the comment: Even if xmlrpc.client imported them in its namespace? -- ___ Python tracker ___ ___ Python-bugs-list mailin

[issue26640] xmlrpc.server imports xmlrpc.client

Serhiy Storchaka added the comment: Moving public classes and functions to other module can break pickle compatibility. -- nosy: +serhiy.storchaka ___ Python tracker ___ ___

[issue26640] xmlrpc.server imports xmlrpc.client

Changes by SilentGhost : -- nosy: +loewis versions: +Python 3.6 -Python 3.4 ___ Python tracker ___ ___ Python-bugs-list mailing list U

[issue26640] xmlrpc.server imports xmlrpc.client

New submission from ProgVal: from xmlrpc.client import Fault, dumps, loads, gzip_encode, gzip_decode Shouldn't these class/functions be moved to a new module, with a name like xmlrpc.common? -- components: Library (Lib) messages: 262428 nosy: Valentin.Lorentz priority: normal severity: