Revision history [back]
Based on diagnosing this by email the problem is that the code being stepped into is inside a .egg file on the remote host and it looks like, in the remote case only, Wing is failing to correctly recognize this and tries to open the full path as an actual file name. This is a bug and we'll try to fix it.
If you need to step into the package, I think you can work around this by unzipping the .egg file. It is just a .zip file and can be unzip'ed so you have a directory with same name as the .egg (xyz.egg -> xyz).
Thanks for reporting this problem!