-
Notifications
You must be signed in to change notification settings - Fork 21
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
New enforce fork for Python 3.5.10, 3.6, 3.7, 3.8, 3.9 #76
Comments
Hi @SamuelMarks. Even though I am not sure about some changes, it'd be still awesome to have so much additional effort put into this project. And I'd feel honoured to have those updates back in the repo! Thank you very much for your work! |
@SamuelMarks will you send a PR? |
Oh I didn't realise this project was keen to reactivate. Sure, I'll send a PR now. |
sorry, didn't mean to imply that i was the owner -- i'd love to use this! |
@SamuelMarks alternately if you're actively developing your fork, that is awesome! i'd be happy to use/help if you need any |
@SamuelMarks sure, would be happy to help. first thing will be to use your version and poke around. will report back! |
BTW is there a reason you've turned off issues on your fork? we might want to move this conversation there |
Enabled. I think getting all tests to pass is the priority, the next priority is getting it merged into here (and if unsuccessful to continue on my fork). |
Some updates? |
Just started a new fork: https://github.com/SamuelMarks/enforce
New features / changes (thus far):
typing
s that are only valid for Python < 3.6Literal
(PEP586)Still a ways to go. Would welcome any and all contributions. Also open to offering all progress back to @RussBaz, if he wants to retake the reigns.
🙏
The text was updated successfully, but these errors were encountered: