-
Notifications
You must be signed in to change notification settings - Fork 18
Active fork of grumpy #68
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
Comments
I am highly supportive of this effort but...
|
There are 2 ways
Anyway I would like to maintain or cowork this project as a new grumpy org not someone's repository. |
Hi. First of all, thanks for you support. I am preparing to publish an article detailing the new features of my branch. If you can, please leave comments before I do release it next week: https://labs.getninjas.com.br/unfinished-draft-released-grumpy-runtime-v0-3-0-a05f1cf8e111
In fact is not hard to support both for now. I do think about a command line switch, or even try to parse as Py3 and fallback to Py2. But the way to do it is not important now I guess. Better is to have the only Python 2-and-3 compatible runtime and maybe let projects mix both flavors to ease the upgrade to Py3. When messing with the compiler, made clear to me that many Py3 features are just compatible with Py2, and as easy or easier to implement. For exemple the PEP-3174 (
In fact, personally I am committed to push Grumpy until Python 2.7 EOL. If it does not be close to substitute Python 2.7 there, I will see it as sink cost of my bandwith and stop. The whole work I made in this time after forking is all about making easier/appealing for new people to contribute. Now the job will be of getting more hands to help. Please take a look at the article I linked up. I do think it is a lot more welcoming than before, but maybe not enough.
I had hold myself from a hard-hard fork until have something useful/better to show. And this repo here have 9k starts that will not be pulled over. Was hoping Google to create the organization and hand it over (what you think @trotterdylan ?). But is time to do the new organization :/ We may create a whole new organization, like grumpyorg/grumpy, or put it on https://jazzband.co one. What do you think? |
Yes, is time to create a grumpy.org / grumpy. Few things should be discussed.
Please understand my short English thanks! |
@alanjds |
Your english is damn good for me.
Sad on pyston repo :/ Corporates sometimes have odd decisions. At least Google is not Facebook nor Oracle and Grumpy is Apache 2 already. Thanks for all the code I could not write myself 😘. |
Yesterday I published grumpy-tools v0.2.1, and now all the article examples do work. I want to public publish the article this week. However there is one feature on the Should it be included? |
Other thing: will we create the grumpyorg to include in the article or publish another later pointing people to it? Have you a preference on a new organization or jazzband? |
Merged the If nothing new cames, I should release the article Tuesday 17. |
@alanjds I think it's better to move this active fork to another organization with python 3 support. |
@rezaghanbari Ok. Will create a new organization instead of jazzband, and will invite all you 🙈 ❤️ Python 3 support is a matter of listing the features and start implementing. Most missing stuff is needed both on Python2 and Python3: Right now I am on the quest to support Btw, is released the |
Huh, @grumpyorg is now taken. I saw it available last week. What will be the new name now? |
@alanjds what about combination of grumpier and org? |
Taken too :/ |
grumpyhome is available |
The new grumpy home is at https://github.com/grumpyhome/grumpy ! |
Closing, as the new home is now here. Thanks @funny-falcon and others for the good feedback and motivation to keep going. |
google#406 opened by @funny-falcon on Jul 4
Looks like @alanjds maintains active fork of this project https://github.com/alanjds/grumpy
Lets support him with our attention!
The text was updated successfully, but these errors were encountered: