new_session raises TmuxObjectDoesNotExist even though the session name is new

Open
#599 3 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
api

Research direction

Start by reproducing new_session with the session name 'pain' using libtmux 0.46.2 on Ubuntu, and record the tmux version with tmux -V. Done means a new session is created without raising libtmux.exc.TmuxObjectDoesNotExist.

Written by the indexing model from the issue text.

Description

Environment:
libtmux version: 0.46.2
Python version: 3.12
tmux version: [run tmux -V]
OS: UBUNTU
Expected Behavior:
A new session named 'pain' should be created without errors.
Actual Behavior:
Raises libtmux.exc.TmuxObjectDoesNotExist even though the session name is new and doesn’t already exist.

Image

Dominant language
Python
Stars
1.2k
Forks
127
Avg merge
2h 13m
Merged PRs (30d)
1

Contributor guide

Open the contributing guide

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 tmux-python/libtmux

All issues in tmux-python/libtmux

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.