DjangoBot: #django

weird, I think multiple db would be avesome if done right

kojiro: by current publisher, i mean the one that's being accessed when the function is executed

It's theoretically a lot easier to implement multi-db after qsrf.

kojiro: for instance, if you try to edit a Publisher, this method will run before it displays the Publisher information

damonj: it's not obvious to me that any is being accessed when render_change_form(...) is run

what is qsrf?

kojiro: i'm sorry. i'll try to be more clear. this method is overriding a method in the admin so that I can pass more variables to a pre-made admin form

So much stuff to read up on.

damonj: render_change_form is a method of a PublisherOption, which afaict doesn't specifically relate to a given Publisher *except* as defined by your database's entity relationships, which are not clearly defined in your paste...

gaztanshana: The queryset refactor branch, it made some fairly significant changes to the ORM's internals.

damonj: can you paste super?

kojiro: super is django.contrib.admin

damonj: ah

mattmcc; This is something that will be implemented later?

No, it was merged some time ago.

In what way does it make implementing multi-db easier? Development in django or for me as "end user" hehe

I would bet dev. in django :P

Oww, I'd love to find out how to make it available to the world. But some tasks are beyond my scope. :/

can anyone tell me if this is a bug: http://dpaste.com/72803/ or am I doing something wrong? I'm using similar code to what's documented here: http://www.djangoproject.com/documentation/mode...

magus: looks like its working now. i can access the css n js files directly now. let me check. if it does not work then i'll paste the error message using dpaste

damonj: I'm sorry, so far I can only think to search the database itself for some foreign key on Publisher. I don't think that's what you really want.

thanks a lot

i did make some changes in the settings

Killarny: If you want to keep models in a module that isn't called 'models', you need to do a little hackery with the app_label option.

never heard of that..

now you have

most people don't split their models out into multiple files

damonj: I guess what I'm saying is that if PublisherOptions has a Publisher object, it should be rather obvious what it is. The programmer hopefully named it something clear, like self.publisher, or self.current_publisher, or something

but it doesn't make contextual sense that a PublisherOptions would have a single Publisher

hey whats the new method for saving an uploaded file? no longer model.save_member_file() ?

jarrod_: check the docs.. it changed a couple of weeks ago

jarrod_: http://www.djangoproject.com/documentation/uplo...

do i have to utilize chunks() directly?

i saw that

seemingly all python mysql integration is far at hand

for webdevelopment

I've never heard anybody say "far at hand" before

gaztanshana: what exactly does that mean?

I like being playful.

it's kind of an ironic juxtaposition

hehe, yeah. :)

kojiro: sorry about that, i was afk for a sec. thanks for the help anyway. i'm going to try and find a way around this.

rozwell, well, like i said, using python for a website admin panel seemed like a cool idea, but there is only a rather minimal db api

damonj: good luck

gaztanshana: compared to what?

damonj: you could always execute a bare SQL statement that matches up a known with an unknonw

my own expectations hehe

unknown*

gaztanshana: Well, libmysqlclient isn't a very elaborate library in the first place.

gaztanshana: you were expecting something from mysql?

gaztanshana: If you're looking for a lot of higher level features, you probably want to look at higher level tools like sqlalchemy.

i mean you've got a connection and a cursor, what else do you need?

is there a self tostring method that's inherent for every object?

damonj: __unicode__ ?

well alright, plus sqlalchemy seems interesting

can i do self.__unicode__ ?

Well, normally you'd do str(obj)

damonj: according to the tute, you need to define __str__(self): return self.name (or something appropriate)

why would you do that ?

i want to see what's inside of it

Oh.

__unicode__ is prefered, as it get's converted down if __str__ is needed.

Then you're actually asking for introspection, like dir()

jinzo: eh, then the tute needs to be updated! ;)

some python magick yes :)

what's dir do?

it'll display all functions/methods that can be done on a object

The current tutorial doesn't use __str__, only the ones for past releases.

mattmcc: ah

<-- behind the times

^^ damonj

ah, is there anything that displays all the variables that something has?

jinzo: That's... not where dir() comes from.

damonj, scrach that url, I clicked it too quick,

mattmcc, I was too quick, sorry for that

http://www.network-theory.co.uk/docs/pytut/dirF... <-- that'll be right

again, I stay corrected ( & note to myself, that I need to sleep as I'm talking/coding nonsense lately )

more general talk about introspection

but dir() is there as well

if i add request to the context processors, and i am allowing users to create emails by providing a template that uses the {{variable}} style replacement, will that be subject to them having the ability to do something like {{request.user}} ?