I get some python errors when running ./bin/gmg, but the commands do process correctly.
$ ./bin/gmg adduser --username example --email example@example.edu
/srv/mediagoblin.example.org/mediagoblin/lib/python3.9/site-packages/PyLD-1.0.5-py3.9.egg/pyld/jsonld.py:577: SyntaxWarning: "is" with a literal. Did you mean "=="?
/srv/mediagoblin.example.org/mediagoblin/lib/python3.9/site-packages/PyLD-1.0.5-py3.9.egg/pyld/jsonld.py:577: SyntaxWarning: "is" with a literal. Did you mean "=="?
Password:
User created (and email marked as verified).
Which version of Python are you running and which branch of Mediagoblin are you on?
A new rc has been put out recently [0], that fixes this sort of compat issues up to, and including, Python 3.9.
#[0] https://git.sr.ht/~mediagoblin/mediagoblin/refs/v0.12.1rc1
Olivier Mehani shtrom@ssji.net Sent from my mobile, please excuse my brevity.
I'm using v0.12.1rc1 branch and Python 3.9.2 on Debian 11. Is there anything I can run here to get better data for this issue?
Unfortunately not, but a diag tool in gmg might be a good idea for future work.
#I assume you're running in a virtualenv. Did you rebuild after pulling?
Olivier Mehani shtrom@ssji.net Sent from my mobile, please excuse my brevity.
This warning is originating from the PyLD library and not MediaGoblin itself. These sorts of warnings are relevant to developers, but not to users of MediaGoblin, so I think we probably should disable them. Does that sound reasonable to you Olivier?
#Yup. Can we reenable them easily when developing?
Olivier Mehani shtrom@ssji.net Sent from my mobile, please excuse my brevity.
Olivier: I'm just happy I was able to get anything to work as I ran into issue after issue to finally get this up and running today. I followed the instructions here, https://docs.mediagoblin.org/en/master/siteadmin/deploying.html, which mostly worked. I'd like to contribute documentation but I need to learn how to do that on here or Savannah.
This would be great!
Here would be best (we need to clarify that Savannah is not use for source tracking anymore).
You'll find the source of the documentation in the docs/ subdirectory of the repo, and you should be able to do a
make docsto build it, so you can check that the output is as you intended.-- Olivier Mehani shtrom@ssji.net Sent from my mobile, please excuse my brevity.
I've just done some testing (Python 3.10 on GNU Guix) and am not seeing this warning. Is anyone else able to see it?