-
-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
NoneType object is not callable #373
Comments
Yup, that looks like a bug and not your fault. I'll need to take a look further to see what is up. |
Sorry, should have included a few other things: Python is 2.7.3 And pip freeze gives: argh==0.26.1 This is all running on a Raspberry Pi B+, running Raspbian Debian 7.8 (wheezy) |
Thanks - travelling at the moment but should get to this in a few days. |
I think something funky is happening when mkdocs tries to split the host and port at the colon(serve.py, Line 107). With some experimentation I got this:
Unfortunately, I need mkdocs to serve out to a IP, and not the localhost, so looks like I'll be stuck building and serving for a while... Because I have no idea why |
How did you resolve your previous error? |
I can't see any way that dev_addr would become a boolean, have you changed the code at all? Can I see your latest config? |
Seems that using mkvirtualenv meant that mkdocs looked for the "face" theme directory inside mkdocs own theme folder:
So I tried to isolate if that was the main error, by dropping the theme lines from my config, and specifying dev_addr from the commandline instead:
So, to run, I ran this command:
And instead got this traceback:
I believe |
I see, interesting. Thanks. This is an odd one, but I have an idea - will look into it. |
I'm not sure if this is my own stupidity, related to #283, or something I've ended up doing myself by accident.
I'm working on developing a mkdocs theme, and
mkdocs build
andmkdocs build --clean
both run without any issues.However, if I try and
mkdocs serve
then I get hit by an error.My
mkdocs.yml
file is simple, and I don't think it is the actual cause, but it might be in my own inept way:The text was updated successfully, but these errors were encountered: