Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Looking for static build testers on macos-x86_64 and macos-arm64

Open
  • Is something wrong?
#472 8 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
32/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
github-actions, macos, python
Domain
build-system, desktop, release, testing-qa

Research direction

Start with the linked jmwright-CQ-Editor releases and the weekly GitHub Actions builds. Test the static packages on macos-x86_64 and macos-arm64 by downloading, unzipping, and launching them, then report usability or packaging problems. Advice about package signing and macOS quality-of-life improvements is also requested, but no project files or tests are named.

Written by the indexing model from the issue text.

Description

Hello,

I have maintained a fork of CQ-editor at https://github.com/jdegenstein/jmwright-CQ-Editor for the past several years.

In that time I have released static builds of CQ-editor built with pyinstaller that bundle CadQuery, build123d and other useful packages. These builds provide a "download, unzip and run" user experience for python / CQ newcomers. These builds are also run on a weekly basis via github actions.

https://github.com/jdegenstein/jmwright-CQ-Editor/releases

I recently finished my effort to also release static builds for macos-arm64 (and have long released macos-x86_64) but I could use some testers on these platforms. Bonus points if any advice can be offered related to eventually signing these packages for these platforms or other related QoL improvements for macos.

Thank you

Dominant language
Python
Stars
1.3k
Forks
210
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from CadQuery/CQ-editor

All issues in CadQuery/CQ-editor

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.