Please release a version to PyPI

[hggh]

would be nice if we can release a version to pypi.

[SEJeff]

Give us a week or so to look through the existing backlog of tickets and merge any outstanding PRs, but this should be doable soonish.

[hggh]

👍

[mleinart]

I dont see a problem uploading a version of some kind, but I'll note that graphite components have always been released lockstep with everything on the same version. Given that the master branch of carbon still doesnt have ceres support merged in, that isn't possible in this case.

Perhaps we just name this 0.10.dev1 or 0.10.a1 - that looks to be what PEP-0440 wants.

[krak3n]

Didn't get round to it then 😛

[deniszh]

I'm wondering if ceres compatible with master carbon... Maybe somebody knows. @iain-buclaw-sociomantic ?

[deniszh]

I created issue #45 for discussing Ceres future.

[iain-buclaw-sociomantic]

Ceres is not only compatible with master carbon, it runs using half the CPU!

I think megacarbon should be considered dead, as the various PRs I raised last year pretty much hammered the final nail in its coffin - graphite-project/carbon#484, graphite-project/carbon#508, and graphite-project/carbon#596.

[deniszh]

That's great, @iain-buclaw-sociomantic !
Then we still have a chance to include it to Graphite properly. :)

[iain-buclaw-sociomantic]

Yep. Although I use graphite-api here, the last test I did using graphite-web appeared to be successful with a cursory test (graphite-project/graphite-web#1719 (comment)). I think there are some known problems with brace matching in the ceres reader however, I'm not sure though, so don't hold me to that. :-)