# Upgrade installation issue

**URL:** <https://support.prodi.gy/t/upgrade-installation-issue/6752>\
**Category:** Uncategorized\
**Created:** [August 23, 2023, 4:19pm UTC](https://support.prodi.gy/t/upgrade-installation-issue/6752 "2023-08-23T16:19:45Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![andyhegedus](https://sea2.discourse-cdn.com/flex020/user_avatar/support.prodi.gy/andyhegedus/32/3625_2.png) [@andyhegedus](https://support.prodi.gy/u/andyhegedus)\
**Post date:** [August 23, 2023, 4:19pm UTC](https://support.prodi.gy/t/upgrade-installation-issue/6752/1 "2023-08-23T16:19:45Z")

</div>

Hi,  
I cannot install the upgrade with the command

```python
pip install prodigy -f https://XXXX-XXXX-XXXX-XXXX@download.prodi.gy

```

I have put in my license key for the x's.

After running command I do prodigy stats  
Version 1.12.5  
Location /Users/andreashegedus/opt/anaconda3/lib/python3.9/site-packages/prodigy  
Prodigy Home /Users/andreashegedus/.prodigy  
Platform macOS-10.16-x86\_64-i386-64bit  
Python Version 3.9.13  
Spacy Version 3.6.1  
Database Name SQLite  
Database Id sqlite

Interestingly I am running MacOs 13.4.1 not 10.16

 ![image](https://us1.discourse-cdn.com/flex020/uploads/prodigy/original/2X/a/a4a6937190153a85a514871a4548de0e6128a2d9.png)

I think this is related to a previous issue where I hade to rename the whl file  
as an example to install .12.5  
I needed to rename  
prodigy-1.12.5-cp39-cp39-macosx\_11\_0\_x86\_64.whl  
to  
prodigy-1.12.5-cp39-cp39-macosx\_10\_15\_x86\_64.whl

There are previous topics from me where we worked on this work around.  
How can I install the upgrade?  
Andy

---

<div class="post-metadata">

**Author:** ![ryanwesslen](https://sea2.discourse-cdn.com/flex020/user_avatar/support.prodi.gy/ryanwesslen/32/2969_2.png) [@ryanwesslen](https://support.prodi.gy/u/ryanwesslen)\
**Post date:** [August 23, 2023, 4:34pm UTC](https://support.prodi.gy/t/upgrade-installation-issue/6752/2 "2023-08-23T16:34:13Z")

</div>

hi @andyhegedus,

> [@andyhegedus](#):
>
> I cannot install the upgrade with the command
> 
> ```python
> pip install prodigy -f https://XXXX-XXXX-XXXX-XXXX@download.prodi.gy
> 
> ```

Can you try to add `--upgrade`?

```command
pip install --upgrade prodigy -f https://XXXX-XXXX-XXXX-XXXX@download.prodi.gy

```

> [@andyhegedus](#):
>
> There are previous topics from me where we worked on this work around.

Yes, here's the link from our previous thread where the problem was Intel Mac.

> [@Installing update 1.11.110 on Mac](https://support.prodi.gy/t/installing-update-1-11-110-on-mac/6362/34):
>
> Hi Ryan, I think it worked and I will recount what I did. I received this whl from you prodigy-1.11.11-cp39-cp39-macosx\_11\_0\_x86\_64.whl I renamed it changing 11\_0 to 10\_15 prodigy-1.11.11-cp39-cp39-macosx\_10\_15\_x86\_64.whl Did a pip install with that renamed file. pip install --upgrade prodigy -f /Users/andreashegedus/Desktop/prodigy-1.11.11-cp39-cp39-macosx\_10\_15\_x86\_64.whl Checked version with prodigy stats Version 1.11.11 Location /Users/andreashegedus/opt…

Alternatively, instead of running `pip install` (which will automatically choose the wheel file for you), you can now choose and download a specific wheel file by putting `https://XXXX-XXXX-XXXX-XXXX@download.prodi.gy` into a browser, and then you'll see all of the versions of Prodigy you are eligible to get.

 ![image](https://us1.discourse-cdn.com/flex020/uploads/prodigy/original/2X/2/2fcc40040f3a4209b9f9254fcd777f805997d549.jpeg)

Then can you try to do the same steps we previously went thru in renaming the wheel file above?

---

<div class="post-metadata">

**Author:** ![andyhegedus](https://sea2.discourse-cdn.com/flex020/user_avatar/support.prodi.gy/andyhegedus/32/3625_2.png) [@andyhegedus](https://support.prodi.gy/u/andyhegedus)\
**Post date:** [August 23, 2023, 4:53pm UTC](https://support.prodi.gy/t/upgrade-installation-issue/6752/3 "2023-08-23T16:53:28Z")

</div>

Hi,

I tried adding --upgrade  
Same result still at 1.12.5  
I tried going directly to the website as you suggested. I am greeted with a login panel with user id and password. What should I use?  
Andy

---

<div class="post-metadata">

**Author:** ![ryanwesslen](https://sea2.discourse-cdn.com/flex020/user_avatar/support.prodi.gy/ryanwesslen/32/2969_2.png) [@ryanwesslen](https://support.prodi.gy/u/ryanwesslen)\
**Post date:** [August 23, 2023, 4:56pm UTC](https://support.prodi.gy/t/upgrade-installation-issue/6752/4 "2023-08-23T16:56:31Z")

</div>

> [@andyhegedus](#):
>
> I tried going directly to the website as you suggested. I am greeted with a login panel with user id and password. What should I use?

You can put your license key in `user id`.

Hopefully you shouldn't need to put in the user id though if you type into the browser: `https://xxxx-xxxx-xxxx-xxxx@download.prodi.gy`, not `https://download.prodi.gy`. But worst case using the license key in `user id` should suffice. (FYI my screen shot showed `https://download.prodi.gy` because after it takes your license key, it'll only show `https://download.prodi.gy`).

---

<div class="post-metadata">

**Author:** ![andyhegedus](https://sea2.discourse-cdn.com/flex020/user_avatar/support.prodi.gy/andyhegedus/32/3625_2.png) [@andyhegedus](https://support.prodi.gy/u/andyhegedus)\
**Post date:** [August 23, 2023, 5:08pm UTC](https://support.prodi.gy/t/upgrade-installation-issue/6752/5 "2023-08-23T17:08:35Z")

</div>

Hi,

I used license key for both fields and that worked. Download 1.13.1 appropriate whl file, renamed as before and it installed.  
Andy

---

<div class="post-metadata">

**Author:** ![ryanwesslen](https://sea2.discourse-cdn.com/flex020/user_avatar/support.prodi.gy/ryanwesslen/32/2969_2.png) [@ryanwesslen](https://support.prodi.gy/u/ryanwesslen)\
**Post date:** [August 23, 2023, 5:57pm UTC](https://support.prodi.gy/t/upgrade-installation-issue/6752/6 "2023-08-23T17:57:45Z")

</div>

Excellent - I'm so glad it worked out 😃

Enjoy trying out `v1.13`! By the way, we're planning more updates in the upcoming weeks so hopefully this workflow will work again for any future updates!
