Can you try these one by one, with the start page open (don't switch to the Draft WB), in the python console, and see if any of them crashes?
Code: Select all
from pivy import coin
from PySide import QtCore,QtGui
import Draft
Can you try these one by one, with the start page open (don't switch to the Draft WB), in the python console, and see if any of them crashes?
Code: Select all
from pivy import coin
from PySide import QtCore,QtGui
import Draft
Hi sgrogan, I also noticed that there is no file description for the 0.18 releases.
This omits important parts. My proposal to improve it is:FreeCAD development builds for Linux, MacOS, and Windows have a filename in the form
FreeCAD-<dev-version>-<revision>.extension (revision = github commit count number)
Code: Select all
FreeCAD development builds for Linux, MacOS, and Windows have a filename in the form
FreeCAD-<dev-version>-<revision>-<operating system>-<bit rate>-<build system>-<Python version>-<Qt version>.<file-extension>
where revision is the GitHub commit count number, Py2 means Python 2.x, Qt4 means Qt 4.x, Conda is an open source package management system, LP is ??.
Agreed. Kunda1 has been pushing this for some time.uwestoehr wrote: ↑Mon May 13, 2019 10:14 pm Currently there the different files have all their own scheme and this is confusing. What is for example "LP"? (I really don't know.) What is "VS"? Why appears "Linux" and "OSX" on the same place but "Win" does not? Do we really need to distinguish between different Visual studio versions?
So all unnecessary info should go and all files should have the same scheme.
LP is LibPack. 11.x to 12.x means PY2/QT4/VS2013 > PT3/QT5/VS2015+.
I would say the opposite. The Win testers know QT4/5 etc. The LP_12.x has a newer version of Qt(5.12) than the Conda based builds(5.6), this offers information above what "About FreeCAD gives.
That is why I proposed a file scheme that contains the info about Qt.
This would lead to pospone all the remaining py3 debug on next FC release cycle, too late compared to py2 life cycle.
No crashes. Until now none of the crashes was reproducible, except the language change which doesn't bother me too much.yorik wrote: ↑Mon May 13, 2019 9:21 pm Can you try these one by one, with the start page open (don't switch to the Draft WB), in the python console, and see if any of them crashes?Code: Select all
from pivy import coin from PySide import QtCore,QtGui import Draft