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

Unintentional clobbering on Windows

Abierto
  • ¿Algo no está bien?
#99 0 comentarios 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
Error
Claridad
Necesita aclaración
Estado de actividad
Tranquilo
Stack tecnológico
python

Línea de trabajo

The report describes a collision between the Evtx module from python-evtx and the evtx module from another package on Windows, but names no files, tests, or proposed change. Start by examining how this project packages and installs its module, then assess whether the collision can be addressed within this repository. Done means both packages can be installed in one Windows environment without clobbering imports; the issue gives no test or implementation path.

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

Descripción

I raised this issue at the other repo mentioned in the content below, however am simply copy/pasting it since the issue applies somewhat equally to both:

Not specifically sure how you might want to deal with this issue, or if you do, however there is a clobbering issue between the evtx python package and the python-evtx package on python for Windows.

When python-evtx is installed, its main module, Evtx, is accessible for import. However Windows is a case-insensitive system, and when subsequently installing evtx, it's main module, evtx then ends up clobbering python-evtx (and vice-versa depending on the which one is installed first). Because python is case-sensitive, it's only going to see the one "evtx" folder, and case-sensitive imports will fail if the intended import comes from the package doing the clobbering.

For example, when python-evtx is installed, in the %PYDIR%\Lib\site-packages directory, the modules are stored in the Evtx folder under site-packages. Then installing evtx will simply be seen as existing due to the presence of the current Evtx folder (since it matches based on case-insensitive behavior), and install evtx into the same folder. Subsequent imports of evtx fail because the module is stored in Evtx.

I am aware that the best approach to this separation is a venv, and am prepared to work that way as necessary. However, this will occur even in a venv when both packages are installed in the venv.

I just figured it would be a good idea to bring this up in case you weren't aware. I'll be bringing up the same issue at the python-evtx github page as well.

Lenguaje dominante
Python
Estrellas
785
Forks
170
Merge medio
2 d 21 h
PR fusionados (30 d)
1

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 williballenthin/python-evtx

Todos los issues de williballenthin/python-evtx

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.