5 ms·
I've enjoyed the Python networking libraries I've used. A lot. Could you be more specific? Also, I'm not quite clear on your issue with packaging. Can you be m
by leoh 13y ago
I've enjoyed the Python networking libraries I've used. A lot. Could you be more specific?
Also, I'm not quite clear on your issue with packaging. Can you be more specific? Compared to C, I find importing existing code to be nearly heavenly.
Regarding backwards compatibility, maybe it's an issue, maybe it's not. On the one hand it's frustrating and some people will make it an issue. On the other hand, I can't help but think of cases like Apple, where they were the first to abandon modems, serial ports, diskette drives, and CD drives—but probably made the right decision.
- zanny 13y agoHes not talking about Python imports, hes talking about pulling Python packages through pip or one of the dozen utilities to do so from pypi. Though I do feel pip has been standardized on enough to solve that problem.
- MostAwesomeDude 13y agoThere are two options for Python networking: Twisted, and things that are not Twisted. Guess which one most people pick. What do you use to package? distutils, setuptools, distribute, distutils2, pkgutils...? How to choose?
- d0mine 13y agostart with distutils which is in stdlib and if it doesn't provide enough features; use setuptools (distribute and setuptools are merged) that extends distutils functionality.