#django

but i guess would have to go the validator route

has anyone used a user model with a non-integer id? did password resets work?

How much more 'by default' would it get? :)

:)

mattmcc: DateTimeField(greater_than=now())? :P

heh, that could work

ugh, this password thing is pissing me off, i can't even find it in the source

Well, you can always subclass the field and make your own FutureDateTimeField with the validator added by default.

hmm, cool

Has anyone had any experience (positive or negative) with Django-chartit?

Stavros, you using contrib.auth ?

k_89: yeah

with AbstractBaseUser, i removed the username

i hve no clue about best practices in django-land, but what's the opinion on rolling a simple user-roles system and ditching contrib.auth

using bcrypt for password hashing

and this is for an api, so won't need any admin

k_89: contrib.auth is just simpler

really, hmm

i should dig into it

this is what the User model looks like atm

that's pretty much the default user model

hmm, cool

so it looks like django just doesn't support non-integer id models: https://github.com/django/django/blob/master/dj...

are there any unexpected consequences if my urlconf has '^foo/?', include(foo.urls)? note the /? instead of the usual /

Stavros: That's specific to the default user model. Non-integer models work just fine.

mattmcc: well, they don't work with the admin

I use UUID models all over the place in the admin. They work fine.

oh i can override it, right

thanks

didn't notice that

mind pasting your password-changing code?

Oh, we still have just the default user. But replacing that one method should suffice.

how do install group_messaging? I cant find it :(

I won't have 1.5 in production for probably another 4-5 months.

mattmcc: oh, so you don't have a UUID-based user model, right

i misunderstood

what do you use for uuids, by the way?

Universal uniqueness? :)

It's a quasi-multi-tenant environment.

haha, no, i mean to generate them

just the uuid module?

Oh. There are a handful of UUIDField implementations floating around.

Ours I think started out as a copy of the one in django-extensions, with some tweaks for native Postgres support.

ah, i see, thanks

i generally use a textfield defaulting to the shortuuid module, is there any advantage to a dedicated uuidfield?

This is where SmileyChris chastises me for not using his version.

mattmcc: er, sorry to bother you about cloud hosting again, but have you used ec2?

i apparently signed up for an ec2 account a long time ago, so i think my free year has expired; does that mean i'll get billed just for using it, even if i stay within the micro tier limitations?

they seem purposefully vague about it in the documentation

Well, AWS docs tend to suck across the board.

indeed :x much of it reads like a sales pitch

i'm afraid that i'm running up a monster bill without any means of being able to tell

er, and on a more django-specific front, is there a nice way to write a management command that monitors the db for changes without having to be constantly polling it?

Stavros: Postgres' native data type validates and stores them more efficiently than a text field.

(right now, i do a query for pending jobs in some table, and process them one at a time if i find any; if i don't, i sleep for a little bit and then try the query again)

mattmcc: interesting

i'm using user-facing ones, so i prefer the uuids being as short/readable as possible, so i guess they're different use cases

Yeah.

For user-facing stuff, I just use a fairly basic url shortener.

a module, you mean, or something like bit.ly?

bit.ly-like. http://code.activestate.com/recipes/576918/

oh, so it encodes numbers using a random alphabet to make it hard to reverse?

Yeah.

that's pretty clever

hey guys! just a quick question, is there a way to use a forms.ModelForm for authenticating a user with username/password?

But since it is reversible, it works nicely for obscuring links to stuff that has an integer PK.

couchsurfer: you could probably use the user modelform and just include username/password and then run the authenticate function on it...

mattmcc: yeah, that's pretty nifty for that

Stavros how would i just include those fields?

i'm mostly interested in object ids in an API not being sequential, so that wouldn't work very well

couchsurfer of course you could. it's still a form. but the question is, why would you?

couchsurfer: contrib.auth already has an AuthenticationForm.

couchsurfer: include = ("username", "password"), but it's easier to just make a form

oh interesting

mattmcc thanks! i never knew...

It has a login view, too..

seconding using the built-in views; they're highly customizable

you just provide a template file in a known location and it works

anyone know what magic I need to submit a polygon drawn with google maps to a PolygonField/

?

yay, finally, my first templates are done: https://github.com/skorokithakis/django-project...

Stavros: how do project templates work?

Siecje: what do you mean?

I don't quite get how you use them

also there are no .html files in that repo

you use them when setting up a new project, instead of the default one

why would there be .html files?

oh I see, where to put templates and apps etc

yeah