ibrewster's profile - activity

Is there a way to get the exact execution string/environment that Wing uses when launching a script? I have a Python/PySide2/matplotlib application set up in a venv that looks correct when I run it from within wing, but if I run it directly from the command line, the font sizes in my plots are all huge. Apparently Wing is doing something right to make it work, but I don't know what.

Ok, finally, to wrap this up: apparently I need to import matplotlib.pyplot before I create my QApplication instance. So

pyplot wasn't calling use, at least not according to the debugger (the only time it came up was when I called it) howeve

Just as a further follow-up, apparently it IS getting set properly when I call Matplotlib.use(), but then it gets change

As I stated, no, sys.executable is NOT the same. To quote: "sys.executable is exactly as expected when run directly - th

Thanks. os.environ seems to be the same other than some additional wing-specific entries on the wing side (such as WINGD

Get exact execution string? Is there a way to get the exact execution string/environment that Wing uses when launching a

Both are inherited, but until WingPro itself actually tries to access a document, no access is granted. Apparently if th

Working around Mac OS X Catalina's restrictions? This isn't precisely a wing issue, but I'm running into it in wing spec

@wingwareSupport: Most likely yes, that does make a difference. From what I can tell, the only difference between your s

This isn't precisely a wing issue, but I'm running into it in wing specifically, so I'm hoping you guys might have an answer. I recently updated my mac OS machine to Catalina (BIG mistake!). Now trying to run commands like os.listdir or anything else that accesses the file system from the wing debugger or built-in shell just gives a "permission denied" error - even though I am just trying to access my files. I have tried adding WingPro.app and wing-internal-python to the "full disk access" section of the security preferences pane, but I still get the issue. Running python through the terminal, on the other hand, works fine after adding terminal to that section. So it seems like I should be able to fix this by adding something to the full disk access section, but I can't figure out what... Any tips/ideas? Thanks.

EDIT: PRECISE steps to recreate this issue:

1. Add WingPro.app to the full disk access list in the security pane. Make sure it is NOT listed in the "Files and Folders" section
2. Open WingPro, but DO NOT open or create any documents in Documents, Desktop, etc.
3. From the python shell, try to run something like os.listdir() on your Documents, Desktop, etc

As an interesting note, this issue is "fixed" the first time WingPro itself tries to access (open or save) a file in any of the affected directories. Once that has happened, even if only once, this problem no longer exists. Even removing Wing from the Full disk access section (with wing not running) does not cause the issue to re-appear. Also, apparently, this problem does not arise if you do not first add Wing to the full disk access section, as in that situation the system properly prompts to allow access (according to comments).

This is clearly an issue with the implementation of the new security features in Catalina, and how they interact with the existing "full disk access" permissions, and not an issue with WingIDE. In any case, now that WingPro has accessed documents in all relevant locations, it is working properly. Thanks for the feedback!

Not precisely specific to my machine, but rather to how I was using wing. I had 1) put wing into the Full Disk access se

"...the dialog that appears when you first try to access a file in Documents from Wing..." And therein lies the rub. I h

Interestingly, running sys.executable from the terminal python (which does work) and from the Wing python shell (which g

Wing 7.1.3.1, MacOS 10.15.2, python 3.6.5. I think the key here is this line: "...after giving Wing permission to use th

Interesting wrinkle. So sys.executable points to python in my virtualenv (well, venv technically), which is a symlink to

Working around Mac OS X Catalina's restrictions? This isn't precisely a wing issue, but I'm running into it in wing spec

For what it's worth, this has been an issue since wing version 7.0.4. I have been stuck back on that version because of

I'm trying to use WingIDE to edit a PySide2 application on Windows (initial writing and debugging occurred on a Mac, and I'm now trying to get it working on windows). My install of python is from Miniconda, version 3.7.1, but I installed pyside2 via pip (in the anaconda prompt) because the version installed by conda install was too old for my purposes. When I run my script from the Anaconda prompt it works properly, which leads me to believe that PySide2 is installed correctly.

However, when I try to launch the same script from inside WingIDE, or, in fact, just try to import PySide2 from the python shell, it fails with the following error:

>>>import PySide2
Traceback (most recent call last):
  Python Shell, prompt 6, line 1
    # Used internally for debug sandbox under external interpreter
  File "C:\Users\Israel\Miniconda3\Lib\site-packages\PySide2\__init__.py", line 51, in <module>
    _setupQtDirectories()
  File "C:\Users\Israel\Miniconda3\Lib\site-packages\PySide2\__init__.py", line 21, in _setupQtDirectories
    import shiboken2
  File "C:\Users\Israel\Miniconda3\Lib\site-packages\shiboken2\__init__.py", line 8, in <module>
    from .shiboken2 import *
builtins.ImportError: DLL load failed: The specified module could not be found.

Which would indicate to me that it is being unable to find/load a DLL that is being found and loaded properly when running the Anaconda prompt. I have compared the python path between the two instances of python, and aside from some ordering differences they are the same. Additionally, I have confirmed that Wing is running the same executable as the Anaconda prompt, and I do not have multiple installs of python on my system anyway (I set it up clean just for this). What am I missing? Something in the environment variables?

Oh, I see where I went wrong. I looked at those pages, but failed to recognize the difference between the Python path an

Oh, I see where I went wrong. I looked at those pages, but failed to recognize the difference between the Python path an

WingIDE, pyside2, and Miniconda on windows I'm trying to use WingIDE to edit a PySide2 application on Windows (initial w