-
Notifications
You must be signed in to change notification settings - Fork 71
Namespace error #19
Comments
I managed to solve this part:
by renaming the top section in my config file ;) |
Sorry about that! I made a bunch of sweeping name changes last night, and didn't think about the config section header name changing. Glad you got it sorted. |
I still have the top issue referring to namespace unfortunately, now I get logged into the site and it searches for the first item to process and the it exits with pretty much the same error as above. |
Can you post the stack trace as it is now? |
Apologies, it would have been useful if I had commented with that before!
Edit: Also just to rule it out I created a Debian container with all the dependancies and I get the same error;
I wanted to ensure that it wasn't something strange with using Alpine linux which it appears not to be the case. Edit 2: back using alpine if I pull the previous commit before the name changes it's working so must be something with the name change mate, I'll continue testing and if I fix it I'll submit a PR. |
Solved it, I deleted my cache file and it's on it's merry way! cheers guys! |
Phew, I'm glad I didn't break anything serious. Interesting, though - does your docker image have a default cache file it uses? I'd assume that it's generated the first time you run the script. |
I mount the cache file from the host to inside the container, same for config :) once I've finished my testing and I'm happy I'll up the code to my GitHub and I'll put a PR in here for the readme of how to use the image with docker. |
Hi,
I'm attempting to create a docker image for this script using a small alpine linux base. I've had it running fine on Friday night after solving this namespace issue but for the life of me I cannot remember what I did. The error I'm getting is
I've done
pip install ns
andpip install namespace
. I'm running the setup viapython setup.py install
I'm sure it's something simple but I can't work it out myself!
Thanks,
b3vis
The text was updated successfully, but these errors were encountered: