-
-
Notifications
You must be signed in to change notification settings - Fork 136
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
Build for Python 3 #356
Comments
Mopidy 3.0.0a3 is now on PyPI, this pre-release removes support for Python 2.7 and runs under Python 3.7 and 3.8. See mopidy/mopidy#779 (comment) |
We're targeting a Mopidy 3 release Dec 21. Do you think Iris will have a working pre-release out by then? |
Unfortunately that's not looking likely. This is my only (and first!) Python project so it will take me a bit of time to work through the upgrade. I have started but progress is slow at this stage. |
This porting checklist saves a lot of time, especially when you don't have much experience with Python 3 (like me). |
Would it be helpful if I ran through the above checklist (as much as I can) and submitted a PR? |
@kingosticks I am grateful for any assistance, so yes please :-) |
I'm trying to install Mopidy 3.0.0-b1 but it's not available on
|
I just installed it into a fresh python3.7 virtualenv using You can also install from source by following the instructions at https://docs.mopidy.com/en/develop/devenv/ |
Hmmm seems peculiar. Ideally I'd run this in Docker but that can wait until I get the basics sorted.
|
Mopidy 3 requires Python 3.7 |
Mopidy should work on
|
Yes it should. Since there's no .deb out yet, the idea is to follow https://docs.mopidy.com/en/latest/installation/pypi/. However, if you are on Ubuntu 18.04, or something else that only ships with Python 3.6 as default, then it's a little more complicated; each Ubuntu release has a But if you are working with docker you could just use our image? |
I suppose I have to wait for Iris migration to pyhton3 before installing mopidy 3, correct? |
Yes.
…On Wed, 25 Dec 2019, 11:02 Fabio Marzocca, ***@***.***> wrote:
I suppose I have to wait for Iris migration to pyhton3 before installing
mopidy 3, correct?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#356?email_source=notifications&email_token=AAHEHKDQ2D7A7KEHAVCLF6DQ2M4UBA5CNFSM4GTT2UNKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEHUIGMA#issuecomment-568886064>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAHEHKBXWTLQWPAV6VTIPCLQ2M4UBANCNFSM4GTT2UNA>
.
|
Hello. My current notes for Iris on mopidy 3 are: This is usefulhttps://mopidy.com/blog/2019/12/27/mopidy-3-faq/
|
@MarcinWieczorek that's awesome, thanks heaps! Is that based off the current state of the |
Yes indeed
|
Keen for your thoughts on 564839c. Essentially |
I have seen there is a new release. Is this issue fixed? |
The changelog says
So I guess that must indeed be solved. |
thanks. |
I'd also welcome a release on PyPI so we can update our distribution package to the latest Iris version. @jaedb One thing I noticed in the tarball from Github is that setup.cfg has |
Thank you for getting this updated so quickly @jaedb - I can't imagine a Mopidy without the Iris front-end. Eagerly awaiting a pip release! |
I'm glad to see the update. @jaedb, has anything changed about the dependendies? I'm about to update the package in AUR. |
Nice work, @jaedb! It's working well for me. Also eagerly awaiting a pip release :-) |
Wouldn’t mind seeing some idiot proof instructions for how to install this on a raspberry pi using docker. I have zero experience with docker but like the idea of it from a security standpoint. |
pip install mopidy-whatever in dockerfile |
Ahh so the docker container is mopidy. Now I see |
That doesn’t seem practical on a raspberry pi |
It's as practical as it gets. You can have mopidy separated from python packages which is good (I think I'm going to switch to that soon). It's similar to just using a virtualenv, but with docker. |
Iris does have a Docker container and will be uploaded to Docker Hub when the final stages of release are finished. |
@kingosticks do you have any advice on the |
Is there a somewhat working test version I could try at the moment? |
You can ignore |
But isn't that already specified at https://github.com/jaedb/Iris/blob/master/tox.ini#L28 ? Is this because it should be |
@BrainStone yes, you should be able install from source using the
|
@jaedb would something like Edit: Yes it does. |
When using the following packages:
Working:
Not working
After searching with Spotify i get this error:
Even with tornado-4.5.3:
|
@brammittendorff I had that problem too, but then I installed https://github.com/jaedb/Iris/archive/3.44.0.zip instead of develop.zip and it worked. |
@jjok You are right that one works, even with Spotify thanks alot. So the working setup is:
|
This has just been released to pip and the image to Docker hub so I shall close this issue. Please open a new issue for any problems you may encounter. |
I have found only v.3.43.0 in pip3. |
sudo python3 -m pip install Mopidy-Iris [should work for you] |
Upgrade all python code to 3, with backwards compatibility to 2.7 (which is what Mopidy currently supports).
UPDATE: The Iris Python3 version will not be backwards compatible to Python 2.7 (as is the case with Mopidy 3).
The text was updated successfully, but these errors were encountered: