Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Suggestion: Simple Environment Check in Windows Installer

Abierto
  • ¿Algo no está bien?
#462 1 comentario 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
25/100
Tipo de issue
Nueva funcionalidad
Claridad
Necesita aclaración
Estado de actividad
Estancado
Stack tecnológico
python
Área
desktop, release

Línea de trabajo

El issue no proporciona ningún archivo fuente del instalador, punto de entrada ni prueba desde la que empezar. Primero reproduce la instalación de Windows con un entorno Python/CadQuery existente y compárala con el resultado en un entorno limpio descrito aquí. Se considera terminado cuando se hayan acordado las condiciones del entorno que se deben detectar y se haya documentado o probado el comportamiento de advertencia resultante.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

Hi CQ-editor team,

I'm a noob (as in "eager mechanical engineer and OpenSCAD user with no background in software development") assisted by Cascade (an AI assistant) and I encountered a situation with the Windows installer that I thought might be worth sharing.

Issue:
When I first ran the installer, it somehow picked up an old CadQuery 0.2.1 version instead of 2.4.0. Apparently existing Python/CadQuery installations were affecting the installation process. Maybe because I ran an old installer in the first place?

What Helped:
After succeeding with a Conda install (after many trials and errors and help from Cascade) I came back to the windows installer to see what was wrong and running it in a clean environment (thanks to a script Cascade created for me) solved the issue. The installer then worked perfectly, installing the correct versions.

Suggestion:
Would it be helpful to add an environment check to the installer? Maybe just a simple warning if it detects existing installations that might interfere?

Here is the script created by Cascade to run the installer in a clean environment, but I'm not sure if it will be useful to you as I'm quite new to this (to be saved as a .bat file):

@echo off
setlocal EnableDelayedExpansion

REM Save current PATH
set "ORIGINAL_PATH=%PATH%"

REM Create test directory
set "TEST_DIR=C:\CQ_Editor_Test"
if not exist "%TEST_DIR%" mkdir "%TEST_DIR%"

REM Copy installer to test directory
copy "contributing on CQ-editor Github\CQ-editor-master-Windows-x86_64.exe" "%TEST_DIR%"

REM Save current datetime for log
for /f "tokens=2 delims==" %%I in ('wmic os get localdatetime /value') do set datetime=%%I
set "LOGFILE=%TEST_DIR%\install_log_%datetime:~0,8%_%datetime:~8,6%.txt"

echo Testing CQ-editor installer > "%LOGFILE%"
echo Test started at: %date% %time% >> "%LOGFILE%"
echo Original PATH: %ORIGINAL_PATH% >> "%LOGFILE%"

REM Run installer
echo Running installer...
start /wait "" "%TEST_DIR%\CQ-editor-master-Windows-x86_64.exe"

REM Log post-installation PATH
echo. >> "%LOGFILE%"
echo Post-installation PATH: >> "%LOGFILE%"
echo %PATH% >> "%LOGFILE%"

REM Restore original PATH
set "PATH=%ORIGINAL_PATH%"

echo Test completed. Check %LOGFILE% for details.
echo Your original PATH has been restored.
pause

Note: You'll need to modify the installer path in the script to match where your CQ-editor installer is located on your system.

Thank you for creating such a great tool for the CAD community! I am so glad to finally be able to work with CadQuery after months of just reading the docs ^^U and quite a long journey to find my way to a working CQ-editor.

Please let me know if this contribution is worth at all, or if I could do better. I'll be more than happy to help.

Lenguaje dominante
Python
Estrellas
1.3k
Forks
211
Sin PR fusionados en 30 d

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de CadQuery/CQ-editor

Todos los issues de CadQuery/CQ-editor

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.