Great! I've tried logging stuff but it doesn't seem to work when uploading 
it to a webserver. When running on my localhost server there was a log 
about a depreciation, then when it was doing training, then when it has 
finished training. But I can't seem to see it in the webserver terminal :/

On Thursday, February 16, 2017 at 12:24:40 AM UTC+8, Shawn Milochik wrote:
>
> It's probably some difference between environments. If you know your code 
> works (it runs locally) and you're running the same versions of all your 
> dependencies (Python, Django, Openface, etc.), then it doesn't *seem* too 
> likely to be a major bug. It *could* be a bug -- not checking for and 
> handling an exceptional condition. For example, what if your code processes 
> each file in a directory -- but that directory is empty? It'll "work" 
> perfectly, and return nothing.
>
> Add some logging along the way -- see what files it sees, what directories 
> it's looking it, etc. If you're hitting any external resources (APIs, 
> databases, etc.) make sure that your credentials work from your server and 
> that the services are available.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/cb3b5747-08ad-4844-809c-c2ccba7c2e37%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to