pyvenv: activate.fish breaks $PATH for bash scripts

Open
#70,864 3 comments 0 reactions 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
Mostly clear
Activity status
Stale
Tech stack
bash, fish, python
Domain
cli, devtools

Research direction

Start by locating the pyvenv-generated activate.fish script and reproduce the reported behavior by activating an environment before running a bash script. Compare the resulting PATH with the expected environment PATH; done means bash scripts retain a usable PATH after activation.

Written by the indexing model from the issue text.

Description

stdlib type-bug
BPO 26677
Nosy @vsajip

Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.

Show more details

GitHub fields:

assignee = None
closed_at = None
created_at = <Date 2016-03-31.15:49:21.729>
labels = ['type-bug', 'library']
title = 'pyvenv: activate.fish breaks $PATH for bash scripts'
updated_at = <Date 2016-04-05.17:46:31.201>
user = 'https://bugs.python.org/FlorianDold'

bugs.python.org fields:

activity = <Date 2016-04-05.17:46:31.201>
actor = 'Goneri Le Bouder'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2016-03-31.15:49:21.729>
creator = 'Florian.Dold'
dependencies = []
files = []
hgrepos = []
issue_num = 26677
keywords = []
message_count = 2.0
messages = ['262696', '262916']
nosy_count = 3.0
nosy_names = ['vinay.sajip', 'Florian.Dold', 'Goneri Le Bouder']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue26677'
versions = ['Python 3.5']

Dominant language
Python
Stars
77.2k
Forks
36k
Avg merge
1d 9h
Merged PRs (30d)
558

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 python/cpython

All issues in python/cpython

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.