You must misunderstand something. This is about the python interface and not about treating users as babies. There are rules for providing cross-platform python interfaces and not aligning to these rules will introduce incompatibilities. If we cannot align to these rules because we have multiple versions of the same freecad library in one of the supported systems, we have to think about if this issue is dependent on the way how things are distributed on this system.vocx wrote: ↑Sun Nov 10, 2019 12:57 amI disagree with this. The users should always be accountable for what goes in their system. We cannot treat the users like babies, and hand hold them entirely. I think if the documentation is good enough, a competent user should be able to figure things out when it comes to dependencies, paths, and things of that nature. With that said, if this Conda thing really improves things as you say, fine, I'm not opposed to that; I just think the user should have some semblance of competence to start.
Please take your time and think about distributing a python-module for different systems/distros which depends on FreeCAD (import FreeCAD). Simple try this for Ubuntu (I suppose you have access to Ubuntu) and you will recognize, that you have to select a freecad version and modify the sys.path before you can "import FreeCAD".
Now think about other users with different platforms and you will recognize that there are other system dependent modifications necessary to make your module useable on these system.
And once you done this all, ask yourself what the reason for all this was.