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 steve.dower
Recipients chrullrich, paul.moore, steve.dower, tim.golden, zach.ware
Date 2015-09-23.01:16:32
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1442970992.28.0.033934392543.issue25166@psf.upfronthosting.co.za>
In-reply-to
Content
Burn is always started in the per-user scope so that we can do per-user installs without elevating, but it looks like we need to manually change this once we know it's an all-users install.
History
Date User Action Args
2015-09-23 01:16:32steve.dowersetrecipients: + steve.dower, paul.moore, tim.golden, zach.ware, chrullrich
2015-09-23 01:16:32steve.dowersetmessageid: <1442970992.28.0.033934392543.issue25166@psf.upfronthosting.co.za>
2015-09-23 01:16:32steve.dowerlinkissue25166 messages
2015-09-23 01:16:32steve.dowercreate