dm.xmlsec.binding

[Carson Gee]

When doing upgrades where I reinstall the base requirements (and fresh installs) I’ve been getting these:

    import dm.xmlsec.binding as xmlsec
  File "/edx/app/edxapp/venvs/edxapp/local/lib/python2.7/site-packages/dm/xmlsec/binding/__init__.py", line 2, in <module>
    from _xmlsec import *
  File "etreepublic.pxd", line 33, in init dm.xmlsec.binding._xmlsec (src/_xmlsec.c:11150)
ValueError: lxml.etree._Element has the wrong size, try recompiling

If I reinstall dm.xmlsec.binding==1.3.2 this gets fixed, so it is correctable, but it appears that whatever is installing that package (it isn’t explicit in the requirements folder), is running before lxml is getting installed and thus is getting compiled incorrectly. So two questions: Does anyone know what package is bringing that in? I would guess it is from the Shibboleth feature. And how do we get it to install after lxml? Do we need bring back post.txt, move lxml to pre.txt or is pip deterministic enough that we can just move whatever requirement is bringing that in to the back of base.txt?

​

[Braden MacDonald]

Thanks for the info. 

dm.xmlsec.binding==1.3.2 is a dependency of python-saml, so yes it is related to the Shibboleth feature. This issue appears to be triggered by the recent upgrade from distribute to setuptools, and is holding back the weekly release. DB was looking into whether it could be fixed with https://github.com/edx/edx-platform/pull/8905 . I'm not sure if that will resolve it, or what the current status of the issue is, but it seems like the folks working on the release are on track to get this resolved by Tuesday. 

--

Braden MacDonald

@OpenCraft

--
You received this message because you are subscribed to the Google Groups "General Open edX discussion" group.
To view this discussion on the web visit https://groups.google.com/d/msgid/edx-code/CAAcikhPiwP1_8No78%3DkSV9os%2Bjv5_fg5D4Grybuh0qXo-FmR%2BA%40mail.gmail.com.

[Carson Gee]

I see 8905 got merged, if it ended up fixing the dm.xmlsec.binding installation order/compilation error, can we get it ported to cypress?

To view this discussion on the web visit https://groups.google.com/d/msgid/edx-code/CA%2BXWCNkXZXFCt6A_AwiKJ%2BKMzA1gxaYShO7BZM7un2Lic-hbvw%40mail.gmail.com.