Closed gtalarico closed 6 years ago
It looks like the encoding of the file ssl.py
is not specified properly (could be a BOM mark?). Where did you get the module?
I tried some stuffs in ironpython64 console :
@eirannejad I saw that you updated IronPython standard lib to 2.7.7 (revision number : b56d731cb83c5593de1a0b6dd0a72f33644cf9be), so I don't understand why files are different.
Then I tried some other stuff in RPS :
@daren-thomas It looks like RPS is still finding a ssl.py file somewhere even when sys.path is empty. I don't understand. (Update: actually, it does the same with in ironpython console if I pop all sys.path entries. import ssl still work)
Uhm this might be my bad. Originally when I updated pyRevit to 2.7.7 apparently I forgot to update the standard library. And then I did the same for RPS. We need to check to see if the standard library in RPS is the latest shipped with 2.7.7
@CyrilWaechter FYI, RPS attached a zipped file of the standard library to the it's executor assembly and that's why RPS is able to find the modules with no sys.path
My bad for not updating this ! Manully replacing the standard library with the one shipped with 2.7.7 fixed it.
@daren-thomas It was the encoding issue. ssl.py
was saved in UTF-8 BOM. After converting it to UTF-8 in notepad++ and relinking the standard library zip file, there are no exceptions on import ssl
This could be closed btw
@eirannejad thanks for pointing that out :-)
I get this error when importing the ssl module Work on same ironpython version on CLI, but fails on RPS.
Does anyone have any idea what might be the cause or a workaround?