Skip to content
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

Should this pep need to be finalized and implemented before python 3.6 feature freeze? or what are the thoughts regarding this? #23

Open
auvipy opened this issue Nov 17, 2015 · 5 comments

Comments

@auvipy
Copy link

auvipy commented Nov 17, 2015

just willing to know to participate/help in the process

@rbtcollins
Copy link
Contributor

I know graham and cory are planning to get this moving again soon, but I don't htink the Python release schedule has much bearing on it.

@auvipy
Copy link
Author

auvipy commented Nov 17, 2015

thank you for bringing the light :)

@Lukasa
Copy link
Contributor

Lukasa commented Nov 17, 2015

Correct.

I have no expectations of this being done even remotely quickly. I'm willing to take up stewardship of this process from @rbtcollins (assuming he kindly volunteers to stay involved in the process!), but updating the WSGI specification is going to be a lengthy and arduous process I suspect, so I would not hold my breath if I were you @auvipy.

@auvipy
Copy link
Author

auvipy commented Nov 17, 2015

thanks again :)

@auvipy
Copy link
Author

auvipy commented Dec 7, 2015

http://bugs.python.org/issue23794 associated bug

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants