Awesome. Thanks!
On Tue, Apr 1, 2008 at 10:27 PM, Jacob Kaplan-Moss <
[EMAIL PROTECTED]> wrote:
>
> Hi Justin --
>
> Yes, there is a Django Software Foundation. We're still working on
> getting everything set up and all the paperwork filed, but it does
> exist :)
>
> Jacob
>
> >
>
--
Justin Li
Hi Justin --
Yes, there is a Django Software Foundation. We're still working on
getting everything set up and all the paperwork filed, but it does
exist :)
Jacob
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Dja
Hey guys, I remember hearing about the DSF at PyCon. Is it a reality yet?
Is the official name the DSF? I could use a bit of guidance for an article
I'm writing up.
-justin
--
Justin Lilly
Web Developer/Designer
http://justinlilly.com
--~--~-~--~~~---~--~~
You
Introduction of resource-based Models
=
My name is Sebastian Hillig and I currently study IT Systems
Engineering in Potsdam/Germany at the Hasso Plattner Institute.
I came to Django when exploring the "world" of web frameworks about
1.5 years ago and gladly go
On Tue, Apr 1, 2008 at 7:41 AM, Russell Keith-Magee
<[EMAIL PROTECTED]> wrote:
> * Existing permalinks need to be preserved in some fashion, if only
> so that the archive of answers in django-users continues to be a
> useful resource.
It'll be tough. The worst part about anchors is that they
On Mon, Mar 31, 2008 at 7:48 PM, James Bennett <[EMAIL PROTECTED]> wrote:
> The next release will have 'M-x copyeditor' for that, actually...
See, this is why I like to mention Emacs 'round here; I can always
count on James for the follow-up. I'll tell you what, though, "M-x
copyeditor" would *t
On Mon, Mar 31, 2008 at 7:47 PM, pbx <[EMAIL PROTECTED]> wrote:
> Second, I take and agree with your point about editorial authority.
> Leaving aside the question of outside resources, I wonder if some
> pathway for user feedback or annotation of the official docs, in
> addition to the ticket
On 4/2/08, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote:
>
> > It may be worth checking if this is still a problem with queryset-
> > refactor; if it is stil a problem, it might be better to fix the
> > problem there, rather than trunk.
>
>
> Michael's using the branch (see the first quoted sec
Whoops.. I missed this a couple of days ago. I think I lost
consciousness somewhere in the Py3k thread when catching up after the
weekend.
On Tue, 2008-04-01 at 20:45 +0800, Russell Keith-Magee wrote:
>
> On 31/03/2008, at 2:33 AM, mtrier wrote:
[...]
> This is the behavior I'm seeing
> > on Que
On Tue, 2008-04-01 at 10:10 -0700, Adam V. wrote:
> In DateTimeField.get_db_prep_save there is a hard-coded check for the
> mysql backend, which drops the microseconds from the value.
>
> I'm working on an external MS SQL backend (django-mssql) and I'm
> running into a different problem here.
>
On Mar 31, 7:45 pm, "Jacob Kaplan-Moss" <[EMAIL PROTECTED]>
wrote:
> I'm embarking on a mission to refactor Django's documentation;
Great! I'll be happy to help out with some of the grunt work as and
when
I can find a spare moment.
> * Beginner material: we've got a good amount if this in t
> So feedback is welcome, please give it.
Breaking the huge documents into smaller chunks for readability is
good... but please do leave the original huge ones as well! There are
cases where "a huge document" serves more help than "a bunch of
smaller ones" and really has its worth.
Opening /cache/
On 31/03/2008, at 2:33 AM, mtrier wrote:
>
> Before opening a ticket I thought I would check what the expected
> behavior is for generative values(). This is the behavior I'm seeing
> on Queryset Refactor branch and to me it seems like it is not the
> correct behavior.
>
from original.foo.
On 01/04/2008, at 2:45 AM, Jacob Kaplan-Moss wrote:
>
> I'm embarking on a mission to refactor Django's documentation; this
> is where
> you give me feedback about how much crack I'm smoking. Keep in mind
> that most
> of this post fits into the "heads-up" category: if I'm not asking
> for
> I have a patch in my backend already, to enable regex searches in MS
> SQL. I think this is reasonable, as you have to install either a COM
> or CLR extended stored procedure in your database to get this
> functionality. Inserting values in a DateTimeField is perhaps a bit
> more basic a functio
> I think that it's perfectly OK to distribute a patch to change the
> hardcoded functionality -- it's far better than trying to monkey-patch
> the code under active development.
I have a patch in my backend already, to enable regex searches in MS
SQL. I think this is reasonable, as you have to i
On Apr 1, 9:10 pm, "Adam V." <[EMAIL PROTECTED]> wrote:
> In DateTimeField.get_db_prep_save there is a hard-coded check for the
> mysql backend, which drops the microseconds from the value.
>
> I'm working on an external MS SQL backend (django-mssql) and I'm
> running into a different problem here
In DateTimeField.get_db_prep_save there is a hard-coded check for the
mysql backend, which drops the microseconds from the value.
I'm working on an external MS SQL backend (django-mssql) and I'm
running into a different problem here.
DateTimeFields are sent to queries as unicode which looks like
I'm looking for feedback on my SoC application which I call
"Effortless Model Testing". EMT would add sample instance generation,
fuzz testing, and (if still necessary) model-level validation to
Django.
I have my ideas explained in detail on my web page:
http://sarcasticzombie.net
Anyone willin
On Tue, Apr 1, 2008 at 7:39 AM, Tim Chase
<[EMAIL PROTECTED]> wrote:
> If this is a fluke that will eventually be "fixed", will there be
> a way to replicate this sort of behavior (or at least some of the
> side-effects), to get/keep "mix-ins", such as
[...]
Yes. In fact, it already is fixed.
>> class X(models.Model):
>> x = models.CharField()
>>
>> class Y(X):
>> y = models.CharField()
>>
>> class Z(X):
>> z = models.CharField()
>>
>> produced the tables
>>
>> x(id, x)
>> y(id, x, y)
>> z(id, x, y, z)
>>
>> All I need to know is if this is some kind of fall-back till full-
>>
Model inheritance is not there yet. You can take a look at the
queryset-refactor branch, since Changeset 7126 moder inheritance begun
to take shape.
The changeset also includes documentation about that. You can either use
this branch or wait until it gets merger to trunk.
http://code.djangoproje
On Tue, Apr 1, 2008 at 2:31 AM, jurian <[EMAIL PROTECTED]> wrote:
> All I need to know is if this is some kind of fall-back till full-
> blown model inheritance is implemented, or if this is just a fluke.
It's a fluke. More information can be obtained from a Google search
for "Django model inhe
I think I might have the wrong idea about model inheritance.
I was using the 'newforms-admin' branch and implemented some model
inheritance just to see if it works and it did. Well, let's say that
it did what I had expected, or wanted it to do at the time.
class X(models.Model):
x = models.Char
24 matches
Mail list logo
