I see there are multiple django bundles for textmate.
Which is the best one you recommend?
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-develop...@googlegroups.com.
To unsubscribe from this gr
With multiple database defined, what is the expected behavior for
syncdb and the other db related commands? The documentation shows that
it is relatively easy to associate an admin form with a given
database, but is there a way of associated a model or app to a given
database?
Regards,
Michael Man
On Tue, Dec 22, 2009 at 4:55 PM, Brett Hoerner wrote:
> On Dec 22, 4:27 pm, Russell Keith-Magee
> wrote:
> > * Allow TEST_NAME=None to mean "don't try and instantiate this
> > database in test mode"
>
> That sounds good, too.
>
If I was using the slaving part of multi-db i'd be very likely to w
On Dec 22, 4:27 pm, Russell Keith-Magee
wrote:
> * Allow TEST_NAME=None to mean "don't try and instantiate this
> database in test mode"
That sounds good, too.
> * Allow a top level TEST_DATABASES setting; TEST_DATABASES would
> override DATABASES; if TEST_DATABASES isn't defined, then TEST_N
On Wed, Dec 23, 2009 at 7:06 AM, Brett Hoerner wrote:
> On Dec 19, 6:48 am, Russell Keith-Magee
> wrote:
>> You're right - read slaves are an intended common use case
>
> I know the branch landed but I'd like to mention another issue
> regarding read-slaves, hope that's OK. :)
>
> Running tests a
On Dec 19, 6:48 am, Russell Keith-Magee
wrote:
> You're right - read slaves are an intended common use case
I know the branch landed but I'd like to mention another issue
regarding read-slaves, hope that's OK. :)
Running tests against code that uses master and read-slaves (but
actually point at
Am 22.12.2009 um 08:20 schrieb Simon Willison:
> On Dec 22, 12:52 am, Johannes Dollinger
> wrote:
>> I'd like some more kwargs to Signer and TimestampSigner. Mostly
>> what's
>> inhttp://dpaste.com/136418/(except the `separator` kwarg, which was
>> a bad idea as it depends on encode()): Signer
A ticket has already been created for this, but SmileyChris
recommended I bring the issue up here.
Working with pagination and query strings within a template can be
painful. Personally, I have never had a situation when I was
paginating using a GET parameter where there were not other parameters
Having talked to James about this I'm holding off on the commit until
we've had it reviewed by real cryptographers. I'll aim to get it in
before the 1.2 beta feature freeze.
Cheers,
Simon
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To
... and congratulations to Marc Garcia and Jannis Leidel for the i18n/
l10n improvements that just went in as well. Also congratulations to
everyone for the other awesome commits going in at the moment. There
are far too many congratulations to spell them all out at the moment
(with hindsight I wis
On Tue, Dec 22, 2009 at 2:44 PM, Peter wrote:
>
> I just noticed and can only agree... nice work.
>
> //Peter
>
> On Tue, Dec 22, 2009 at 18:27, Simon Willison
> wrote:
>>
>> And a big congratulations to all involved. Here's the changeset log
>> (on GitHub since Trac seems not to like being linke
I just noticed and can only agree... nice work.
//Peter
On Tue, Dec 22, 2009 at 18:27, Simon Willison wrote:
> And a big congratulations to all involved. Here's the changeset log
> (on GitHub since Trac seems not to like being linked to at the
> moment):
>
>
> http://github.com/django/django/com
On Tue, Dec 22, 2009 at 12:58 AM, Jani Tiainen wrote:
> Escaping bug exists in Oracle 9.2.0.5 and earlier. It was fixed in
> patchset 9.2.0.6 and any later version.
>
> What comes to Oracle official support options for 9.2:
> Premier Support Ends: 31-Jul-2007
> Extended Support Ends: 30-Jul-2010
>
On Dec 22, 2009, at 12:04 AM, Mario Briggs wrote:
> Hi Ian,
>
> Ian Kelly wrote:
>> Not currently, no. And if I were to put in some work on improving on
>> the Oracle backend's support for filtering on TextFields, I would
>> concentrate first on fixing the query so that it correctly compares
>>
I've previously brought up some issues with the removal of certain
options from the choices on localflavor's USStateField[1] as a result
of ticket #8425[2] and, with feature freeze for 1.2 approaching and
perhaps more time soon to be available for such things, I'd like to
call attention to it again
And a big congratulations to all involved. Here's the changeset log
(on GitHub since Trac seems not to like being linked to at the
moment):
http://github.com/django/django/commit/836d297e68d6a63103780295adebf6eaf6779611
And here's the documentation:
http://docs.djangoproject.com/en/dev/topics/db
As Russell said, this is probably a bad time, but I thought I'd throw
in some quick notes nonetheless.
> '''django-modeltranslation''': I think this general approach is the way to go
I agree that it's probably the best alternative available currently,
but still not without significant drawbacks (
On Dec 22, 6:22 am, Russell Keith-Magee
wrote:
> As far as the patch itself is concerned, looks good to me. My only
> other request would be a serving of dogfood - if we're going to
> include a signed cookie module, it would be nice to prove that it can
> actually be used by actually using it.
I'
18 matches
Mail list logo
