- Python Home
- About
- News
- Documentation
- Downloads
- Community
- Foundation
- Developer's Guide
- Issue Tracker
- Issues
- Summaries
- User
- Administration
- Help
Message289402
This issue tracker has been migrated to GitHub,
and is currently read-only.
For more information,
see the GitHub FAQs in the Python's Developer Guide.
| Author | barry |
|---|---|
| Recipients | 0xl3vi, barry, serhiy.storchaka |
| Date | 2017-03-10.18:57:13 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1489172233.81.0.123965062281.issue29779@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
I don't think the Python envar has to follow the contraction from bash. $PYTHONHISTORY reads very nicely. I have similar code in my $PYTHONSTARTUP, but it would be nice to be able to get rid of it and just let Python do the common thing. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2017-03-10 18:57:13 | barry | set | recipients: + barry, serhiy.storchaka, 0xl3vi |
| 2017-03-10 18:57:13 | barry | set | messageid: <1489172233.81.0.123965062281.issue29779@psf.upfronthosting.co.za> |
| 2017-03-10 18:57:13 | barry | link | issue29779 messages |
| 2017-03-10 18:57:13 | barry | create | |

