When the new PyPi release will be published?

[svetlyak40wt]

No description provided.

[MSeal]

There's been a few things merged but nothing active in the past couple weeks. @davidbrochart any reason we shouldn't snap a release?

[davidbrochart]

Sorry, I skipped that one with the holidays. I think we can make a release, yes. I'll do it tomorrow.

[davidbrochart]

While making the 6.1.7 release, I can see it already exists on PyPI. I'm not sure who made the release, but this repo was not updated accordingly. How can we proceed?

[davidbrochart]

I just released 6.1.8, but not following the releasing steps is very bad, we need to make sure this doesn't happen again in the future.

[davidbrochart]

I had to release 6.1.9 because of a jedi issue. I just pinned jedi<=0.17.2 for now, but we should come up with a proper fix in the future.

[davidbrochart]

It would be good if someone with "admin" rights to the PyPI project could yank 6.1.8.

[davidbrochart]

And 6.1.10 is released! Three releases in one day, I hope it's the last one 😄
Again, it would be good to yank 6.1.9 in PyPI.

[svetlyak40wt]

Thank you, @davidbrochart!

[bollwyvl]

Unfortunately, I think pinning jedi on #596 was not the right play... this actually adds an unused dependency (with a troubled history of versioning) to an upstream of the place where the problem exists. This would make the ipykernel IPython test infrastructure not fail, which would hide this versioning bug.

ipython/ipython#12751