-
Notifications
You must be signed in to change notification settings - Fork 12
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
Windows support? #59
Comments
Hey @chrizzFTD thanks for attempting to give it a try 😄 Yes, unfortunately no Windows support yet 😢 It should be possible to use the spawn method from You're very welcome to try and add it yourself though I have no idea it will work out of the box. I've made #60 for that specific task and then hopefully adding it solves this 👍 |
@chrizzFTD mind trying out #61's branch to see if it works for you on windows? |
Yes, thank you so much for taking a look so quickly @tgoodlet 😃 I've left some updates on #61 (comment), but in short, the only issue I'm seeing is (because of the same windows deal):
I'm keen on helping testing as much as possible! |
@chrizzFTD awesome!
Indeed. I'll coordinate with you on #61. |
This is very hacky and pokes around in `trio` internals but it *should work* as it piggy backs on the new cross platform subprocess support. Relates to #59
This is very hacky and pokes around in `trio` internals but it *should work* as it piggy backs on the new cross platform subprocess support. Relates to #59
Hmm I wonder if part of solving this should be adding a CI job too. Oof but no python support yet.... |
@njsmith tipped me to free vms from microsoft for testing purposes as well. |
This pokes around a little in `trio` hazmat but it *should work* as it piggy backs on the new cross platform subprocess support. Relates to #59
Just an update, as of #61 and #62 we do have working windows support both verified in manual testing by @chrizzFTD and now in travisCI. There's still some kinks to work out (unreliable CI builds it seems) as well as some more documentation needed to get windows users working well with |
The unreliable CI builds seem to be either a race condition in determining the "arbiter" actor or some weird issue with being unable to find the I want to get #79 docs complete before considering this done as well. |
Also need to update the listed OS support in |
Thanks to @salotz for pointing out that the first example in the docs was broken. Though it's somewhat embarrassing this might also explain the problem in #79 and certain issues in #59... The solution here is to import the target RPC module using the its unique basename and absolute filepath in the sub-actor that requires it. Special handling for `__main__` and `__mp_main__` is needed since the spawned subprocess will have no knowledge about these parent- -state-specific module variables. Solution: map the modules name to the respective module file basename in the child process since the module variables will of course have different values in children.
Thanks to @salotz for pointing out that the first example in the docs was broken. Though it's somewhat embarrassing this might also explain the problem in #79 and certain issues in #59... The solution here is to import the target RPC module using the its unique basename and absolute filepath in the sub-actor that requires it. Special handling for `__main__` and `__mp_main__` is needed since the spawned subprocess will have no knowledge about these parent- -state-specific module variables. Solution: map the modules name to the respective module file basename in the child process since the module variables will of course have different values in children.
Thanks to @salotz for pointing out that the first example in the docs was broken. Though it's somewhat embarrassing this might also explain the problem in #79 and certain issues in #59... The solution here is to import the target RPC module using the its unique basename and absolute filepath in the sub-actor that requires it. Special handling for `__main__` and `__mp_main__` is needed since the spawned subprocess will have no knowledge about these parent- -state-specific module variables. Solution: map the modules name to the respective module file basename in the child process since the module variables will of course have different values in children.
Hi, this looks like a great project!
I wanted to give it a try but after installing via
pip install git+git://github.com/tgoodlet/tractor.git
, importing tractor fails because forkserver seems to not be available on my os (windows10):Any plan on adding windows support in the future?
The text was updated successfully, but these errors were encountered: