no package installation possible

[Feedback1000]

Hey.

I tried to install sympy.

Previously I installed IronPython 3.4.

The ipy -m pip install sympy==1.4 command didn't work because I received the following error message:

Der Befehl "ipy" ist entweder falsch geschrieben oder
konnte nicht gefunden werden..

Even though the path exists:

Can you help?

Regards,
Fabian

[BCSharp]

ipy.exe on your system is installed in directory C:\Programme\IronPython 3.4 but you try to execute it from directory C:\Windows\System32, therefore the executable is not found. Change the current dirtectory to the IronPython isnstallation directory and run from there. E.g.:

C:\Windows\System32>cd "\Programme\IronPython 3.4"
C:\Programme\IronPython 3.4>ipy -m pip install sympy==1.4

To be able to run ipy from anywhere, add the IronPython installation directory to the PATH environment variable. Adding the subdirtectory Scripts may be useful too because it's where isympy.exe is going to be installed.

[Feedback1000]

Hey Pavel. Thank you for your help. But it doesn’t matter if I want to install sympy or f.e. vectors I get the same error: Can you help? Regards Fabian Von: Pavel Koneski ***@***.***> Gesendet: Sonntag, 12. November 2023 20:24 An: IronLanguages/ironpython3 ***@***.***> Cc: Feedback1000 ***@***.***>; Author ***@***.***> Betreff: Re: [IronLanguages/ironpython3] no package installation possible (Discussion #1752) ipy.exe on your system is installed in directory C:\Programme\IronPython 3.4 but you try to execute it from directory C:\Windows\System32, therefore the executable is not found. Change the current dirtectory to the IronPython isnstallation directory and run from there. E.g.: C:\Windows\System32>cd "\Programme\IronPython 3.4" C:\Programme\IronPython 3.4>ipy -m pip install sympy==1.4 To be able to run ipy from anywhere, add the IronPython installation directory to the PATH environment variable. Adding the subdirtectory Scripts may be useful too because it's there where isympy.exe is going to be installed. — Reply to this email directly, view it on GitHub <#1752 (comment)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/BDLYF7Q3KFJYWHNBUKK2RPLYEEO6RAVCNFSM6AAAAAA7IGX5EWVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM3TKNBXGU2DG> . You are receiving this because you authored the thread. <https://github.com/notifications/beacon/BDLYF7QZERAZ3M3MV2LM743YEEO6RA5CNFSM6AAAAAA7IGX5EWWGG33NNVSW45C7OR4XAZNRIRUXGY3VONZWS33OINXW23LFNZ2KUY3PNVWWK3TUL5UWJTQAOMVJO.gif> Message ID: ***@***.*** ***@***.***> >

[slozier]

If ipy is not on your path, depending on your shell, you may have to do .\ipy -m pip install sympy==1.4.

[Feedback1000]

Not yet helpful: Von: slozier ***@***.***> Gesendet: Mittwoch, 13. Dezember 2023 16:49 An: IronLanguages/ironpython3 ***@***.***> Cc: Feedback1000 ***@***.***>; Author ***@***.***> Betreff: Re: [IronLanguages/ironpython3] no package installation possible (Discussion #1752) If ipy is not on your path, depending on your shell, you may have to do .\ipy -m pip install sympy==1.4. — Reply to this email directly, view it on GitHub <#1752 (comment)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/BDLYF7VETIRPMOWVXLNFPFDYJHE7ZAVCNFSM6AAAAAA7IGX5EWVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM3TQNBUGA4TS> . You are receiving this because you authored the thread. <https://github.com/notifications/beacon/BDLYF7VV2RL5DNP3I2OXYW3YJHE7ZA5CNFSM6AAAAAA7IGX5EWWGG33NNVSW45C7OR4XAZNRIRUXGY3VONZWS33OINXW23LFNZ2KUY3PNVWWK3TUL5UWJTQAO6YQG.gif> Message ID: ***@***.*** ***@***.***> >

[BCSharp]

@Feedback1000 maybe you do not realize, but your recent posts arrive without the error messages you are getting. Without the error messages it is hard to guess what is going wrong on your system.

One thought comes to mind: since the default installation folder used by the MSI installer (C:\Programme\IronPython 3.4 in your case) is a read-only location for a regular user, to update it with new packages you have to run ipy -m pip install sympy==1.4 from the elevated (administrator) command prompt, rather than the regular shell prompt. Have you tried that?