-
-
Notifications
You must be signed in to change notification settings - Fork 29
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unit tests fail on Windows #15
Comments
MyPy is really upset when I reference When I submit the patch please let me know if my complaint-avoidance solutions are acceptable. |
I'm also getting pylint errors saying "Optional is unsubscriptable". It appears that pylint has a fix coming but it isn't live yet. I'll recreate my environment using Python 3.8 for now. |
Thanks for getting Windows going! I'm trying to switch over to GitHub Actions in #17, and while some things are failing, some Windows tests are passing. Can you help me understand why yours fail but mine succeed, and how to make my GitHub Actions Windows tests more accurate for your environment? The pylint failures happen on 3.9, but not 3.8 I think. Don't worry about those, I will track them down :) |
Sure thing! I'll look at the results in #17 now. |
I've checked out scriv from master on Windows and ran the following commands:
Almost every tox environment failed. There appear to be multiple issues:
os.sep
is not respected. Tests for output relied on hard-coded paths likecall(['git', 'add', 'changelog.d/20130225_151617_joedev.rst'])
, but failed because Windows used backslashes in the command.Black attempted to reformat every file in the virtual environment, which took a very long time to fail. Errors like
error: cannot format venv\Lib\site-packages\docutils\languages\fa.py: I/O operation on closed file
appeared for what appears to be every file in the virtual environment. Until I fix this it may be difficult to zero in on the other issues due to sheer volume of output.make
is not available in my environment. This may be insurmountable in a Windows environment but I'll see if I can at least trace this.I'll work to resolve both of these issue and submit a patch.
The text was updated successfully, but these errors were encountered: