Comments on: Dynamic names as first-level URL path objects in Django

By: Philip Gatt

Philip Gatt — Wed, 27 Apr 2011 05:14:02 +0000

Instead of checking for an error, check that the desired url is the catchall. In my app I have this and it’s working:

def clean_username(self):
username = self.cleaned_data['username'].lower()
try:
r = urlresolvers.resolve(‘/{0}/’.format(username))
except urlresolvers.Resolver404:
raise RuntimeError(“Username should match a url-check routes file”)
else:
if r.url_name != ‘room’:
raise forms.ValidationError(‘Username is unavailable’)
return username

By: Buckley

Buckley — Tue, 08 Dec 2009 15:36:27 +0000

What I’m trying to say is the exception will never be raised. Even if the user chooses a valid username, it will still match the ‘user’ pattern regardless of whether or not the username has been picked by someone else.

By: Elf Sternberg

Elf Sternberg — Tue, 08 Dec 2009 15:00:50 +0000

Yes, and that’s the point! If the resolve block doesn’t throw an exception, the resolution works, meaning you’ve chosen a name that conflicts with (a) a reserved URL for the application or (b) a username already in use by someone else. The user must pick something else.

Does that help?

By: Buckley

Buckley — Tue, 08 Dec 2009 14:27:11 +0000

I don’t understand how this would work. Won’t the resolve call in the try block return the user url pattern in the case where the registration is valid?