New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Python module installers use 2.7 hardcoded path #631
Comments
i have similar problems on windows i have python 3.x and csoundqt asks for python2.7, i had to rename the py.dll in the csound_64/plugin64 folder. now the popup is gone and i guess the functionality too. |
Csound is built with Python 2.7 and so the PYTHONPATH used in the install 2016-04-14 23:24 GMT+02:00 nogothenogo notifications@github.com:
|
Yes, but I think we are referring to the csnd6 module. Since it depends on On Thu, Apr 14, 2016 at 2:46 PM, fggp notifications@github.com wrote:
|
(I'm not sure how to resolve this, but I think it should be resolved for 6.08 and have assigned the milestone accordingly.) |
removing from 6.08 for interim, we should consider committing to ctcsound.py for cs7, if so, maybe this issue is moot for the time being |
Maybe instead of invoking python directly, we could use FindPythonInterp cmake module and use |
Given the fact, that python2 will be EOL in less than 9 months, it would be great, if this could be added to a very close milestone again! |
Is this issue now redundant? I thought we had moved to python3. |
I created a plugins repository (https://github.com/csound/plugins) to test
the possibility of building plugins separately. Among these plugins,
there's a port of the py opcodes to Python 3. The build have only been
tested on linux, because I don't have a Windows or an OsX machine. If the
py opcodes plugin builds on Windows and OsX as well, it can be integrated
in Csound right now and then, we wouldn't need anymore a hard coded path to
Python 2.7. Nota bene: this would mean that we don't build anymore the
Python wrapper for Python 2.7. This is a backward compatibility break; so
maybe should we wait for Csound 7 before doing this?
François
Le dim. 15 déc. 2019 à 22:33, John ffitch <notifications@github.com> a
écrit :
… Is this issue now redundant? I thought we had moved to python3.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#631?email_source=notifications&email_token=ABNOAKL52OCY3SLW4R4VQIDQY2PDHA5CNFSM4CAWDGQ2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEG5CX7Q#issuecomment-565849086>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABNOAKMRL7MHEM42ULAVZETQY2PDHANCNFSM4CAWDGQQ>
.
|
Do you have a roadmap for the release of csound 7? |
No definitive roadmap for now. However, you can build some plugins cloning
this repo: https://github.com/csound/plugins. The py (libpy.so) opcodes in
this repo are built for Python3. This way, you can already get rid of
Python2.7 for your package on ArchLinux.
François
Le mer. 25 déc. 2019 à 12:08, David Runge <notifications@github.com> a
écrit :
… Do you have a roadmap for the release of csound 7?
It would of course be great, to have a python3 ready plugin available also
for the current release (i.e. >= 6.13.0), as I will now remove the plugin
from the package on Arch Linux for the time being to allow the distribution
to remove python2 from the repos in the near future.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#631?email_source=notifications&email_token=ABNOAKN6FKKB4W7RXNPYTT3Q2M5JLA5CNFSM4CAWDGQ2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEHUIMLA#issuecomment-568886828>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABNOAKMT7JRCW5JXWVBDUSTQ2M5JLANCNFSM4CAWDGQQ>
.
|
Closing as stale, seems we've moved on to Python3 |
Although cmake finds python 3.4 and links to it, the python csound module is installed in ~/.local/lib/python2.7
The text was updated successfully, but these errors were encountered: