IronPython 3 Compatibility and Update for xlrd & xlsxwriter#2422
IronPython 3 Compatibility and Update for xlrd & xlsxwriter#2422sanzoghenzo merged 4 commits intopyrevitlabs:developfrom
Conversation
|
I think it's worth splitting the pull request into several,
I think there may be problems with dependencies and changing them, after which there will be problems with compatibility with the pyRevit code. Also, can you resolve the merge issues? Update: I checked the code superficially, there is use of libraries only here, perhaps there will not be so many problems with changing versions. |
sanzoghenzo
left a comment
There was a problem hiding this comment.
Nicely done @trgiangv!
Aside for the merge conflicts to resolve, I've pointed out a minor change.
Thank you for your work!
Hi @dosymep
|
sanzoghenzo
left a comment
There was a problem hiding this comment.
Last round; I'm not sure if the xlrd.examples needs to be there, so you can ignore that comment
db00375 to
d6b344f
Compare
ef0d90a to
1f87638
Compare
|
Your rebase was a little messed up, I took the liberty to fix it. I think we're good to go! |
|
📦 New work-in-progress (wip) builds are available for 5.0.0.24294+1030-wip |
|
📦 New work-in-progress (wip) builds are available for 5.0.0.24295+0909-wip |
|
📦 New public release are available for 5.0.0.24174+2300 |
Description:
This pull request introduces:
Compatiblevariable for handling IronPython 2/3, Cpython, netcore, netframework. trgiangv@cf51642Updated
xlrdandxlsxwriterLibrary:Fix build
pyrevitLabs.pyRevit.Runtimeonly target IronPython 2.7pyRevit/dev/pyRevitLabs.PyRevit.Runtime/Directory.Build.targets
Line 24 in 86697ad
Additional Notes:
What challenges are we facing if we set
IronPython3as the default engine?