old TempoVis.py in recent builds

This subforum is specifically to discuss packaging issues on different platforms (windows, mac, linux), and using different packaging systems (conda, etc...)
User avatar
sgrogan
Veteran
Posts: 6499
Joined: Wed Oct 22, 2014 5:02 pm

Re: old TempoVis.py in recent builds

Post by sgrogan »

kkremitzki wrote: Fri Oct 04, 2019 10:02 pm I removed those because, in my testing trying to fix the builds, I was getting errors about them not being present. There's a bug somewhere screwing with all this.
@kkremitzki, can you try this?

Code: Select all

usr/share/freecad-daily/Ext/freecad/*.py
usr/share/freecad-daily/Ext/PySide/*.py
usr/share/freecad-daily/Mod/AddonManager/*.py
usr/share/freecad-daily/Mod/AddonManager/*.ui
usr/share/freecad-daily/Mod/Arch/Dice3DS/*.py
usr/share/freecad-daily/Mod/Arch/Presets/*.json
usr/share/freecad-daily/Mod/Arch/Presets/*.csv
usr/share/freecad-daily/Mod/Arch/*.py
usr/share/freecad-daily/Mod/Complete/*.py
usr/share/freecad-daily/Mod/Draft/*.py
usr/share/freecad-daily/Mod/Fem/*.py
usr/share/freecad-daily/Mod/Fem/femexamples/*.py
usr/share/freecad-daily/Mod/Fem/femexamples/meshes/*.py
usr/share/freecad-daily/Mod/Fem/femguiobjects/*.py
usr/share/freecad-daily/Mod/Fem/feminout/*.py
usr/share/freecad-daily/Mod/Fem/femmesh/*.py
usr/share/freecad-daily/Mod/Fem/femobjects/*.py
usr/share/freecad-daily/Mod/Fem/femresult/*.py
usr/share/freecad-daily/Mod/Fem/femsolver/*.py
usr/share/freecad-daily/Mod/Fem/femsolver/calculix/*.py
usr/share/freecad-daily/Mod/Fem/femsolver/elmer/*.py
usr/share/freecad-daily/Mod/Fem/femsolver/elmer/equations/*.py
usr/share/freecad-daily/Mod/Fem/femsolver/fenics/*.py
usr/share/freecad-daily/Mod/Fem/femsolver/z88/*.py
usr/share/freecad-daily/Mod/Fem/femtest/*.py
usr/share/freecad-daily/Mod/Fem/femtools/*.py
usr/share/freecad-daily/Mod/Fem/Resources/ui/*.ui
usr/share/freecad-daily/Mod/Idf/*.py
usr/share/freecad-daily/Mod/Image/*.py
usr/share/freecad-daily/Mod/Image/ImageTools/*.py
usr/share/freecad-daily/Mod/Import/*.py
usr/share/freecad-daily/Mod/Inspection/*.py
usr/share/freecad-daily/Mod/Material/materialtools/*.py
usr/share/freecad-daily/Mod/Material/*.py
usr/share/freecad-daily/Mod/Material/*.ui
usr/share/freecad-daily/Mod/Measure/*.py
usr/share/freecad-daily/Mod/Mesh/*.py
usr/share/freecad-daily/Mod/MeshPart/*.py
usr/share/freecad-daily/Mod/OpenSCAD/*.py
usr/share/freecad-daily/Mod/Part/*.py
usr/share/freecad-daily/Mod/Part/AttachmentEditor/*.py
usr/share/freecad-daily/Mod/Part/AttachmentEditor/*.ui
usr/share/freecad-daily/Mod/Part/BOPTools/*.py
usr/share/freecad-daily/Mod/Part/CompoundTools/*.py
usr/share/freecad-daily/Mod/Part/BasicShapes/*.py
usr/share/freecad-daily/Mod/PartDesign/*.py
usr/share/freecad-daily/Mod/PartDesign/*.ui
usr/share/freecad-daily/Mod/PartDesign/Scripts/*.py
usr/share/freecad-daily/Mod/PartDesign/fcgear/*.py
usr/share/freecad-daily/Mod/PartDesign/PartDesignTests/*.py
usr/share/freecad-daily/Mod/PartDesign/WizardShaft/*.py
usr/share/freecad-daily/Mod/Path/*.py
usr/share/freecad-daily/Mod/Path/PathScripts/*.py
usr/share/freecad-daily/Mod/Path/PathScripts/post/*.py
usr/share/freecad-daily/Mod/Path/PathTests/*.py
usr/share/freecad-daily/Mod/Points/*.py
usr/share/freecad-daily/Mod/Raytracing/Init.py
usr/share/freecad-daily/Mod/Raytracing/InitGui.py
#usr/share/freecad-daily/Mod/Raytracing/RaytracingExample.py
usr/share/freecad-daily/Mod/ReverseEngineering/*.py
usr/share/freecad-daily/Mod/Robot/*.py
usr/share/freecad-daily/Mod/Show/*.py
usr/share/freecad-daily/Mod/Show/SceneDetails/*.py
usr/share/freecad-daily/Mod/Sketcher/Init.py
usr/share/freecad-daily/Mod/Sketcher/InitGui.py
usr/share/freecad-daily/Mod/Sketcher/Profiles.py
#usr/share/freecad-daily/Mod/Sketcher/SketcherExample.py
usr/share/freecad-daily/Mod/Sketcher/TestSketcherApp.py
usr/share/freecad-daily/Mod/Sketcher/TestSketcherGui.py
usr/share/freecad-daily/Mod/Sketcher/ProfileLib/*.py
usr/share/freecad-daily/Mod/Spreadsheet/*.py
usr/share/freecad-daily/Mod/Spreadsheet/Resources/icons/*.svg
usr/share/freecad-daily/Mod/Start/*.py
usr/share/freecad-daily/Mod/Start/StartPage/*.py
usr/share/freecad-daily/Mod/Surface/*.py
usr/share/freecad-daily/Mod/TechDraw/TDTest/*.py
usr/share/freecad-daily/Mod/Test/*.py
usr/share/freecad-daily/Mod/Tux/*.py
usr/share/freecad-daily/Mod/Web/*.py
Note the two commented files, they are examples and are not allowed?
"fight the good fight"
vocx
Veteran
Posts: 5197
Joined: Thu Oct 18, 2018 9:18 pm

Re: old TempoVis.py in recent builds

Post by vocx »

kkremitzki wrote: Fri Oct 04, 2019 10:02 pm I removed those because, in my testing trying to fix the builds, I was getting errors about them not being present. There's a bug somewhere screwing with all this.
I just wanted to note something about Arch files.

The Dice3D and Preset files are in the source directory

Code: Select all

source-dir/src/Mod/Arch/Dice3D
source-dir/src/Mod/Arch/Preset
Once I compile the source, they end up here

Code: Select all

build-dir/Mod/Arch/Dice3DS/
build-dir/data/Mod/Arch/Presets
The Dice3DS files are Python files (module to be imported), while the Presets are .json and .csv (just information, no code).

The debian/freecad-daily-runtime.install seems to place them in the same usr/share directory, is this the proper way? Or should data and code be separate?

Code: Select all

usr/share/freecad-daily/Mod/Arch/Dice3DS/dom3ds.py
usr/share/freecad-daily/Mod/Arch/Dice3DS/__init__.py
usr/share/freecad-daily/Mod/Arch/Dice3DS/util.py
usr/share/freecad-daily/Mod/Arch/Presets/ifc_products_IFC2X3.json
usr/share/freecad-daily/Mod/Arch/Presets/ifc_products_IFC4.json
Always add the important information to your posts if you need help. Also see Tutorials and Video tutorials.
To support the documentation effort, and code development, your donation is appreciated: liberapay.com/FreeCAD.
User avatar
sgrogan
Veteran
Posts: 6499
Joined: Wed Oct 22, 2014 5:02 pm

Re: old TempoVis.py in recent builds

Post by sgrogan »

vocx wrote: Fri Oct 04, 2019 11:34 pm The Dice3DS files are Python files (module to be imported), while the Presets are .json and .csv (just information, no code).

The debian/freecad-daily-runtime.install seems to place them in the same usr/share directory, is this the proper way? Or should data and code be separate?
This seems to be handled by the rules file https://salsa.debian.org/science-team/f ... /rules#L17
My question is this a FreeCAD CMake thing , or are there different requirements for different distro's?

The PPA (and I think most distro's) is packaged from the install target.
"fight the good fight"
User avatar
kkremitzki
Veteran
Posts: 2511
Joined: Thu Mar 03, 2016 9:52 pm
Location: Illinois

Re: old TempoVis.py in recent builds

Post by kkremitzki »

vocx wrote: Fri Oct 04, 2019 11:34 pm Or should data and code be separate?
That was the idea with the distinction between freecad-runtime and freecad-common files, with freecad-runtime being meant to solely have Python files. But there's no need for that, in retrospect, so eventually I'll combine the two and just have freecad-common, I think. With 0.19 there will be a break in the binary packages, i.e. libfreecad-python3-0.18 will have its name changed, so that would be a good time to do it.
Like my FreeCAD work? I'd appreciate any level of support via Patreon, Liberapay, or PayPal! Read more about what I do at my blog.
openBrain
Veteran
Posts: 9034
Joined: Fri Nov 09, 2018 5:38 pm
Contact:

Re: old TempoVis.py in recent builds

Post by openBrain »

Hi,
Updated today with daily build of 2019/10/08 and got this when I open a file : ;)
<string>(2)<class 'ModuleNotFoundError'>: No module named 'Show.TempoVis'
User avatar
DeepSOIC
Veteran
Posts: 7896
Joined: Fri Aug 29, 2014 12:45 am
Location: used to be Saint-Petersburg, Russia

Re: old TempoVis.py in recent builds

Post by DeepSOIC »

openBrain wrote: Wed Oct 09, 2019 2:50 pm Hi,
Updated today with daily build of 2019/10/08 and got this when I open a file : ;)
<string>(2)<class 'ModuleNotFoundError'>: No module named 'Show.TempoVis'
If the file was saved while you were editing a sketch, that's to be expected. Just ignore.
openBrain
Veteran
Posts: 9034
Joined: Fri Nov 09, 2018 5:38 pm
Contact:

Re: old TempoVis.py in recent builds

Post by openBrain »

DeepSOIC wrote: Wed Oct 09, 2019 3:18 pm If the file was saved while you were editing a sketch, that's to be expected. Just ignore.
Don't know as this is a file from the forum. :) Anyway thanks for explanation.
Still can be better if the error message is a bit more "comprehensive". ;)
User avatar
DeepSOIC
Veteran
Posts: 7896
Joined: Fri Aug 29, 2014 12:45 am
Location: used to be Saint-Petersburg, Russia

Re: old TempoVis.py in recent builds

Post by DeepSOIC »

openBrain wrote: Wed Oct 09, 2019 3:21 pm Still can be better if the error message is a bit more "comprehensive". ;)
Well, it's tricky. TempoVis instance is saved as a property of a sketch when a sketch is open, and FreeCAD will save that property to a file, and point to the class as a module name + class name combo to later restore the object. However, TempoVis.py was renamed into mTempoVis.py, so FreeCAD fails to find that TempoVis.py when loading the project, so this is a totally all-right error message. FreeCAD has no idea about what TempoVis is, this loading mechanism is general.

The error should go away after resaving the project.
Post Reply