Alex
Alex
Updated docs available at https://github.com/go-enry/go-enry#use-cases
@pombredanne sorry for delayed response. Although I would be happy to maintain enry in some low profile mode even without the company support, I do not expect it to be...
> I could also probably help on maintaining it as we need it for Gitea project :) I have just release a post-srcd version at https://pkg.go.dev/github.com/bzz/enry/v2 but will be happy...
After a very brief conversation with @mcuadros and @kuba-- and @lafriks comment above - a consensus seems to emerge: - I'm volunteered to do some long-delay maintenance on the https://github.com/bzz/enry/pull/4...
@pombredanne Enry's new and all the further releases are going to available at https://github.com/go-enry/go-enry/releases/tag/v2.3.0 🎉
At current state, simplistic version of this is possible by hard-coding log statements in ```diff diff --git a/common.go b/common.go index 949db71..d4a6c57 100644 --- a/common.go +++ b/common.go @@ -3,11 +3,14 @@...
This is just nice-to-have for now: the use case listed above is addressed in lookout by incorporating language in DataServer API https://github.com/src-d/lookout/pull/131
I've started adding it during OSD and will push simple WIP with CPython extension by cffi soon
Issue description updated to include the scope.
Makes perfect sense, esp. given https://github.com/src-d/guide/blob/master/engineering/conventions.md#operating-system-support \cc @smola