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.
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
evtxpython package and thepython-evtxpackage on python for Windows.When
python-evtxis installed, its main module,Evtx, is accessible for import. However Windows is a case-insensitive system, and when subsequently installingevtx, it's main module,evtxthen ends up clobberingpython-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-evtxis installed, in the %PYDIR%\Lib\site-packages directory, the modules are stored in theEvtxfolder undersite-packages. Then installingevtxwill simply be seen as existing due to the presence of the currentEvtxfolder (since it matches based on case-insensitive behavior), and installevtxinto the same folder. Subsequent imports ofevtxfail because the module is stored inEvtx.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-evtxgithub page as well.