[program-l] Re: Installing python 3.10 on a brand new machine - No module named 'pip'

  • From: jacob kruger <jacob.kruger.work@xxxxxxxxx>
  • To: program-l@xxxxxxxxxxxxx
  • Date: Tue, 22 Nov 2022 13:50:20 +0200

Just another update - 3.9 started doing the same thing as well after a restart or two.


Have now just installed a clean copy of 3.11, and, it seems to be working - maybe I'll try create a restore point, just in case, to see if that can undo any change if this now reoccurs.


Jacob Kruger
+2782 413 4791
"Resistance is futile...but, acceptance is versatile..."


On 2022/11/21 11:05, Jacob Kruger wrote:


Ok, tried a couple of things, including double-checking install paths and environment variables, running processes as administrator, etc, etc, but same kept reoccuring.

However, when just switched over to last stable/full release of python 3.9 = 3.9.13, everything started cooperating again, so, think will just stick to that version for now.

Jacob Kruger
+2782 413 4791
"Resistance is futile...acceptance is versatile..."

On 20 November 2022 02:03:28 <joeldodson@xxxxxxxxx> wrote:

Hi Jacob,

Apologies if you’ve already mentioned this, but did you install python from the Windows store or by downloading it from python.org?

I’ve always installed from the python.org download (and have to manually update dot releases) and taken the default options and have no problems creating virtual environments.  These days I use:

python -m venv –prompt=blah .venv

I recently installed 3.11.0 locally and one of the questions was whether to add python to the path.  I don’t recall the default setting.

I also recall in the past having to add something manually to my path, not sure if that was python related though.

I know hearing “it works on my machine” can incite violence (you’re probably a better person than I am though), hopefully this at least is something to consider.

Cheers,

Joel

*From:* program-l-bounce@xxxxxxxxxxxxx <program-l-bounce@xxxxxxxxxxxxx> *On Behalf Of *kperry@xxxxxxxxxxxxx
*Sent:* Saturday, November 19, 2022 7:40 AM
*To:* program-l@xxxxxxxxxxxxx
*Subject:* [program-l] Re: Installing python 3.10 on a brand new machine - No module named 'pip'

That is strange.    I have started using pyenv-win because of the problems like this at time.  My only suggest is this.  Remove python, Look in your user directories under roming and local etc. Remove all python stuff there.  Look in program files and 86x folders and remove all python stuff there.  Finally Install your python to something like a c:\data\tools folder so you can control it better.  Reboot after all that is removed. Finally   Then remake your venv stuff. After all that things should work.  This is one reason I use pyenv-win even if it is hard to get installed at first.  Once it is installed I can change my python version with a single command line and don’t run into these problems.*From:* program-l-bounce@xxxxxxxxxxxxx <program-l-bounce@xxxxxxxxxxxxx> *On Behalf Of *jacob kruger
*Sent:* Saturday, November 19, 2022 1:32 AM
*To:* program-l@xxxxxxxxxxxxx
*Subject:* [program-l] Re: Installing python 3.10 on a brand new machine - No module named 'pip'

Ken, I am fully aware of that ;)

Just tried out venv now, and, same thing - even if activate virtual environment, and then actually navigate to the venv/Scripts directory, and then tell it to execute pip.exe from there am getting a similar error - almost like python's installation itself was not complete, is lacking some dependencies, etc.

Will maybe try something like python 3.9, and see if that makes a difference on this machine.

Or else will try out poetry shell first, although would rather, overall stick to either virtualenv or venv.

Stay well


Jacob Kruger
+2782 413 4791
"Resistance is futile...but, acceptance is versatile..."

