sync up with uvloop fork that I have to allow people to start testing it.#127
Merged
sync up with uvloop fork that I have to allow people to start testing it.#127
Conversation
… it all-platform version
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What do these changes do?
Note
We are extremely close to what I will consider to be The Endgame Of Winloop minus a few miscellaneous thingies going on.
This is based off the current pull request being taken place We are very close to where we can finally deprecate our project. I wanted to ensure these were 1 to 1 so that people could more easily report any suspicious behaviors a little more quickly since uvloop takes a bit of time to make and merge a pull request. This does have the hidden ability of being all-platform even though it's not being widely distributed so feel free to test it out for yourself.
When I get back home from work today I will continue to tweak the tests as needed and start finalizing modifications to the current test-suite.
I am aware of #126 but I'm still a bit busy. However if I decide to sit down with it in the next few days when I get time off from work this might be the final bug we tackle if none else are currently being reported.
Are there changes in behavior for the user?
Warning
Compile to other platforms at your own risk!!!! Tests might break on other platforms so be extremely careful and cautious!
Is it a substantial burden for the maintainers to support this?
Related issue number
Checklist