Hi Pete, Not sure if this is noteworthy but the standarddialogs.py file was not installed under my PyQt5 directory in my new Python 3.6.1 instance nor in its affiliated virtual environment. After scouting around, I did find a standarddialogs.py in the original PyQt5 tarball I downloaded to configure and build PyQt per Eric's suggestion that I download and configure all Eric IDE dependencies separately instead of trying to use the QScin wheel via Python's PIP.
Of the standard dialogs, all executed without warning or error EXCEPT the QFileDialog.* buttons. The 4 QFileDialog buttons in the middle of the list all successfully opened a fully functional dialog box and recorded the sought-after informantion. However, they immediately threw the warning "Gtk-WARNING **" Invalid input string" when I initially clicked the test button but before any further action. None of the standard dialogs resulted in a seg fault, just those 4 resulted in a Gtk-WARNING. -Ben On Tue, May 30, 2017 at 9:52 AM, Helen Ready <[email protected]> wrote: > Hi Pete, > > Sorry about the long delay. Thank you for taking the time to share your > wisdom, especially about the insight on Qt and QScin being immune to venv > fencing! Next time, I'll be sure to install Eric and dependencies under > the Python install directory (usr/local/python/3.6.1/) instead of one of > its sub virtual environments (usr/local/python/3.6.1/venv/myvenvproject/). > > In your opinion, from a Linux security point-of-view, is it optimal to > just execute and use the Eric IDE from a sudo elevation off of my user > account or is the recommendard expectation for me to run Eric from my > standard account? Put another way, am I wasting my time trying to make > this work as "./eric6" when I should be running the Eric IDE as "sudo > ./eric6" for security and/or functionality reasons? > > "it looks, it crashes, where the native Gtk file dialog is bent into Qt" > << Yes, this is exactly what is happening when I attempt to open a File > Dialog box within the Eric IDE. Specifically, I click on a File Open icon, > a separate window opens for the Gtk Dialog Box with the border but a blank, > black screen and then the app crashes hard with a seg fault to the command > line. > > "Please try to execute python examples/dialogs/standarddialogs.py (from > PyQt5), and check, if the QFileDialog functions behave." << Sure, no > problem! I will get back with you with the info today and let you know how > it goes. > > Thanks! > Ben > > > On Tue, May 23, 2017 at 4:18 AM, Hans-Peter Jansen <[email protected]> wrote: > >> Hi Ben, >> >> On Freitag, 19. Mai 2017 16:27:08 Helen Ready wrote: >> > Let me start by saying Thank You for the amazing IDE, Eric, and its >> > community. >> >> Welcome to the club. >> >> > Recently, I decided to take the plunge into Linux with CentOS 7 >> > as my first. After installing Python 3.6.1 from source and setting up a >> > virtual enviroment, I naturally went to install the Eric IDE as my next >> > step. >> >> Installing Python from source need some careful considerations about >> * what _other_ versions of Python are installed in the system? >> * which Python(s) are qscintilla, sip, PyQt build on.. >> because some parts of it (Qt, qscintilla) cannot be fenced in the VE, >> they're >> pure C++... >> >> OTOH; your traceback, although missing symbols, points to some >> interference >> between Qt and Gtk (it looks, it crashes, where the native Gtk file >> dialog is >> bent into Qt...). >> >> Please try to execute python examples/dialogs/standarddialogs.py (from >> PyQt5), >> and check, if the QFileDialog functions behave. >> >> Pete >> _______________________________________________ >> Eric mailing list >> [email protected] >> https://www.riverbankcomputing.com/mailman/listinfo/eric >> > >
_______________________________________________ Eric mailing list [email protected] https://www.riverbankcomputing.com/mailman/listinfo/eric
