| msg214113 - (view) |
Author: Jurko Gospodnetić (Jurko.Gospodnetić) * |
Date: 2014-03-19 16:59 |
| On Windows, when you repair your Python 3.4 installation, it will not reinstall pip & setuptools. Here by 'repair' I mean a 'Windows Installer' based repair installation. Reproduced using: * Windows 7 SP1 x64. * Python 3.4.0 (32-bit). To reproduce do the following: * Install Python. * For example to the target installation folder: 'C:\Program Files (x32)\Python\Python340'. * This will automatically install pip & setuptools Python packages. * Delete or rename your target installation folder. * Rerun your Python installation and choose to repair the current installation. * This will restore the original target installation folder and all the basic installation files under that folder, but it will not reinstall pip & setuptols Python packages. |
|
|
| msg214115 - (view) |
Author: Martin v. Löwis (loewis) *  |
Date: 2014-03-19 17:41 |
| There is currently a condition in the installer to run ensurepip only if this is an installation (i.e. not an uninstallation); this should probably be extended to also run this on repair. Contributions are welcome. |
|
|
| msg216192 - (view) |
Author: Don DeZutter (DeZutter) |
Date: 2014-04-14 20:00 |
| On Windows 7 SP1 x64 after having installed Python 3.3 (x64) in “c:\Python33” and then subsequently installing Python 3.4 (x64) in “c:\Python34”, and then uninstalling the Python 3.3 (x64) and I’m not sure what else I may have done, I can no longer do any of the following: Open an IDLE window using the Windows Start Menu; Uninstall, Change, or Repair Python 3.4 using Windows Programs and Features; Uninstall Python 3.4 using Windows Start Menu; Reinstall Python 3.4 using the current 3.4 .msi install program. I would like to go back to being able to do a forced fresh install. I am a Python newby so maybe I should open a new incident but I don’t know how to start one yet. Perhaps I should try the previously described reproduce procedure by doing the following: Rename or delete target installation folder and then rerun Python installation procedure to install. |
|
|
| msg216276 - (view) |
Author: Martin v. Löwis (loewis) * |
Date: 2014-04-15 04:26 |
| Don: This is not a helpdesk system, but a bug tracker; the difference is that we don't help you here, but you help us. If you need help yourself, I suggest subscribing to python-list, at https://mail.python.org/mailman/listinfo/python-list and posting a question there. |
|
|
| msg216350 - (view) |
Author: Don DeZutter (DeZutter) |
Date: 2014-04-15 17:59 |
| Martin: Thank you for your prompt and helpful response to my attempt to tag along to a possibly similar bug. I had been working on my issue for about two weeks and truly believed it was a bug before i adventured as I did. As you know, the difference between a problem and a bug is who comes up with the fix. I continued working my issue and discovered I could reinstall by running msiexec with the "/l *v" option and again with the "/fa /l*v" option which forces all file files to be reinstalled. I still consider this to be a bug in the Python installer because the installer does not truly repair. But I am a happy camper now will use the python-list you recommended. Don DeZutter On Mon, Apr 14, 2014 at 11:26 PM, Martin v. Löwis <report@bugs.python.org>wrote: > > Martin v. Löwis added the comment: > > Don: This is not a helpdesk system, but a bug tracker; the difference is > that we don't help you here, but you help us. > > If you need help yourself, I suggest subscribing to python-list, at > > https://mail.python.org/mailman/listinfo/python-list > > and posting a question there. > > ---------- > > _______________________________________ > Python tracker <report@bugs.python.org> > <http://bugs.python.org/issue20983> > _______________________________________ > |
|
|
| msg404367 - (view) |
Author: Zachary Ware (zach.ware) * |
Date: 2021-10-19 22:19 |
| The installer system for v3.4 and before has long since been retired. |
|
|