Since everyone is a volunteer, Cathy, there are unfortunately no real timelines. It really comes down to someone who feels they have the knowledge necessary to review the PR having the spare time to do so. So emailing here and saying, "my PR has addressed all the comments and has been ready to go for 29 days; anything else I can do?" is the right thing to up the PR's exposure.

On Thu, 17 Aug 2017 at 08:02 Cathy Avery <cavery@redhat.com> wrote:

Hi,

I have a python pull request https://github.com/python/cpython/pull/2489
that introduces AF_VSOCK to the python C socket module. Unfortunately
things have gone quiet for several weeks. Since I am new to this process
I am unclear on what to expect as the next steps. I believe I have
addressed all issues. If I am mistaken please let me know. A real
functioning test setup is a bit painful and I would be happy to help in
anyway I can. The Microsoft Hyper V team is now introducing support of
vsock in the upstream linux kernel so its adoption is spreading amongst
the various hypervisors.

Any guidance on the basic timelines would be very helpful.

Thanks,

Cathy

_______________________________________________
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: https://mail.python.org/mailman/options/python-dev/brett%40python.org