| 18 Sep 2022 |
 Roger Maitland#7070 | Are the csv files in the src directory included in your static build? | 15:46:40 |
 Jern#4673 | not as far as I can tell | 15:52:25 |
| Roger Maitland#7070 | Those are required - all of the raw data is stored in these csv files | 15:53:09 |
| Jern#4673 | pip install git+https://github.com/gumyr/cq_warehouse.git#egg=cq_warehouse is this the correct way to install cq_warehouse? Might be something odd about the way the files are handled in a github static build? | 16:10:19 |
| Jern#4673 | https://github.com/jdegenstein/jmwright-CQ-Editor/blob/main/.github/workflows/pyinstaller-builds-actions.yml | 16:12:23 |
 fpq473#6357 | AFAIK pyinstaller tries to be smart about what it bundles, so it's possible that it didn't realize that the csv's should be included.
Maybe there's a "dumb mode" where you can just include everything. | 16:34:31 |
| fpq473#6357 | 
Download unknown.png | 16:35:33 |
| fpq473#6357 | Separate but related, jmwright's CQ-editor builds have the following problem for me: if there's an exception in the Console, then the error is just huge and borks the console. | 16:35:34 |
| fpq473#6357 | * Separate but related, jmwright's CQ-editor builds have the following problem for me: if there's an exception in the Console, then the error is just huge and borks the console.
So you might want to see if your builds have the same issue. | 16:36:07 |
| Roger Maitland#7070 | Looks good to me. | 16:37:19 |
| Jern#4673 | Yes, mine do have this issue as well. I originally thought it was due to some changes I made but now I am confident it is not my fault. | 16:49:18 |
| Jern#4673 | ok I got it working, I had to add the cq_warehouse directory as a data directory, which pulls in the CSVs correctly. The other issue mentioned by fqp473 is not fixed yet | 19:12:23 |
 sethfischer#4882 | I structure my CQ projects as proper Python packages, and I install the package(s) in a virtual environment. An example is https://github.com/sethfischer/osr which is a project comprising of two packages osr_mechanical and osr_warehouse. I install both those package in editable mode and start cq-editor in that environment. | 22:38:03 |
| sethfischer#4882 | * I structure my CQ projects as proper Python packages, and I install the package(s) in a virtual environment. An example is https://github.com/sethfischer/osr which is a project comprising of two packages osr_mechanical and osr_warehouse. I install both those package in editable mode and start cq-editor in that environment. I use a similar setup for https://github.com/sethfischer/cq-electronics which has an examples directory. | 22:39:28 |
| sethfischer#4882 | * I structure my CQ projects as proper Python packages, and I install the package(s) in a virtual environment. An example is https://github.com/sethfischer/osr which is a project comprising of two packages osr_mechanical and osr_warehouse. I install both those packages in editable mode and start cq-editor in that environment. I use a similar setup for https://github.com/sethfischer/cq-electronics which has an examples directory. | 22:42:12 |
| 19 Sep 2022 |
 matt3o#1392 | I'm trying to keep the library as accessible as possible, I'm having a lot of troubles getting people to use it because they can't get the environment working | 06:00:54 |
| sethfischer#4882 | Being able to pip install from pypi would be as accessible as you can get. But to do that you users would need a Conda or venv environment going | 06:16:14 |
| sethfischer#4882 | But I'm a developer 🙂 on the other had the first package I pushed to pypi was a CQ library | 06:21:08 |
| matt3o#1392 | people weren't even able to have it working when it was just a file to put in the same directory 😄 | 06:21:34 |
| sethfischer#4882 | It's a real shame they're missing out on so much goodness 🙂 | 06:23:18 |
| matt3o#1392 | on their defense I'm using all dev versions | 06:24:10 |
| matt3o#1392 | if they download the latest release or just pip install, it doesn't work | 06:24:59 |
| sethfischer#4882 | * But I'm a developer 🙂 on the other hand the first package I pushed to pypi was a CQ library | 06:27:57 |
| sethfischer#4882 | Do you know if you users as mainly Win, Mac, or Linux? | 06:29:09 |
| matt3o#1392 | well statistically I'd say Win | 06:37:18 |
| matt3o#1392 | it's not an openscad kind of deal, they'd expect something like that but generally speaking the entry level of CQ is a little bit steeper | 06:41:54 |
| sethfischer#4882 | * Do you know if your users as mainly Win, Mac, or Linux? | 06:43:42 |
| sethfischer#4882 | Yes. As a minimum users need to be able to set up a Conda or virtual env with the correct version of Python. And then be able to install packages into that environment. | 06:47:53 |
 Draek#9615 | Remembering my first steps with conda all I can say is that it's impossible to get it working for someone that is not into computer science | 09:11:12 |
| matt3o#1392 | I'm planning on making a cloud service for my little library, I'm afraid it's the only way to have it widely used | 09:20:46 |
