Add changes in 2.13 dev version floating around - #2
Conversation
|
@dan-blanchard perhaps this is better suited to go on a |
|
That's a reasonable idea, although I'd be more inclined to call the branch Unfortunately, I don't think I can create a PR for a branch that doesn't currently exist. You should be able to create one and then follow the manual merge steps that show up in the "Merge pull request" box to merge it in there instead. |
|
Of course, just discussing this idea here :) If I do end up opening a dev branch I'll likely merge the #1 changes into it as well. Hopefully, we might be able to get some traction going and revive the project as a fork. |
|
Cool. I didn't know about Pyped, I'd say that project probably has more traction and I wouldn't waste any more time on a NIH fork. |
|
That project hasn't really been updated in over a year, whereas the dev version I have here is from February. So traction is all relative here. 😄 |
|
I'm open to any discussion about merging projects. Pyped is quite stable, although I wish to add exception skipping to it and maybe turn on the auto print by default. Some unit tests also need updating and the doc could do with some gif. All in all, I've met 2 other projects doing the same thing so merging make sense to me. I'm currently on a trip but feel free to carry on the discussion and i'll catch up with you in a week. 14.08.2015, 23:20, "Dan Blanchard" notifications@github.com:That project hasn't really been updated in over a year, whereas the dev version I have here is from February. So traction is all relative here. —Reply to this email directly or view it on GitHub. |
|
Ok, I'm more available now. What do you have in mind ? |
I've just taken the code that they linked to on the Google Code page (that they never actually committed) and added it to the repo. Since Google Code is going to get shutdown soon, it seemed like a good idea.