+1 for Django
+2 for the dev Team...
Congrats Guys.
You are doing great...
Shihan
- Original Message -
From: "James Bennett" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>;
; <[EMAIL PROTECTED]>
Sent: Thursday, September 04, 2008 6:07 AM
Subject:
A bit of an anti-climax. Here I am setting up rc1 at 5am, and having trouble
building the html docs with sphinx.
I decided to copy-paste the error i'm getting, open my mailbox and whoah!
django 1.0 was released 4 hrs ago
Great work, guys - wish I had/could contributed more :(
On Thu, Sep 4, 2008
+1 for Django 1.0 party in Bogota, Colombia.
Thanks to the development team. And especially for Justin Bronn, for his gis
contribution.
Ariel Núñez // Project Manager // Puenti Ltda
Barranquilla // Colombia // South America
[EMAIL PROTECTED] // +57(300)8438443 // +57(317)3205876
On Wed, Sep 3,
Hi,
I'm a happy user of django, and I want to say this is the better
framework for a good, elegant and fast development, i wanna be a
developer of django but is something hard, in my country Colombia, I
say to everybody about this amazing framework and work in a couple of
projects for make more
On Sep 3, 2008, at 7:07 PM, James Bennett wrote:
>
> The Django team is pleased to announce the release of Django 1.0
> this evening:
>
> Download: http://www.djangoproject.com/download/
> Release notes: http://docs.djangoproject.com/en/dev/releases/1.0/
>
> Have fun with it, and we'll see you
On Sep 3, 2008, at 8:07 PM, James Bennett wrote:
> The Django team is pleased to announce the release of Django 1.0
> this evening:
>
> Download: http://www.djangoproject.com/download/
> Release notes: http://docs.djangoproject.com/en/dev/releases/1.0/
>
> Have fun with it, and we'll see you
Hi James,
The release notes has a string that seems wrong ... "Django 1.0
represents revision 88XX of our public repository". Did you forget the
XX bit ?
Regards
Rajeev J Sebastian
On Thu, Sep 4, 2008 at 5:37 AM, James Bennett <[EMAIL PROTECTED]> wrote:
>
> The Django team is pleased to
Congratulations!!
Was wondering if you could get a hold of adrian and get him to update the
python packages stuff to the latest version?
Otherwise looking good! :)
On Thu, Sep 4, 2008 at 12:07 PM, James Bennett <[EMAIL PROTECTED]>wrote:
>
> The Django team is pleased to announce the release of
The Django team is pleased to announce the release of Django 1.0 this evening:
Download: http://www.djangoproject.com/download/
Release notes: http://docs.djangoproject.com/en/dev/releases/1.0/
Have fun with it, and we'll see you in a few days for DjangoCon.
--
"Bureaucrat Conrad, you are
This is not a bug. It is how the permissions system works. So far as
the Admin goes, it is model granular, not row granular or field
granular, meaning that if you grant a user full access to the User
object, as you did, they can do anything to that table, including
change permission
On Wed, 2008-09-03 at 13:21 +0200, Michael Radziej wrote:
> Hi,
>
> changeset 8802 introduced a small paragraph about Boolean database fields.
> The problem is that the exact wording implies a guarantee to MySQL users
> that they will always get 0 or 1.
>
> I think we should leave a door open
Jacob's comment on #django-dev:
> that's been discussed ad-nauseum in the past. models don't
> have __setattr__ hooks for speed, so you can say
> "model.intfield = "Fish"" for all Django cares.
> [...] it's a well-known problem, but one without a "good" fix.
> I think model validation will
For anyone who's interested, it'd be great to meetup at DjangoCon to
go over a good design approach to composite fields.
On Sep 2, 2:44 pm, Rock <[EMAIL PROTECTED]> wrote:
> One use case for Composite Primary Keys is for setting up database
> partitions. In my case I am using Range-Hash
On Tue, 2008-09-02 at 22:02 -0700, David Cramer wrote:
> For anyone who's interested, it'd be great to meetup at DjangoCon to
> go over a good design approach to composite fields.
Take notes. There's going to be a lot going on at DjangoCon (including
celebrating), so there will be a group who
Hi,
changeset 8802 introduced a small paragraph about Boolean database fields.
The problem is that the exact wording implies a guarantee to MySQL users
that they will always get 0 or 1.
I think we should leave a door open to change this behaviour, and I suggest
to advice the user that this is
We've just put up the package for the first Django 1.0 release
candidate; this package contains all of the progress made on Django
through the alpha and beta releases, and is fairly close to the final
Django 1.0 release. It's still not recommended for production use, but
we do encourage everyone
16 matches
Mail list logo