|
From: Remi C. (Imap) <rem...@gm...> - 2015-10-26 22:32:19
|
Hi At the moment python3-wbem does not need m2crypto, apparently. Which is really great because installing it on Windows is extremely painful (for example, it does not work with the latest SWIG version: https://github.com/swig/swig/issues/344 ). Would it be also possible for pywbem python2, to use something else than m2crypto ? Thanks Remi Le 12/10/2015 09:17, Andreas Maier a écrit : > > Hi Ross, > I think it is generally possible to have a single source that supports > both Python 2.x and 3.x. If needed, there could even be runtime tests > for the version. > > It is definitely a requirement to maintain compatibility at the client > API for Python 2.x code. > > As far as the process goes, let me take a look at your changes, and > then I can integrate them upstream. > > All, > backwards support for Python 2.x exists only for 2.6 and 2.7 (for the > pywbem client, not sure for the other subprojects). I recently > stumbled across a statement of supporting back to 2.3, but that is not > correct. > If anyone has a requirement fir supporting earlier than 2.6, let me > know (including why). > > Cheers > Andy > > — > Reply to this email directly or view it on GitHub > <https://github.com/deejross/python3-pywbem/issues/2#issuecomment-147325607>. > |