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 terry.reedy
Recipients Saimadhav.Heblikar, dstufft, rhettinger, terry.reedy
Date 2015-03-05.21:04:43
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1425589483.35.0.392987236512.issue23551@psf.upfronthosting.co.za>
In-reply-to
Content
Yes, this would complement your checker patch from last summer.  It would solve the issue of how to tell or help people, especially beginners, install packages to run with the checker.

Idea for the package manager: include an option to duplicate a set of installed packages from one version to another. A recent SO question (paraphrased): "Started with 2.7, installed multiple packages, added 3.4, can't use packages.  HOW???"  Current answer, with easily missed details, something like: "Packages must be installed for each version.  Use PIP to make requirements.txt (sp?) package list from 2.7 and use that to install same to 3.4."  Nicer answer: use option that gets details right.  Perhaps list could be checked for availability in 3.4.  Or displayed in text widget to be edited.

I look forward to your proposal.
History
Date User Action Args
2015-03-05 21:04:43terry.reedysetrecipients: + terry.reedy, rhettinger, dstufft, Saimadhav.Heblikar
2015-03-05 21:04:43terry.reedysetmessageid: <1425589483.35.0.392987236512.issue23551@psf.upfronthosting.co.za>
2015-03-05 21:04:43terry.reedylinkissue23551 messages
2015-03-05 21:04:43terry.reedycreate