-
Notifications
You must be signed in to change notification settings - Fork 40
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
Switch from fork to start_soon #62
Conversation
CI is mad because it's trying to use Python 3.6. I could update: cocotb-bus/.github/workflows/tests.yml Line 30 in 3c93452
but I'm going to take a beat to see if I'm pulling on a thread that requires more thought than I'm putting into it. Also, I'm guessing this should be updated to whatever the correct supported versions of cocotb would be: Line 33 in 2c846dc
But I'm also not sure what to put there. |
cocotb is now 2.0.0.dev0, so: |
For the |
Yeah, I was more uncertain about the starting point. Looks like
So we can probably start at 1.6.0: |
Thanks, I can try this. But should these tests just run on a newer version of Python instead? Maybe I'll try that first. |
1.6 adds start_soon()
Ignore attrs warning
@toddstrader ,
|
Additional patches |
#75 (once merged) makes CI work again, but it doesn't pass because of the issues fixed by this PR. @toddstrader Would you mind updating this PR (resolve conflicts and add the changes that @jahagirdar mentioned), or are you okay with me doing it? |
@cmarqu if you're willing please do. We abandoned ship on cocotb-bus since trying to keep cocotb and cocotb-bus coherent in this interstitial period between v1 and v2 is quite painful. |
Hi @cmarqu What's the state of this PR? |
Nothing new. I'll try to take a look at it soon. |
Replaced by #78 |
Closes #61 I've
s/fork/start_soon
which resolves my particular problem, but I have no idea if this is generically correct. Also, I don't know how far backstart_soon
goes in cocotb, so clearly this would break some people until they also update cocotb.