Liveness of this project

[Lapin0t]

Hi, it seems that this project is quite alive, there are some pull requests and issues recently submitted but @aliles seems not to be around, is there anyone willing to step up as the official fork (@sh0oki I saw that you proposed that in #60)? That way the codebase doesn't die and if he comes back we can merge everything back.

[sh0oki]

@Lapin0t sounds good.

[evanunderscore]

I started on some branches to support choices via enums and pulling types from docstrings before I eventually decided to started fresh with defopt. I won't have time to finish those properly to merge into a fork, but if there's anyone who likes the features and would like to see them added to begins, they are more than welcome to use those as a starting point.

[isman7]

Hi, I discover this module by some book bibliography and I like it. I'm using inside two or thre projects. In one of them using CEFPython and Bottle, then I ended with double logging handlers. I forked the code, modify to accept a logger and handler instance, and come here to make a Pull Request, and arrived here!

So for me it is OK, I don't have enougth experience to fully mantain the code, but I'm here to contribute as much as I can.

@sh0oki you will have your first pull request in minutes! I've notice my solution is similar (but doesn't cover exactly the same than #61). I will study it to add it.

[isman7]

Ops, I just realized that you merged all together @Lapin0t. I've pull requested you also.

[Lapin0t]

Mmh, I never maintained any decent public project either (but it shouldn't be much harder than just quickly reviewing code before merging). The problem is that if we all start submitting pull requests to every other fork it's going to be unmanageable.

To digress a little bit, I think that this may be a design flaw of github (and any other current social coding service I know): everything is really centralized. You can fork things but there is a strong hierarchy between the fork and the original and there is no help at all to manage something in a distributed manner using only same-level repos (eg forks) (like what seems to currently happen on this project).

My first random idea: maybe forking is a bad practice and we should only have branches. That way we actually remove the notion of repo (because the interesting part in forking is what you change afterwards and that could have been done without bothering anyone with an unnamed branch). It's not that easy to think about ways to effectively distribute git (the protocol is distribution-enabled but no one is using that).

[dneise]

Hey, I guess one could contact @aliles via his website and ask about future plans of this project.

Also, if you are taking care of begins, maybe one can ask Aaron if you can also push to pypi.

[Jamim]

Hi folks,

Did someone try to contact @aliles?
Is there any chance that this project will be resurrected?

Thanks!

[sh0oki]

I tried a couple of times, got no answer. I guess the best option is restarting, a new python package and so on. WDYT?

…

________________________________ From: Aliaksei Urbanski <notifications@github.com> Sent: Tuesday, July 9, 2019 11:17 AM To: aliles/begins Cc: Elisha; Mention Subject: Re: [aliles/begins] Liveness of this project (#64) Hi folks, Did someone try to contact @aliles<https://github.com/aliles>? Is there any chance that this project will be resurrected? Thanks! — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub<#64?email_source=notifications&email_token=AB3GKZK2TEPNZJZEO2S4CVDP6RCQHA5CNFSM4CZM2YXKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODZPPTOA#issuecomment-509540792>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AB3GKZNXNK2G75RYRFNLT3DP6RCQHANCNFSM4CZM2YXA>.

[ulgens]

What about https://www.python.org/dev/peps/pep-0541/#continued-maintenance-of-an-abandoned-project

[AxelVoitier]

Hello,

I also would like to see this project being maintened. I had issues with the logging extension not being flexible enought, and fixed it with some tricks.
But since python 3.8, there had been changes in the base logging module that breaks my fix... I can refix it with additional tricks, but now it has to get dirty with monkey patching of begin ...

This package is already great as is, and I use it more and more. But it can have even more potential if the community can round the corners here and there.

I can volunteer as maintener if needed.
I don't care who will "own" the new master repo, because that does not matter much in the end.
But then come the choice of either trying to recover the pypi name (would make sense as nobody here seems to want to introduce breaking changes). Or truely fork to a different name for simplicity.

[sh0oki]

Sounds good! I tried emailing the original maintainer a couple of times with no luck. Maybe a new name is a better approach... How about pybegin for a new name?

…

On 23/01/2020 16:17, Axel Voitier wrote: Hello, I also would like to see this project being maintened. I had issues with the logging extension not being flexible enought, and fixed it with some tricks. But since python 3.8, there had been changes in the base logging module that breaks my fix... I can refix it with additional tricks, but now it has to get dirty with monkey patching of begin ... This package is already great as is, and I use it more and more. But it can have even more potential if the community can round the corners here and there. I can volunteer as maintener if needed. I don't care who will "own" the new master repo, because that does not matter much in the end. But then come the choice of either trying to recover the pypi name (would make sense as nobody here seems to want to introduce breaking changes). Or truely fork to a different name for simplicity. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#64?email_source=notifications&email_token=AB3GKZJMJJS3KAIUSZL5ZQLQ7GRJPA5CNFSM4CZM2YXKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEJXQEGA#issuecomment-577700376>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AB3GKZK3CNGGR55A2F5W5OLQ7GRJPANCNFSM4CZM2YXA>.

[harkabeeparolus]

Based on the previous comments in this issue, I think I will give up hope on this project and look at other alternatives. There seem to be other, current projects that follow the same design philosophy:

• The previously mentioned defopt by @evanunderscore and @anntzer looks promising. Putting the help text inside docstrings also makes the source code a lot prettier to look at than using decorators, in my opinion.
• Also Typer seems like it is worth investigating. It's a super simple interface on top of Click, which gives you both the power of Click and the simplicity of something like begins.

Does anyone else have further suggestions for actively maintained alternatives in the same spirit?

[isman7]

Hi there! I gave up on begins a year and a half ago, so I migrated everything to Click. Thanks for the recommendation of alternatives! Cheers, El lun., 27 ene. 2020 8:44, traal <notifications@github.com> escribió:

…

Based on the previous comments in this issue, I think I will give up hope on this project and look at other alternatives. There seem to be other, current projects that follow the same design philosophy: - The previously mentioned defopt <https://github.com/anntzer/defopt> by @evanunderscore <https://github.com/evanunderscore> and @anntzer <https://github.com/anntzer> looks promising. Putting the help text inside docstrings also makes the source code a lot prettier to look at than using decorators, in my opinion. - Also Typer <https://github.com/tiangolo/typer> seems like it is worth investigating. It's a super simple interface on top of Click, which gives you both the power of Click and the simplicity of something like begins. Does anyone else have further suggestions for actively maintained alternatives in the same spirit? — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#64?email_source=notifications&email_token=ACIKATBFKWF6QRLN2PYVJJDQ72GGFA5CNFSM4CZM2YXKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEJ6SMQA#issuecomment-578627136>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACIKATEOZFRSH5B722EWH5DQ72GGFANCNFSM4CZM2YXA> .