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
Size of signal.py #943
Comments
+1000! Actually this touches a deeper issue that we should discuss. Currently we have I would like to propose the following alternative:
What do you think? |
Ok I'm all for your suggestion @francisco-dlp - I can't remember where we had that discussion before, but that is also my recollection of the conclusion. I'm happy to do the grunt work on initially separating out the code, the question is when? ASAP and for v1.0.0 or (given it will break so much for everyone) - do we take this as a 1.1.0 target and warn everyone now that it's coming? |
I think that 1.0 is appropriate for this. Even |
I've set the milestone to |
Addressed by #963 |
signal.py is getting very big and is expanding rapidly as people add more and more functionality.
What is, or should be, our strategy for keeping this manageable? Presumably some separation of code to different places in a rational way, but what might the different sections of code be?
The text was updated successfully, but these errors were encountered: