DjangoBot: #django

basically, is there anything I should know

in terms of structuring my app, files to include/not include

that way it handles all the linking and path stuff for me, and it's linked to the directory i checked it out in

cpengwin: I don't think there are any RCS-specific tips on that one, really :)

this also has the added benefit of only adding that module to sys.path, and not adding all modules in the parent directory

I see.

so if that project has a setup.py

cpengwin: no pyc or pyo else nothing much

run python setup.py develop

ok

if you get an error

it's because they are using distutils instead of setuptools

and presumably also the data....

that's the other thing - database stuff

cpengwin: yes

storing settings for development vs. deployment

just change the line that imports the setup function to be "from setuptools import setup" and everything will work

Is there an easy way to make a file which I can check into SVN and preload into my django database?

Alright.

cpengwin: i somtimes include fixtures, but not automatic fixtres

those steps are actually what I use for getting django in to my Python installs as well

and is it resilient to changes in the model?

and now if you ever wanna update the sources just $ svn co, and the updated module is already linked

and you don't have to worry about munging PYTHONPATH

mikeal: svn up

whoops

svn up

haha

oh man, i can't wait until more people use git :)

or git svn rebase :P

mikeal: agree

what's git?

git is _really_ nice for this, because then if you wanna switch branches you just use git branch x

and all the sym links remain the same

alternatively just swap the directory

never really found the checkout functionality they have all that useful, mostly serves as a way to confuse the hell out of myself as to which branch I'm on

with svn i gotta go in to the branch i'm working in and re-run setup.py develop

ferringb: but it ells you why

tells

i just run $ git branch , before I do any real work

if you forgot a checkin

then i know which one i'm on

git wins over hg for me

far more comfortable w/ bzr personally, but to each their own

i really don't like hg

ecach their git :P

i really hate the way you put together patches

each

quick question: should i be using str(myint) to convert strings in django? or is there some unicode equivalent?

trbs: you there?

thinketh: erm, unicode() :��

u"string" to declare, or unicode(string)

the linux kernel uses git, is there really a choice?

:P

Magus-: thanks.

mikeal: thanks too!

but if you have characters that don't translate you'll hit errors

you might wanna use

"string".encode('utf8', 'ignore')

that'll save you from people getting 500 errors when they put in non-unicode characters

[530]: have you seen the new #2070 patch? :)

mikeal : assuming utf-8

axiak: think so

i'll assume all i want :P

unless you just added it

[530]: it's like 2 days old...and changes a lot of things

axiak: have looked at it but not to closely

did you get that thinketh ^^