I just tried a few things, but it all seems to be working for me. I am using a later build than 2.0 (should be the same as our last
for everything that matters) but haven't had to change any settings.
I wonder how dependent this is on your particular spreadsheet? The invalid literal error is coming from data in the spreadsheet you're loading, though it should be handled immediately. I can't see why we're not detecting the handler - it is the simplest possible
case and openpyxl is pure Python, so there's no C extensions to worry about. Do you see the same issues if you open a blank sheet?
One possibility for us not finding the handler may be due to how it was installed. I used a simple
pip install openpyxl
for 2.7 and 3.3 - did you do something different or use a version earlier than 1.7.0? When VS breaks at the error, do you see the source code for openpyxl?
As for "does this happen in any other projects", yes it does, but we haven't been able to find a common cause besides installation issues. Installing with pip should work fine in every case - custom installers may do weird things that hurt IntelliSense,
but debugging uses standard Python features (like
libraries don't do anything to break this. openpyxl certainly doesn't seem to do anything strange, at least in the latest version.