Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Errno 32] Broken pipe on command output (reggression or PR #236) #279

Closed
mrjk opened this issue Nov 11, 2022 · 1 comment
Closed

[Errno 32] Broken pipe on command output (reggression or PR #236) #279

mrjk opened this issue Nov 11, 2022 · 1 comment

Comments

@mrjk
Copy link

mrjk commented Nov 11, 2022

Hey, I was almost close to necro-bump #236 , but it seems this patch is not available on cleo-1.0.0a5 anymore. I discovered that while using a recent version of poetry:

$ poetry version  --dry-run -s patch | head -n 1
0.1.1

[Errno 32] Broken pipe
Exception ignored in: <_io.TextIOWrapper name='<stdout>' mode='w' encoding='utf-8'>
BrokenPipeError: [Errno 32] Broken pipe

Current version of cleo and potry (which use cleo):

$ poetry --version
Poetry (version 1.2.2)

$ pip freeze | grep cleo
cleo @ file:///~/.cache/pypoetry/artifacts/1c/64/4e/3535588c61539bf8675d193a6dca8b9541451019ae21fb31af535f0643/cleo-1.0.0a5-py3-none-any.whl

The git history of cleo is not very clear to me, I didn't really understood what happened between this PR, the main branch and the 1.0.0a5 tag. I also opened a bug in the poetry project #7014.

@mrjk mrjk changed the title [Errno 32] Broken pipe on command output (reggression #3602) [Errno 32] Broken pipe on command output (reggression or PR #236) Nov 11, 2022
@Secrus
Copy link
Member

Secrus commented Nov 12, 2022

Currently, we are working on releasing Cleo 1.0, which includes a lot of fixes. What you see on main, is unfinished 1.0. Tag 1.0.0a5 was a release that started our work on restoring Cleo to a proper shape.

TL;DR not a regression, #236 is not released yet.

@Secrus Secrus closed this as completed Nov 12, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants