#python error when installing requirements

1 messages ยท Page 1 of 1 (latest)

merry ether
#

Hi guys, When I run python -m pip install -r requirements.txt I get the following error...

Command "/home/seedit4me/PMM/Plex-Meta-Manager/pmm-venv/bin/python -u -c "import setuptools, tokenize;__file__='/tmp/pip-build-ssd21iu0/ruamel.yaml.clib/setup.py';f=getattr(tokenize, 'open', open)(__file__);code=f.read().replace('\r\n', '\n');f.close();exec(compile(code, __file__, 'exec'))" install --record /tmp/pip-266314g3-record/install-record.txt --single-version-externally-managed --compile --install-headers /home/seedit4me/PMM/Plex-Meta-Manager/pmm-venv/include/site/python3.7/ruamel.yaml.clib" failed with error code 1 in /tmp/pip-build-ssd21iu0/ruamel.yaml.clib/

thick starBOT
#

Please complete #938455615741775902 and someone from the community or one of our <@&938443185347244033> members will respond when they're available.

Including the meta.log from the beginning is a huge help use !logs for more information.

kindred wing
#

python error when installing requirements

shy eagle
#

Just checking based on the name - are you installing PMM on a seedbox?

#

And if so, do you have root permissions?

merry ether
#

yes and yes ๐Ÿ™‚

#

Shall I re-run the command with sudo?

shy eagle
#

what happens if you just use pip install -r requirements.txt

merry ether
#

same error

shy eagle
#

google suggests you may need to upgrade pip

merry ether
#

is that a simple apt upgrade pip?

shy eagle
#

do pip --version

#

what's the output?

daring viper
#

You should be doing this in a virtual environment, not using sudo. nvm; I see you are, but sudo shouldn't be required.

merry ether
shy eagle
#

Isn't pip on version 22 or something?

merry ether
#

lmao

shy eagle
merry ether
#

yikes

shy eagle
#

๐Ÿคฃ

#

try upgrading pip

merry ether
#

I'll have to check with my seedbox guys just incase it brakes any apps (shouldn't do tbh)

daring viper
#

What version of python is this?

shy eagle
#

you can do it within the venv I think?

shy eagle
merry ether
#

Ah so whatever I install in the env doesn't effect anything outside of it?

daring viper
#

Ah, sure.

#

That's the idea.

shy eagle
merry ether
#

Nice. Let me try upgrading then ๐Ÿคž

shy eagle
#

python -m pip install --upgrade pip

merry ether
#

thank you

shy eagle
#

np

merry ether
#

ok that worked so lets try it now

shy eagle
#

it's at least 5 years old rofl

merry ether
#

hahahaha

#

Jesus

#

No errors ๐Ÿค

shy eagle
#

๐Ÿ˜„

merry ether
#

I shall carry on with the guide, thank you guys

shy eagle
#

Chad may be able to answer this, but you may need to upgrade each time you re-activate the venv?

#

I can't remember if it's deleted once stopped

daring viper
#

pip 9.0.1 was released on Nov 6, 2016 and Python 3.7 on June 27, 2018, at which point pip 18 was current, so not sure how this state arose.

#

You shouldn't need to upgrade again.

shy eagle
#

you may want to inform your seedbox owner in case this is a wider issue lol

daring viper
#

Once something is installed in the venv it's installed in the venv.

#

pip did go straight from version 10 to 18, however.

shy eagle
#

ah yes, logic!

#

Can't wait for the iPhone 23 next year

shy eagle
#

@merry ether are you happy for us to close this thread?

merry ether
#

hahaha yes thanks guys

merry ether
#

@shy eagle Hi mate, just before you close it, I got up to the part where you test the config and it's saying to run Docker... This is meant to be an installation without Docker right?

shy eagle
#

I think that's an error in the docs that has been fixed in the nightly and develop version of the docs but hasn't been pushed forwards to latest yet

merry ether
#

Ah, what should I type to test it?

shy eagle
#

follow this one ๐Ÿ™‚

merry ether
#

thanks ๐Ÿ˜„

#

So at the end of the guide, it says to type deactivate and so if I want to rerun the script, I just activate it again?

shy eagle
#

yes

daring viper
#

You can run it without the "activate" step by calling the python binary inside the venv folder:

cd /path/to/plex-meta-manager
pmm-venv/bin/python plex_meta_manager.py [OPTIONS]
merry ether
#

is there a downside to leaving it running?

#

So I can set up a cronjob to auto run every x hours?

merry ether
#

ah excellent

daring viper
#

If you leave PMM running it will wake up once a day and process metadata. You can change the time[s] that happens with runtime options.

If you want it to run then quit at 5:37 PM on Wednesday, you can schedule that with cron or whatever.

merry ether
#

I'll do it at midnight each day ๐Ÿ™‚

shy eagle
#

I think the latter approach would be recommended so that PMM isn't continuously using resources?

daring viper
#

remember to change that path.

merry ether
#

oops. Sorry, which latter approach? Running it as a service?

daring viper
#

the cron approach of scheduling the run-and-quit will not use resources all the time running in the background.

merry ether
#

so just add --quit to the end? cd /path/to/plex-meta-manager && pmm-venv/bin/python plex_meta_manager.py --config config/config.yml --run && --quit

daring viper
#

No. --run will run immediately and quit once finished.

merry ether
#

ahhh ok thank you

daring viper
#

Wait until 5AM to wake up and Do The Things, then go back to sleep:

python plex_meta_manager.py --config config/config.yml

Do The Things right this second, then quit:

python plex_meta_manager.py --config config/config.yml --run
merry ether
#

that's cool. I'm gonna go down such a rabbit hole with all the possible configurations ๐Ÿ˜›

merry ether
#

may aswell carry this thread on

shy eagle
#

is this your unmanaged issue?

#

collect1ons

merry ether
#

yeah

shy eagle
#

see the issue? ๐Ÿ˜„

#

I'm praying you see the issue

merry ether
#

omg

shy eagle
#

LOL

merry ether
#

Hahahahahahaha

#

Who the feck typed that before and I've copied it lmao

shy eagle
#

idk how you managed that

merry ether
#

ah brill all gone now ๐Ÿ˜„