Open Stack

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

On 27/11/14 12:09, Thomas Goirand wrote:
> On 11/27/2014 12:31 AM, Donald Stufft wrote:
>> 
>>> On Nov 26, 2014, at 10:34 AM, Thomas Goirand <zigo at debian.org>
>>> wrote:
>>> 
>>> Hi,
>>> 
>>> I tried to package suds-jurko. I was first happy to see that
>>> there was some progress to make things work with Python 3.
>>> Unfortunately, the reality is that suds-jurko has many issues
>>> with Python 3. For example, it has many:
>>> 
>>> except Exception, e:
>>> 
>>> as well as many:
>>> 
>>> raise Exception, 'Duplicate key %s found' % k
>>> 
>>> This is clearly not Python3 code. I tried quickly to fix some
>>> of these issues, but as I fixed a few, others appear.
>>> 
>>> So I wonder, what is the point of using suds-jurko, which is
>>> half-baked, and which will conflict with the suds package?
>>> 
>> It looks like it uses 2to3 to become Python 3 compatible.
> 
> Outch! That's horrible.
> 
> I think it'd be best if someone spent some time on writing real
> code rather than using such a hack as 2to3. Thoughts anyone?

That sounds very subjective. If upstream is able to support multiple
python versions from the same codebase, then I see no reason for them
to split the code into multiple branches and introduce additional
burden syncing fixes between those.

/Ihar
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.22 (Darwin)

iQEcBAEBCgAGBQJUd0wMAAoJEC5aWaUY1u57gVMIAI70aQjReaa32WVJExL18c4t
QfJ3U+4yGxURIwqu/VKfpujN+KNQ7JWR+zqSUpv1gGxRTQcwFYLLKeW9XRxBnETw
0YxLvCrju3MInFDCFZrJzm3mTMlnQSosQSoK08Phn++cyRs1R/isaWPU7UHMbiSM
jIqRQkLYYPoSnhiTm1LkOoWg3oP82g3vxOPQmAlTAlx38lJ81ioBq7z9rRQzW+CX
DcZy+64t+iePY9w0P4mvXdl/saDAlh7Hl/nu7RKcC5ycoa2un07N6SAazycMPvln
naQvaXFfjPjGP5ToLNWIDwhRWmMkUa581ng37+6LewvbFNUDttKCHobp8cvVqy8=
=d0S7
-----END PGP SIGNATURE-----