DjangoBot: #django

Hi. Is there some way to be able to import basic django modules (without actually using them) without having a django project set up (and thus no settings module to point DJANGO_SETTINGS_MODULE to)?

I want to generate documentation for a django-helpers style library

which has to import the modules provided by that library to get to the docstrings

and I don't want to have try/except blocks around my django imports just so generating the docs works

i hate that ;x

what does this mean? [Errno socket error] (111, 'Connection refused')

looks like a mysql error

becky: most likely permission issue

you probably didn't bind to the right interface in my.cnf

becky, did u get my message?

before i got connection reset by peer?

hense: check the faq in the topic

<sayane> becky, google blocked your server's ip

<sayane> and sitemap framework or something tries to "ping" google

sayane_: no

sayane_ ok i'll disable signal and try

any idea why they would do that?

too lot of "pings"

so that you don't do a DOS/DDS on them

rozwell: hm, I've been though there but I don't see anything related to my question in there?

ok i'll put some sleeps in or something

rozwell: what item are you refering to?

hense: http://code.djangoproject.com/wiki/IrcFAQ#Shell

hense, what is your question?

hense: if you're importing django stuff, then you need to set up the environment for it

rozwell: how does that relate to my question?

sayane_: http://dpaste.com/67248/

sayane_: (just a paste of what I wrote earlier to state my question)

sayane_ seemed to have worked. I'll have to see why they banned me :(

becky, move your ping code to command and execute it with cron

hense, it depends

for example models and template modules needs to be configured before using

and django.utils.html doesn't

sayane_ the code is set up to only ping when object is entered. objects are entered one at a time maybe one/week... ping code only updates if created or deleted...

(this is just an example)

there's no using involved at all, as I said, I just want to import the modules so the docstrings can be read

and there's no code other than module and class definitions on module level

(and the django imports which is my problem)

hense: as i said, you're still going to have to set up the environment for django

hense the problem is that even if you define a model, there is code executed behind the scenes

I've been reading the django code and it seems that I really have no other way than to set up a simple setting though settings.configure

sayane_: I know how python class creation works

sayane_: there are no models though.

so what modules are you using?

as I said, there is no code from any django modules executed..

hense: if you'd read that link i gave you you'd know of several ways to set up the environment without creating a settings module

they're just imported

hense: importing does execute code

the django modules

sigh

any modules

top level code gets executed at import time

sigh is right... Managers, QuerySets oh my!

oh you illy bugger

I've been coding python vor 15 years now, stop with the basics already :)

well then you know that

the point is that I'm not using anything provided by the django modules

yet you deny it

if you're importing it you certainly are

and that it's really silly that they seem to need that environment setup anyway

right, well it is what it is

they're executing this code on module level

which is really bad style

yet it happens

but, well, it's as they say, if you know python, you won't like django

very true.

if __name__ == '__main__' executes at the module level

hense: well besides settings and a couple of other things it's quite pythonic

the fuck 8)

rozwell: 'a couple of other things' being incredibly ugly stuff like this class Meta business

hense: i don't find that ugly

besides creating horrific clashes in terminoligy since python already has metaclasses, it's completely useless

there's no clash there

of course there is.

it's never referred to as a "metaclass"

it's referred to as the Meta inner class

right. not confusing at all. 8)

anyway, it's only there to keep metadata isolated

i've never encountered anyone being confused by it

that's probably because ~90% of all django programmers seem to be utter python newbies that probably never heard of metaclasses

well, if they've never heard of meteclasses, there's no problem then, is there? :)

anyway, django isn't the only python web framework out there

so if you don't like it, hey you've got options

and metaclasses are used in a number of places in django

in reality, you often haven't

so it's not like you wouldn't encounter them if you're using django

often haven't what?

only a small percentage of programmers actualy get to chose all the technologies they have to use

hense: what is your point?

heh, and normally django isn't a top down decree

aonweb: that was a response to rozwell saying I had a choice about not using django

oh ok. carry on

anyway, if you come into it with the notion that it's not for you, you're probably going to find it's not for you

rozwell: erm, what? you know that programmers work in teams, right?

and i suppose that can't be helped

yes

i don't see what that's got to do with anything

what does it mean if Im getting a StopIteration exception when running models.AClass.objects.extra(...)

rozwell: in a team, decissions get made. normally not by democratic processes.

fualo: you're using an iterator wrongly