Log file Viewer
#dcpython logs for Tuesday the 29th of November, 2011
[16:18:07] <dahoste> but I was feeling even worse than usual, about not going, since it'd been hyped up. :)
[16:32:00] <j00bar> kennethreitz: chords are tasksets that have a callback when all tasks in the taskset are complete
[16:32:39] <j00bar> redis backend basically sets up a counter and since redis has atomic decrement-and-return, decrements that counter as each task in the taskset is finished until it hits zero - at which point the call back is dispatched
[16:33:22] <j00bar> oh - we use redis for a lot of other stuff. the celery talk wouldn't be redis specific.
[16:36:10] <j00bar> the hidden gem of redis - super powerful, super hard to use right: http://redis.io/commands/sort
[18:57:33] <aclark> j00bar: right. we usually go around the room for most of the first hour then have a talk
[19:23:15] <hazmat> aclark, it might be more aptly titled "friends don't let friends use celery" ;-)
[19:24:12] <hazmat> its probably fine with redis, but for other storages, it needs to more actively promote ones that work at scale
[19:24:52] <hazmat> its a lot of code and policy for a problem that can be handled pretty simply by rolling your own
[19:27:07] <aclark> yes we did: http://www.slideshare.net/richleland/celery-the-distributed-task-queue
[19:54:30] <aclark> kennethreitz: i'm WTF'ing over here. whenever i use the zc.buildout to install django i don't have to think about it. if i pip install it i'm lost. i should just look at what that recipe does as a reminder
[19:55:38] <aclark> i'd love to be able to say DJANGO_SETTINGS_MODULE=some.module.in.some.package but i get the impression it's looking for an actual module name not a package name ;-)
[20:01:26] <aclark> i also get the sense that i just STFU and create non namespaced package i can do it like they do in https://docs.djangoproject.com/en/dev/topics/settings/ e.g. mysite.settings
[20:12:05] <aclark> oh neat so if you define a settings the module the admin stops allowing you to create new projects
[21:12:15] <aclark> Ah, i think what i was missing is that once you create a project you don't need django-admin.py anymore you can use manage.py
[21:53:21] <richleland> every time I create a virtualenv that uses Django, I modify ~/.virtualenvs/MYENV/bin/postactivate
[21:54:36] <richleland> whereas with manage.py you have to be in the folder that contains it or specify the full path to it
[21:59:02] <aclark> richleland: there seems to be some disconnect between Django's conventions and Python's packaging conventions… or something
[22:02:17] <richleland> I started to implement something like it at natgeo - natgeo.stats, natgeo.core, etc.
[22:03:55] <richleland> I wonder if (in terms of Django) the preference for loose coupling of apps tends to make folks think that namespacing is inherently weird or something
[22:04:41] <richleland> I'd see namespaces in Django being used more to group open-sourced, organization provided apps, but I don't see that too often
[22:04:50] <aclark> richleland: apps and projects are like Plone's products and instances… terms that don't mean anything in the larger Python scope of things
[22:10:35] <aclark> richleland: i think i'm just trying to get at "What is the Python terminology" for this, where appropriate. Obviously a settings module is something that Python is not going to have. So can I pip install a bunch of packages, export DJANGO_SETTINGS_MODULE=some.namespaced.package.settings then run bin/paster serve myapp.ini (and only call manage.py or django-admin.py for django specific things)