-
Notifications
You must be signed in to change notification settings - Fork 43
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
Come talk Gilectemy on Talk Python Podcast? #38
Comments
As a Talk Python To Me listener I ask that you please do this Larry. |
I see no movement on the project since a few months. Does it mean there is no realistic gilectomy on Cpython, and our only hope is an up-to-date pypy ? |
Gilectomy was our only hope. A proven approach. A great business model. Actually I need this for my own I just do not have the capital to work on it full time. I just completed http://blogory.org/python and need to make some money. But if a company like DropBox or Goldman Sachs were kind Forgive me if proprietary concerns prevent me from answering specific questions I head off on vacation in a few minutes and will be off-line until December 30th. First of all it is a huge need. As far as I can tell Python is doing poorly because it does not support simultaneous mult-threading. And the bar is not that high. Linode offers me a 20 core server. Even |
Hi Larry,
I know this is not strictly an issue didn't really belong here but for some reason I'm having a hard time finding your email address or twitter or some other way to contact you directly so here you go.
I think this would make a great topic on my podcast Talk Python To Me. I love to have you on as a guest. What do you say? Interested? We got to talk about other things like Pytho3, the release management process things like that.
Thanks,
Michael
The text was updated successfully, but these errors were encountered: