-
-
Notifications
You must be signed in to change notification settings - Fork 152
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
Current state of Windows support #379
Comments
Just linking to the docs section https://nox.thea.codes/en/stable/usage.html#windows. So, I've seen some PRs been merged to improve the windows support since last year (or maybe more?). Personally I don't use windows, so I can't say everything works fine, but the test suite runs on Windows as well https://github.com/theacodes/nox/blob/master/appveyor.yml. |
Windows should work fine at this point, we can probably remove that from
the docs.
…On Sun, Jan 31, 2021, 11:47 AM Santos Gallegos ***@***.***> wrote:
Just linking to the docs section
https://nox.thea.codes/en/stable/usage.html#windows.
So, I've seen some PRs been merged to improve the windows support since
last year (or maybe more?). Personally I don't use windows, so I can't say
everything works fine, but the test suite runs on Windows as well
https://github.com/theacodes/nox/blob/master/appveyor.yml.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#379 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAB5I436AHSQ32IFYJKBVUTS4WCRVANCNFSM4W3NH3ZQ>
.
|
I've started using nox on Windows. My configuration has poetry and conda. I would be happy to help try to replicate any Windows-specific problems if they arise The three related tickets linked in the documentation appear to be resolved and there hasn't been an update since ~2015. The recommended fix was to pass |
Cool, seems we should just update our docs to remove that section. :3
…On Mon, Feb 8, 2021 at 10:41 AM Kyle King ***@***.***> wrote:
I've started using nox on Windows. My configuration has poetry and conda.
I would be happy to help try to replicate any Windows-specific problems if
they arise
The three related tickets linked in the documentation appear to be
resolved and there hasn't been an update since ~2015. The recommended fix
was to pass shell=True or otherwise ensure that the custom environment
was properly configured for the 32-bit Python on Windows 8.1:
https://bugs.python.org/issue24493#msg250848
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#379 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAB5I443GHC5S2BGNV2YP2TS6AA2PANCNFSM4W3NH3ZQ>
.
|
* Docs: remove outdated notes on Windows compatibility Closes #379 * Docs: add Python Launcher notes to config section
Because tox has surprised me with some very confusing behavior lately, I was looking into converting my project to use Nox instead. Initial experiments have been very pleasant. However, one paragraph in the manual makes me wonder about the state of Windows support. It mentions "Nox has provisional support for running on Windows.", and then links to some tox, Python and virtualenv tickets.
Since that note was added to the manual 5 years ago, I wanted to check whether Windows support is still only provisional. Because of the links to non-tox issues, I'm assuming that Windows support in Nox will be roughly comparable to that in tox. Could that be correct?
The text was updated successfully, but these errors were encountered: