Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

when running a command, stdin requires a keypress on Windows

Open
#1,007 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
python
Domain
cli

Research direction

Start by reproducing the Windows pipeline type file.txt | inv doecho with the shown ctx.run('more') task, then trace how ctx.run handles stdin for child commands on Windows. Done means piped input is consumed without requiring an extra keypress, while direct command execution continues to work.

Written by the indexing model from the issue text.

Description

I am wanting to pass a file to the stdin of a command on Windows
type file.txt | inv doecho

where:

import invoke

@invoke.task()
def doecho(ctx):
    ctx.run('more')

more is run but waits until a key is pressed and then executes as expected. This is nothing to do with more.. the same result can be seen when running cat from cygwin or anything else that reads from stdin

Dominant language
Python
Stars
4.8k
Forks
412
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from pyinvoke/invoke

All issues in pyinvoke/invoke

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.