virtualenv deactivate doesn't self-destruct on ksh: needs unset -f
Bug #422539 reported by
William Shallum
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Virtualenv |
Fix Committed
|
Undecided
|
Jannis Leidel | ||
Bug Description
Virtualenv's deactivate function tries to erase itself by running "unset deactivate". Unfortunately this does not work on ksh (ksh93 version 93t, 2008-11-04). Please use "unset -f deactivate" as this also works on bash and zsh.
Test script is attached
Revision history for this message
| William Shallum (william) wrote | #1 |
| Changed in virtualenv: | |
| status: | New → Fix Committed |
| assignee: | nobody → Jannis Leidel (jezdez) |
Revision history for this message
| William Shallum (william) wrote | #2 |
Revision history for this message
| Jannis Leidel (jezdez) wrote | #3 |
Revision history for this message
| Carl Meyer (carljm) wrote | #4 |
To post a comment you must log in.
Unfortunately the encoded file in virtualenv.py was not updated along with the patch (tested with release 1.3.4). Please update the encoded file too.