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

Using more editor features from spyder

Open
#423 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
desktop

Research direction

The issue mentions the existing Spyder editor integration and possible search/replace, block commenting, and CadQuery class syntax highlighting, but names no files or tests. First review how the current editor component is integrated, then narrow the work to one feature and confirm its expected behavior before implementation. Done would require an agreed feature scope and corresponding validation.

Written by the indexing model from the issue text.

Description

It seems that, just like using the core editor component from Spyder, the editor could fairly simply be improved by using more of the infrastructure Spyder already provides - search/replace, block commenting, add syntax highlighting for cadquery class names, ... Are these patches that will potentially be considered for merging?

Dominant language
Python
Stars
1.3k
Forks
211
PR merge metrics
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.