On 2022/11/18 19:49, kperry@xxxxxxxxxxxxx wrote:

    When you are in a virtual inv your script directory is different.

    *From:* program-l-bounce@xxxxxxxxxxxxx
    <program-l-bounce@xxxxxxxxxxxxx>
    <mailto:program-l-bounce@xxxxxxxxxxxxx> *On Behalf Of *Jacob Kruger
    *Sent:* Friday, November 18, 2022 12:17 PM
    *To:* program-l@xxxxxxxxxxxxx
    *Subject:* [program-l] Re: Installing python 3.10 on a brand new
    machine - No module named 'pip'

    Sorry - should have mentioned, that would be first thing would
    check, and, before activating virtual environment, pip worked
    fine installing virtualenv package, for example.

    Thinking, should maybe also try out venv, or poetry shell virtual
    environments, and see if have similar issues.

    Jacob Kruger
    +2782 413 4791
    "Resistance is futile...acceptance is versatile..."

    On 18 November 2022 17:20:57 <kperry@xxxxxxxxxxxxx> wrote:

        You need to add the pip path to your environment.  It doesn't
        matter if you install it for everyone or justone user.  It
        works fine either way.  I like to install it in a tools
        directory.  My setup is:

        C:\data\tools\python
        If I remember correctly the pip is under
        pythonlib/site-packages.  Find it first and set the
        environment to it

        That way it is not under program files and I can have better
        access to the packages without using administrator.  I do
        have administrator of course I just like it to be in a tools
        directory with all my other compilers etc.

        -----Original Message-----
        From: program-l-bounce@xxxxxxxxxxxxx
        <program-l-bounce@xxxxxxxxxxxxx> On Behalf Of jacob kruger
        Sent: Friday, November 18, 2022 9:03 AM
        To: program-l@xxxxxxxxxxxxx
        Subject: [program-l] Installing python 3.10 on a brand new
        machine - No module named 'pip'

        Ok, got my brand new HP victus machine from newish employer
        now - not a bad machine at all, but, while I specifically
        requested windows 10 pro
        64 bit, just in case, besides the 16Gb RAM and a 1TB SSD
        drive, they did install windows 11 home 64 bit on it - in
        case relevant.

        Anyway, am now trying to finish off configuring the machine
        for work, and, this includes installing all my general
        day-to-day software, which includes installing python 3.10 64
        bit, etc., but, while have tried installing it under both
        Program Files, for all users, or under the user's
        applications folder/path, I am getting more or less the same
        error message mentioned in subject line when I try activating
        a new virtual environment under python from the command line?

        So, first question is, would you recommend installing for all
        users, or on a per-user basis?

        Secondly, thoughts/ideas on what could cause this issue, and
        how to try
        sort it out, etc.?

        Thanks

        Jacob Kruger
        +2782 413 4791
        "Resistance is futile...but, acceptance is versatile..."

        ** To leave the list, click on the immediately-following link:-
        **
        [mailto:program-l-request@xxxxxxxxxxxxx?subject=unsubscribe
        <mailto:program-l-request@xxxxxxxxxxxxx?subject=unsubscribe>]
        ** If this link doesn't work then send a message to:
        ** program-l-request@xxxxxxxxxxxxx
        ** and in the Subject line type
        ** unsubscribe
        ** For other list commands such as vacation mode, click on the
        ** immediately-following link:-
        ** [mailto:program-l-request@xxxxxxxxxxxxx?subject=faq
        <mailto:program-l-request@xxxxxxxxxxxxx?subject=faq>]
        ** or send a message, to
        ** program-l-request@xxxxxxxxxxxxx with the Subject:- faq

        ** To leave the list, click on the immediately-following link:-
        **
        [mailto:program-l-request@xxxxxxxxxxxxx?subject=unsubscribe
        <mailto:program-l-request@xxxxxxxxxxxxx?subject=unsubscribe>]
        ** If this link doesn't work then send a message to:
        ** program-l-request@xxxxxxxxxxxxx
        ** and in the Subject line type
        ** unsubscribe
        ** For other list commands such as vacation mode, click on the
        ** immediately-following link:-
        ** [mailto:program-l-request@xxxxxxxxxxxxx?subject=faq
        <mailto:program-l-request@xxxxxxxxxxxxx?subject=faq>]
        ** or send a message, to
        ** program-l-request@xxxxxxxxxxxxx with the Subject:- faq

Other related posts: