On 5/21/07, Curtis <[EMAIL PROTECTED]> wrote:
> An alternate solution:
>
> response = HttpResponse(pdf, "application/pdf")
> response['Content-Disposition'] = 'attachment; filename=%s.pdf' %
> filename
> return response
I use a similar approach to output PDF's on our intranet
Maybe because there is a high change that you will try to find rows based on
this SlugField, so in common cases this INDEX will be nice.
Also it's documented on
http://www.djangoproject.com/documentation/model-api/#slugfield that this
field has an implicit db_index=True, BUT you can always pass
Hi,
On 4/8/07, Adrian Holovaty <[EMAIL PROTECTED]> wrote:
>
> * The name "values" is a bit too abstract -- it took me a while to
> figure out exactly what this framework *does*. Maybe something like
> "editable constants" or "model-specific options" would be more clear.
Isn't a constant
Maybe you can't find it because it's "wontfix" :))
http://code.djangoproject.com/ticket/3326
On 3/29/07, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote:
>
>
> On Thu, 2007-03-29 at 21:05 +0800, Russell Keith-Magee wrote:
> > Hi all,
> >
> > I just noticed that my RSS reader has stopped providing
Hi,
If you provide a BinaryField it's just a matter of time that "hacks" will
start to go out on blogs, the wiki or even django-users to get ImageField
and FileField on the database (there's a hack on this already), maybe it's
99% bad but if those fields are provided inside django it will be much
Uhm.. when did comments disappear? They're nowhere now!
It's nicer that way :) Forget my last comment!
On 3/27/07, Marc Fargas Esteve <[EMAIL PROTECTED]> wrote:
>
> w0w,
> That's really **cooler** than the previous method. I always wondered how
> often were the on-line docs up
Hi,
On 2/27/07, Geert Vanderkelen <[EMAIL PROTECTED]> wrote:
> Because the other Databases have 'limitations' or 'features' or
> 'defects' that MySQL might not have or whatever. Django is, as I have
> been told, database independent. And Django is working fine with
> MySQL, lets keep it that
Hi,
On 2/28/07, Russell Keith-Magee <[EMAIL PROTECTED]> wrote:
[...]
> Either way, the problem/limitations
> with MySQL needs to be mentioned in the documentation (both
> serialization and fixtures).
Yes, in really big red letters, we could add a directive for the
documentation rst for "thinks
By container we should mean the most top element so it should be the
or that has the label and the input below it ;)
On 2/16/07, Ivan Sagalaev <[EMAIL PROTECTED]> wrote:
>
> Marc Fargas Esteve wrote:
> > You could set the additional class to the container so you can
You could set the additional class to the container so you can use
simple CSS selectors to apply different styles to any element from the
container and inside it. Setting the class on the label or the input
field would not allow to modify the container.
My 0.02,
Marc
On 2/16/07, Waylan Limberg
Hi,
inline
On 2/9/07, James Bennett <[EMAIL PROTECTED]> wrote:
[...]
> But on the other hand, if somebody does decide to go a little while
> without an "svn up", it'd be nice to have this announced so they know
> that they should update (though I have my doubts about how many people
> actually
And I use windows 3.1 'cause I prefer it! Just joking ;)
But psycopg1 is obsolete so newcomers should be recommended to version
use 2 unless there are still outstanding issues with it. They can
always go to psycopg1 if they want ;)
On 2/9/07, Kenneth Gonsalves <[EMAIL PROTECTED]> wrote:
>
>
>
Hi,
inline
On 1/31/07, Matthew Flanagan <[EMAIL PROTECTED]> wrote:
> The Django buildbot slave is currently running inside a Solaris 10
> zone so it is virtualized...kind of.
>
> Let me clarify that testing python 2.3 and 2.4 would require a
> separate buildbot master than pybots unless you can
[note: maybe this message appears twice as I sent it with the wrong
reply-to and google-groups likes to reject it, if so, sorry ;) ]
Hi Matthew
On 1/30/07, Matthew Flanagan <[EMAIL PROTECTED]> wrote:
> I run the django pybot. It wouldn't be difficult to add other backends
> to the tests and is
On 1/30/07, Michael Radziej <[EMAIL PROTECTED]> wrote:
> Marc Fargas Esteve:
> That sounds interesting. (Did I mention that it should run python
> versions 2.3, 2.4 and 2.5? ;-)
As Matthew said this could be done with separate buildbots or slaves
running different jobs.
> I w
Hi,
inline
On 1/30/07, Michael Radziej <[EMAIL PROTECTED]> wrote:
[..]
> I'm now dreaming of a test service that would automatically run the
> testsuite for a given patch (or multiple patches) with all supported
> database backends ...
Also thought about that, getting up a buildbot for testing
Thanks Michael for the explanation, I took the ticket as example until
you pointed me to comment #9 :)
Cheers,
Marc.
On 1/25/07, Michael Radziej <[EMAIL PROTECTED]> wrote:
[...]
> This ticket is a bad example. It should be open, and it is only
> closed since reopen does currently not work.
>
>
Hi,
In the nice graphic on
http://www.djangoproject.com/documentation/contributing/#ticket-triage
#3279 would go from "Unreviewed" to the left to "worksforme" as the
resolution, but what Triage State would it get? "Unreviewed" is not
true, as it has been reviewed, but it's not "Accepted" either
Really nice work, congratulations! ;)
On 1/24/07, Michael Radziej <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> just to give you an idea how fast we proceed: currently 228 out of
> 655 open tickets have been reviewed, and that does not count all
> those that got closed during triage! Isn't that nice?
>
Hi there,
The triage system is really nice! but there's just one thing, with the
removal of priorities when a core developer goes to see the "Read for
check-in" tickets it has no way to know that some of those tickets
should be taken ASAP, for example: #3336 which solved broken links in
20 matches
Mail list logo
