michaelgale / cq-kit Goto Github PK

Hei, I'm unable to install cqkit using pip. I tried with various versions of Python, on Linux and MacOS.

Example:

docker run -it --rm  python:3.10-slim-bullseye bash
root@c71a37b4384e:/# pip install cqkit
Collecting cqkit
  Downloading cqkit-0.5.0.tar.gz (47 kB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 47.1/47.1 kB 1.0 MB/s eta 0:00:00
  Preparing metadata (setup.py) ... error
  error: subprocess-exited-with-error
  
  × python setup.py egg_info did not run successfully.
  │ exit code: 1
  ╰─> [6 lines of output]
      Traceback (most recent call last):
        File "<string>", line 2, in <module>
        File "<pip-setuptools-caller>", line 34, in <module>
        File "/tmp/pip-install-d86usskz/cqkit_8552ef1848204e9dbc49f82914745b8b/setup.py", line 14, in <module>
          with open(loc + "/requirements.txt") as f:
      FileNotFoundError: [Errno 2] No such file or directory: '/tmp/pip-install-d86usskz/cqkit_8552ef1848204e9dbc49f82914745b8b/requirements.txt'
      [end of output]
  
  note: This error originates from a subprocess, and is likely not a problem with pip.
error: metadata-generation-failed

× Encountered error while generating package metadata.
╰─> See above for output.

note: This is an issue with the package mentioned above, not pip.
hint: See above for details.

[notice] A new release of pip is available: 23.0.1 -> 23.1
[notice] To update, run: pip install --upgrade pip

Its likely that cqkit is ready for general release as a pypi package for end users wanting an easier install experience.

cq-kit has a ridiculous amount to offer. It'd be great if either:

• cq-kit could get at least a single official PyPI-hosted release before being officially retired. Yes, I acknowledge that PyPI is superficially useless in this case – because CadQuery itself (i.e., the main mandatory runtime dependency of cq-kit) is unavailable on PyPI. So, why? Conda-forge, in a word. Given a single PyPI-hosted release, releasing a single official Anaconda release is trivial on conda-forge. </shrug>
• The most critical subsets of cq-kit could be merged upstream into the main CadQuery codebase. Whenever free time and volunteer enthusiasm permits, ^{...so never is what I'm saying} would you be willing to submit one or more CadQuery PRs to that effect? Specifically:
  • The export_step_file() improvements delineated here seem especially germane. Those are really all unconditional improvements to CadQuery's vanilla STEP exporter. Your changeset really deserves to see a broader audience.
  • The export_iges_file() exporter. CadQuery currently lacks any IGES support whatsoever, so this would be a tremendous add. An import_iges_file() importer would be great as well, but... you know. Can't beg too much. Easy does it there!

Interestingly, pythonocc-core also abruptly halted development at about the same time as this project's final commit. Even more interestingly, I'm sequestered in the verdant woods of Sharbot Lake – a mere 45 minutes outside of Ottawa. I know, eh? </ahem>

Whichever way you elect to take this, thanks for all the community investment. You rock the CAD scene, Mike! 🚀

Add a import_iges_file function to cqfiles. More than likely this will be a wrapper around IGESControl_Reader() in the OCC API.