Hi Developers,
Basically, I wanted to ask for some devel's opinions on something.
When using the Django signals framework (which, by the way, is a very
good way of decoupling reusable apps whilst allowing for deep
integration), I sometimes find that a signal receiver does not need to
be called
On Sat, Jan 3, 2009 at 5:25 PM, Russell Keith-Magee
wrote:
>
> On Sun, Jan 4, 2009 at 4:28 AM, Brantley Harris wrote:
>> Ah yes, this is definitely a problem. See, I had to be able to import
>> based on a string (database backend), and I was having problems doing
>> so without an absolute impor
WTF? couchdb and MySQL are intended for totally different purposes...
which one is "better" depends on what you are trying to do.
-jasper
On 4/01/2009, at 10:08 AM, mobil wrote:
>
> Ten reasons why couchdb is better than (off topic)
>
>
> http://pylab.blogspot.com/2009/01/ten-reasons-why-couc
On Sun, Jan 4, 2009 at 4:28 AM, Brantley Harris wrote:
>
> On Sat, Jan 3, 2009 at 4:43 AM, Russell Keith-Magee
> wrote:
>> If there is some technical reason why the django.contrib namespace is
>> required, then raise that issue on the developers list and we can see
>> what we can do to break tha
This is not the place for this, this mailing list is for the
development of Django itself, quite frankly it really isn't
appropriate for django-users either.
Alex
On Jan 3, 3:08 pm, mobil wrote:
> Ten reasons why couchdb is better than (off topic)
>
> http://pylab.blogspot.com/2009/01/ten-reaso
Ten reasons why couchdb is better than (off topic)
http://pylab.blogspot.com/2009/01/ten-reasons-why-couchdb-is-better-than.html
Guys I wrote up a small list of reasons why i think couchdb is way
bettter than mysql. Do let me know what you think
--
Gpirate the top torrent search engine
http
On Sat, Jan 3, 2009 at 4:43 AM, Russell Keith-Magee
wrote:
> In the aftermath of DjangoCon [1], Simon Willison, Andrew Godwin and
> myself started the django-migrations SIG [2], with the aim of getting
> a migrations framework into the Django core that draws from the best
> parts of our three res
On 20 déc 2008, 21:52, rndblnch wrote:
> hi,
>
> some times ago, i created a ticket for a bug in file locking on my
> system (volume mounted with appletalk on a mac) [0].
> after a first proposal for fixing the bug (with patch), i asked for
> feedback and got some [1].
> i then proposed another
Russ has made some good points, but I feel a need to chime in anyway!
Brantley Harris wrote:
> The idea is a database migration system that:
> * Is simple.
> * Doesn't make you use sql. This is an orm, we shouldn't have to use sql.
>
As Russ said, there's a need for SQL, and his point
On Sat, Jan 3, 2009 at 5:29 AM, Brantley Harris wrote:
>
> Having not been content with the state of Django migrations systems,
> I've created one of my own:
>
> http://www.bitbucket.org/DeadWisdom/migratory/
In the aftermath of DjangoCon [1], Simon Willison, Andrew Godwin and
myself started the
To begin with, my first impressions are that it's a really good
solution, and I'm interested to see how it shapes up in production
apps :)
I'm slightly concerned with having to link to it from django.contrib.
This is generally regarded as a bad idea, mainly because it makes it
difficult to get up
11 matches
Mail list logo
