On 10/19/07, Jared Flatow <[EMAIL PROTECTED]> wrote:
>
> On Oct 18, 2007, at 8:55 PM, Marty Alchin wrote:
> > On 10/18/07, Jeremy Dunck <[EMAIL PROTECTED]> wrote:
> >> I'd like to improve the quality of Django's documentation.
> >
> > I can't say I'm surprised to hear that. I've heard several
On Oct 18, 2007, at 8:55 PM, Marty Alchin wrote:
> On 10/18/07, Jeremy Dunck <[EMAIL PROTECTED]> wrote:
>> I'd like to improve the quality of Django's documentation.
>
> I can't say I'm surprised to hear that. I've heard several requests
> for changes in the documentation. Heck, I think I've
There is an ongoing discussion on the psycopg list and trac regarding
the use of psycopg with multiple interpreters.
fog is proposing dropping support for multiple interpreters rather
than dealing with the (notably sticky) issues.
Trac: http://www.initd.org/tracker/psycopg/ticket/192
Mail
Watch and download the latest wallpapers and themes.
Brand New for windows, Funny, love and celeberity wallpapers here
just open the site and download your wallpapers.
http://free-themes.notlong.com
--~--~-~--~~~---~--~~
You received this message because you are
i didn't notice the reset command when i asked the original question. i
always pipe my sql. which is what i'm most comfortable with, but i
understand other people like the convenience of the management commands
running the sql directly.
no interactivity beyond "here's what i want to run.
On 10/19/07, Derek Anderson <[EMAIL PROTECTED]> wrote:
>
> Russell Keith-Magee wrote:
> as was somewhat the intent of the question. :) i was trying to figure
> out of there's an existing style i should model my evolve commands after.
That wasn't the question you asked. You asked if sqlreset
Russell Keith-Magee wrote:
> (sql)reset is broken as currently implemented, and as far as I can
> make out, it can't really be fixed without some major changes.
> However, I'm not convinced it is worth spending the effort to fix the
> problems that exist. The problem (sql)reset is intended to
On Thu, 2007-10-18 at 21:55 -0400, Marty Alchin wrote:
> On 10/18/07, Jeremy Dunck <[EMAIL PROTECTED]> wrote:
> > I'd like to improve the quality of Django's documentation.
>
> I can't say I'm surprised to hear that. I've heard several requests
> for changes in the documentation. Heck, I think
On 10/19/07, Kenneth Gonsalves <[EMAIL PROTECTED]> wrote:
>
>
> On 18-Oct-07, at 11:28 AM, Derek Anderson wrote:
>
> > what are thoughts on a new option to sqlreset (and others, as
> > appropriate) to apply the change to the db? something like this:
> >
> > ./manage.py sqlreset --apply
>
>
On 10/18/07, Jeremy Dunck <[EMAIL PROTECTED]> wrote:
> I'd like to improve the quality of Django's documentation.
I can't say I'm surprised to hear that. I've heard several requests
for changes in the documentation. Heck, I think I've even been one of
them, some time ago.
I like the idea of
On 18-Oct-07, at 11:28 AM, Derek Anderson wrote:
> what are thoughts on a new option to sqlreset (and others, as
> appropriate) to apply the change to the db? something like this:
>
> ./manage.py sqlreset --apply
i thought sqlreset was deprecated
--
regards
kg
On Thu, 2007-10-18 at 19:18 -0500, Jeremy Dunck wrote:
> Devs,
> I'd like to improve the quality of Django's documentation.
> I'm sure there will be many opinions on what "improvement" would mean.
>
> I'd like to solicit ideas from django-users regarding how people use
> the docs and wish
Devs,
I'd like to improve the quality of Django's documentation.
I'm sure there will be many opinions on what "improvement" would mean.
I'd like to solicit ideas from django-users regarding how people use
the docs and wish they were different.
OK? I don't want to start the torrent of
Perfect, thanks.
I could create patch for my ticket.
Marc
On Oct 18, 10:06 pm, "Jacob Kaplan-Moss" <[EMAIL PROTECTED]>
wrote:
> On 10/18/07, Adrian Holovaty <[EMAIL PROTECTED]> wrote:
>
> > No -- the code for djangoproject.com that you see in Trac/Subversion
> > is indeed the code we use for
On 10/18/07, Adrian Holovaty <[EMAIL PROTECTED]> wrote:
> No -- the code for djangoproject.com that you see in Trac/Subversion
> is indeed the code we use for the site, but sometimes we make changes
> to the site without checking them in. Looks like we haven't checked in
> our changes in a couple
On Oct 17, 6:47 pm, "James Bennett" <[EMAIL PROTECTED]> wrote:
> You want to read this thread (first result when searching the group
> archive for "queryset exists"):
>
> http://groups.google.com/group/django-developers/browse_frm/thread/54...
I mentioned that thread at the bottom of my post,
On 10/17/07, Marc Garcia <[EMAIL PROTECTED]> wrote:
> I don't know if it's obvious for everybody except me :) but trac
> version of django website is only as an example of website, and "real"
> version is maintained privately?
Hi Marc,
No -- the code for djangoproject.com that you see in
On 10/17/07, Jeremy Dunck <[EMAIL PROTECTED]> wrote:
>
> However, there are many strings that can be passed through that
> filter and sill will break javascript string literals.
Specifically, as you point out, strings that contain "" --
the main point here is to reduce the chances of XSS
2007/10/18, Malcolm Tredinnick <[EMAIL PROTECTED]>:
>
> On Tue, 2007-10-16 at 21:52 +0200, David Larlet wrote:
> > 2007/10/10, David Larlet <[EMAIL PROTECTED]>:
> > >
> > > BTW, no more thought about the way of handling PUT? I've just added a
> > > patch against test.client which add .put() and
The Asia Pacific Leadership Program (APLP) is the center of excellence for
leadership education in Asia Pacific and a signature program of the
East-West Center. The program links advanced and interdisciplinary analysis
of emergent regional issues with experiential leadership learning.
The APLP
*What is the Asian Scholarship Foundation?*
The Asian Scholarship Foundation (ASF) is an Asian-led non-profit
organization funded by a grant from the Ford Foundation that is mandated to:
- strengthen regional capacity to produce scholarly research on Asian
societies;
- create a
2007/10/18, Derek Anderson <[EMAIL PROTECTED]>:
>
> hey,
>
> what are thoughts on a new option to sqlreset (and others, as
> appropriate) to apply the change to the db? something like this:
>
> ./manage.py sqlreset --apply
>
> just as a time saver. i'd write the patch if no one's
There is no need for this. ./manage.py reset runs sqlreset.
On Oct 17, 11:58 pm, Derek Anderson <[EMAIL PROTECTED]> wrote:
> hey,
>
> what are thoughts on a new option to sqlreset (and others, as
> appropriate) to apply the change to the db? something like this:
>
> ./manage.py sqlreset
23 matches
Mail list logo
