Release 0.6

[bradleyayers]

0.5 is now properly broken, with progressbar-2.3-dev being removed from pypi, Attest 0.5 does not even install. Could we please have 0.6 released onto pypi.

[superbobry]

+1, though I'm not sure if attest is even supported anymore

[bradleyayers]

if it's not supported, it should be passed onto someone who can support it…

[SimonSapin]

Short answer: no one is working on it right now, 0.6 has some nasty bugs, and nothing made since 0.5 is documented.

A while ago @dag said he wasn’t really working on Attest anymore. He gave commit access on github to @paradoxxxzero and me since we were making some patches. However only Dag has access to PyPI to make new releases.

With access to PyPI I could make a 0.5.3 release to fix the install. Doing a proper release the Right Way® for 0.6 would require more work.

It’s a bit sad for Attest, but I recently switched to pytest my last project that was still using Attest. The switch was triggered by some hard-to-fix bugs, but the main reason was that no one is maintaining it.

Anyone willing to take over the project is welcome to do so. I think that Dag would give access to Github an PyPI. I’m starting this discussion on pocoo-libs.

[bradleyayers]

I think I'll switch over to py.test too. It looks like it's got the nice things I liked about Attest, with a proper community behind it. Thanks for the tip Simon.

[dag]

I'll gladly push any releases or give you PyPI access. I personally don't really do any Python at all at the moment, myself. I also recommend pytest for new projects; I recall starting liking it before quitting Python - in part why I never got around to finishing the Attest 0.6 release.

[SimonSapin]

Dag, I just pushed a 0.5.3 tag that fixes the install. Can you upload it to PyPI?

[dag]

Could you do it, if I give you access? What's your PyPI username?

[SimonSapin]

Sure. Username is SimonSapin

By the way, what were the reasons for quitting Python? (I’m just curious.)

[dag]

Added.

My reason is that Haskell finally clicked for me. ;)

[SimonSapin]

0.5.3 is on PyPI and installs correctly. I’m leaving this issue open as 0.6 still needs work ... if anyone ever wants to do it.

In the meantime, I also recommend pytest. It has the same kind of assert statement introspection, so switching is not too hard.

[bradleyayers]

Ah Haskell is a worthy swap. Thanks for pushing the fix, now the spam of all my projects failing on jenkins should stop :)

[SimonSapin]

@bradleyayers , you may have seen today’s new pull request on Attest. I see that you have a few more recent commits in your fork. Do you want to officially take over the maintenance?

[bradleyayers]

Sure. I saw the PR, and I'll review it when i get a chance.

On 11/07/2012, at 5:34 PM, Simon Sapin [email protected] wrote:

@bradleyayers , you may have seen today’s new pull request on Attest. I see that you have a few more recent commits in your fork. Do you want to officially take over the maintenance?

---

Reply to this email directly or view it on GitHub:
#131 (comment)

[bfirsh]

What are the blockers for 0.6? I'd like to help get it out! (cc @bradleyayers @SimonSapin)

[bradleyayers]

From memory I believe it's just documentation, i.e. the new 'attest' command, changelog

[bfirsh]

@bradleyayers @SimonSapin Are there any other bits and bobs that need doing to get this ready for release?

[bfirsh]

Ping @dag @bradleyayers @SimonSapin @paradoxxxzero – is this maintained any longer? I am depending on Attest for a test library I'm writing and I would love to help roll a 0.6 release!

[SimonSapin]

I’m not maintaining Attest at all anymore, and AFAIK nobody is. If someone wants to take over maintenance, I can give PyPI access.

[bfirsh]

I would be willing to take over. My PyPi username is bfirsh.

[SimonSapin]

You’d have to ask @dag for push access to this repo, or fork it.

[dag]

Added.

[SimonSapin]

Added on PyPI.

[bfirsh]

Thanks both! I shall take a look at this next week sometime.