#django

anyone familiar with django.core.files.storage?

toothe: Just ask the question

I am migrating a 1.5 project to 1.6 (then 1.9). imports used `import myapp` and settings had `myapp` in requirements. For 1.6 the project name needed to be appened. `myproject.myapp`. Can PYTHONPATH be set the app like in 1.5 or is that a bad pratice. (relative imports)

coulix_tap: the project name was never needed

The djangoproject startproject does use the projectname in the default settings and urs. Is that optional?

project name is a "relative" term, all django needs is an importable path

that should not be done or needed!

myapp is usually on the same level as myproject, not below

I remeber this move too, maybe not in 1.6 though.

there was never ever a need for the project name before the appname

there have been some double import issues, but that was 1.4 or so

Alright I moved back manage.py to the project folder. That did the trick.

is there an IPv4/v6 validation?

validating function?

I'm looking to validate that, say, a certain CIDR block is valid.

toothe: Haven't used it, but https://python-iptools.readthedocs.org/en/latest/ looks applicable.

awesome!

What's the simplest way to form a queryset for `foreign_key = # OR foreign_key IS NULL`?

hi, i'm seeing a really weird phenomenon in my django app where a page load to /user/123 is also firing a request to /user in the background. does anyone know waht could be causing this?

Wait, sorry. Conflating two problems. What I meant to ask is how do I do that for a many-to-many relation.

can anyone help me get anything out of my django server that isnt a 500 error?

i've even tried purposely causing a traceback in the handler for /user. then, when i navigate to /user/123 (which is handled by a different handler), the page loads fine, but in my server logs i see a request going to /user immediately afterwards that triggers the traceback

i have posted my views and url/py here http://pastebin.com/5gc930kC urls seems to call views just fine, and views is being called, but the Index function in views is not responding at all

frostythesnowman: Browser prefetching?

frostythesnowman: Does the same thing happen if you use curl, for example?

Actually, does Django's ORM have a way to enforce an equivalent to null=False on ManyToManyField?

BodaciousBrian: Looks fine, assuming the URL you're viewing is the root, e.g http://localhost:8000/

How are you running Django?

Yes it is... Im running it via the manage.py runserver command

"[27/Feb/2016 17:32:12] "GET /test HTTP/1.1" 500 27" is all i get out of it

deitarion: There isn't an equivalent in SQL, so no. But validation for a form will trigger, that is if you have a ManyToManyField that isn't blank=True, a form won't validate if you don't pick an option.

it seems nothing i change can get a different result

'/test' wouldn't call index.

Only '/'

Oh sorry, i know.. i have just implemented a New test view. but the / is the same result

always error 500 27

So, you are getting a 500 there, what's the traceback?

im not sure how to get a traceback

If DEBUG is True, it'll show up in your browser.

DEBUG = os.environ.get('DEBUG') == 'True'

on the website itself all i get is "Server Error (500)"

So you need to set that environment variable.

haha, got it....

i thought that was setting it =) i have the traceback now

well, i might be able to solve this now that the debug is fixed

return render(request, "index.html", {'working'})

ive tried that line about every way a view is returned that can be found online... In my templates directry i have an index.html that just says 'working' in the files

Well, {'working'} isn't a dictionary, it's a set.

yes i just want anything to be returned..... that isnt a 500 anyway

So make that a dictionary.

Since that's what's expected for the context argument to render..

And, maybe, run through the official tutorial again, or if you haven't yet.