Pyyaml: Is this time to pass the baton?

Created on 7 Aug 2016  路  12Comments  路  Source: yaml/pyyaml

This repo is nearing abandonware which is IMHO a sad thing.
I see @sigmavirus24 was trying to get something done a while back.
@dstufft started a sensible fork IMHO here https://github.com/dstufft/yaml
@ingydotnet @xitology what do you think?

Most helpful comment

Good news. I've been given permission to release PyYAML on PyPI and @ingy and I are working on taking over this and libyaml.

We will be doing releases soon.

Consider the baton passed. :)

All 12 comments

@authbox-lib I see you did some recent work with https://github.com/authbox-lib/pyyaml/commit/ca43af2062d4901cb6ca253677e7b3213bd56131 on top of @dstufft work.

@xitology I see you started to give this some love recently again at https://bitbucket.org/xi/pyyaml/commits/ ?
which is the master repo?

But there are also countless pull request there and this https://bitbucket.org/xi/pyyaml/issues/59/has-this-project-been-abandoned

To the best of my knowledge (citation needed) this is only a mirror of the bitbucket repo (so maybe issues should be disabled?).

Regarding forks, see also https://bitbucket.org/ruamel/yaml which, amongst other new features, supports YAML 1.2 and content-preserving roundtrips... https://yaml.readthedocs.io/en/latest/overview.html

@kwill yes, @ruamel fork is excellent and extends the C/Cython of the original pyyaml.
@dstufft fork has another tack: pure Python only.
and regardless where forks live the "main" forks here or on bitbucket are not what I would call "alive"

@pombredanne yes, we are talking to the author and working out a maintenance plan. @ingy is involved and helping things along. Please be patient.

Good news. I've been given permission to release PyYAML on PyPI and @ingy and I are working on taking over this and libyaml.

We will be doing releases soon.

Consider the baton passed. :)

FWIW @ingy is more commonly known as @ingydotnet :)

@sigmavirus24 @ingydotnet Congrats and thank you!

See also:

  • yaml/pyyaml#32
  • yaml/libyaml#11

Reopening until above issues are resolved.

IMHO the "baton" has been fully passed... And this should be closed.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

MartinDelVecchio picture MartinDelVecchio  路  3Comments

prometheanfire picture prometheanfire  路  6Comments

petmakris picture petmakris  路  3Comments

brianbruggeman picture brianbruggeman  路  9Comments

lucj picture lucj  路  7Comments