Wing IDE 6.0 MacOS

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

Wing IDE 6.0 MacOS

WingIDE - User mailing list
Hi,
I thought I’d try wing 6 to see if the bug in the project properties environment was fixed for MacOS. It isn’t fixed and additionally there are errors when I try to launch from the command line to inherit the environment. There is also an inexplicable ’syntax error’ running the same code in Wing 6 that isn’t there using Wing 5 with the same environment.  

It really feels like there is insufficient testing done on MacOS platform. The docs certainly don’t reflect the reality of the MacOS 

Quote: Whenever you run wing6.0 from the command line, you may specify a list of files to open. These can be arbitrary text files and a project file. For example, the following will open project file myproject.wpr and also the three source files mysource.pyREADME, and Makefile:
wing6.0 mysource.py README Makefile myproject.wpr
(on Windows, the executable is called wing.exe)
No mention of MacOS
This is how I run Wing from the command line: /Applications/WingIDE.app/Contents/MacOS/wing
I like Wing, I’d like to continue using it.

Kind regards,
Andy
[hidden email]
CISSP, CSTA, CSTP, CWSA
GIAC: GCIA, GCIH, GPEN, GWAPT, GCFE, GREM
Computer Forensic & Security Specialist
Blog.InfoSecMatters.net


_________________________________________________
Wing IDE users list
http://wingware.com/lists/wingide
Reply | Threaded
Open this post in threaded view
|

Re: Wing IDE 6.0 MacOS

WingIDE - User mailing list
Andrew Ratcliffe via wingide-users wrote:
> I thought I’d try wing 6 to see if the bug in the project properties
> environment was fixed for MacOS. It isn’t fixed and additionally there
> are errors when I try to launch from the command line to inherit the
> environment. There is also an inexplicable ’syntax error’ running the
> same code in Wing 6 that isn’t there using Wing 5 with the same
> environment.

Sorry, I don't know which bug you are referring to in project properties
environment.  Can you explain that?

On the Mac, Wing will inherit different environment if launched from the
command line vs. if it's launched by clicking on the WingIDE.app or
using "open WingIDE.app" (which is the same as clicking).  I'm not sure
that's relevant, however.

We did make a change in Wing 6 so that it longer inherits
DYLD_LIBRARY_PATH in its environment on OS X, although
the inherited value is still used for code debugged or executed from the
IDE.  That fixes failure to start from the GUI in some rare cases, but
probably also is not relevant... I think I just need more information
about what you mean.

I suspect the syntax error is due to Wing 6 picking up the latest Python
by default, even if it's Python 3.x, while Wing 5 preferred Python 2.x.  
You probably need to set Python Executable in your Project Properties so
Wing 6 uses the right Python interpreter.

>
> Quote: Whenever you run wing6.0 from the command line, you may specify
> a list of files to open. These can be arbitrary text files and a
> project file. For example, the following will open project file
> myproject.wpr and also the three source files mysource.py, README, and
> Makefile:
> wing6.0 mysource.py README Makefile myproject.wpr
> (on Windows, the executable is called wing.exe)
> No mention of MacOS
> This is how I run Wing from the command line:
> /Applications/WingIDE.app/Contents/MacOS/wing

Yes, thanks, this should also be updated to be clearer where the
executable is on MacOS.  The command line usage should otherwise be the
same, however.

Thanks,

--

Stephan Deibel
Wingware | Python IDE

The Intelligent Development Environment for Python Programmers

wingware.com

_________________________________________________
Wing IDE users list
http://wingware.com/lists/wingide