Skip to content
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

Closed
mantaraya36 opened this issue Apr 12, 2016 · 12 comments
Closed

Python module installers use 2.7 hardcoded path #631

mantaraya36 opened this issue Apr 12, 2016 · 12 comments

Comments

@mantaraya36
Copy link
Contributor

Although cmake finds python 3.4 and links to it, the python csound module is installed in ~/.local/lib/python2.7

@nogothenogo
Copy link

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.

@fggp
Copy link
Contributor

fggp commented Apr 14, 2016

Csound is built with Python 2.7 and so the PYTHONPATH used in the install
is for Python2.7. If you put a copy of ctcsound.py in the site-packages
directory of Python 3.x, it should work. ctcsound can be imported in Python
2.7 and in Python 3.x as well, provided it's in their PYTHONPATH.

2016-04-14 23:24 GMT+02:00 nogothenogo notifications@github.com:

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.


You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
#631 (comment)

@mantaraya36
Copy link
Contributor Author

Yes, but I think we are referring to the csnd6 module. Since it depends on
specific version of python, then the installation is performed incorrectly.
My guess is that the path for python 2.7 is hardcoded instead of using the
path detected by cmake for building the module.

On Thu, Apr 14, 2016 at 2:46 PM, fggp notifications@github.com wrote:

Csound is built with Python 2.7 and so the PYTHONPATH used in the install
is for Python2.7. If you put a copy of ctcsound.py in the site-packages
directory of Python 3.x, it should work. ctcsound can be imported in Python
2.7 and in Python 3.x as well, provided it's in their PYTHONPATH.

2016-04-14 23:24 GMT+02:00 nogothenogo notifications@github.com:

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.


You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
#631 (comment)


You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
#631 (comment)

@kunstmusik kunstmusik added this to the 6.08 milestone Aug 24, 2016
@kunstmusik
Copy link
Member

(I'm not sure how to resolve this, but I think it should be resolved for 6.08 and have assigned the milestone accordingly.)

@kunstmusik
Copy link
Member

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

@kunstmusik kunstmusik removed this from the 6.08 milestone Oct 6, 2016
@fsateler
Copy link
Contributor

fsateler commented Oct 6, 2016

Maybe instead of invoking python directly, we could use FindPythonInterp cmake module and use ${PYTHON_EXECUTABLE}.

@dvzrv
Copy link
Contributor

dvzrv commented Apr 13, 2019

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!

@jpffitch
Copy link
Contributor

Is this issue now redundant? I thought we had moved to python3.

@fggp
Copy link
Contributor

fggp commented Dec 16, 2019 via email

@dvzrv
Copy link
Contributor

dvzrv commented Dec 25, 2019

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.

@fggp
Copy link
Contributor

fggp commented Dec 26, 2019 via email

@kunstmusik
Copy link
Member

Closing as stale, seems we've moved on to Python3

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

7 participants