On 4 Aug 2009, at 00:50, Russell Keith-Magee wrote:
>>
>>
>> Does anybody have any opinions on the current way of using methods on
>> the Feed object (title(), link(), description() etc) to build the
>> feed? For me, it has proved inflexible and a little messy, but I
>> can't
>> think of a bett
I think we could think about implementing of session namespaces in
similar way as url namespaces was added in Django 1.1
http://docs.djangoproject.com/en/dev/topics/http/urls/#url-namespaces
The point is to not populate global namespace of sessions by using
session variables in various applicatio
Hi David,
I read your first post now. Then I think it could be great solution if
it's possible to be implemented.
Perhaps I appreciate less lines in every translation model. If you
look at:
class SomeObjTranslation(models.Model):
language = models.CharField(max_length=5, \
Hi Karen
Thanks for your reply. I have found out a set integrity off clause in
DB2. I would try to work this out and see if it helps.
On Jul 31, 5:13 pm, Karen Tracey wrote:
> On Fri, Jul 31, 2009 at 3:15 AM, Tarun Pasrija
> wrote:
>
>
>
> > Hi
>
> > While regressing the ibm_db_django adaptor
Hi Karen
Thanks for your reply. I have found out a set integrity off clause in
DB2. I would try to work this out and see if it helps. Like in MS SQL
Server, there is no concept of foreign references in DB2 but I am
hoping the set integrity clause in DB2 should certainly help.
Thanks and Regards
Maybe you misunderstood -- I just meant for `firstof` and `cycle`, not
template tag implementation in general.
On Aug 3, 4:53 pm, Malcolm Tredinnick
wrote:
> On Mon, 2009-08-03 at 16:25 -0700, ab wrote:
> > Is this something that could be backwards-incompatible in 1.2?
>
> Please, no. There are
Hey all,
This week I implemented the metaclass based solution for backwards
compatibility in the Field API that Jacob suggested last week. Then I
implemented by first stab at a solution to the Oracle/backend with
custom query object problem. However, I don't have access to any of
the the DBs I'
Am 04.08.2009 um 18:31 schrieb Daniel Pope:
>
> 2009/8/3 Jacob Kaplan-Moss :
>> 1. Propose a new shortcut function. Bonus points for a patch.
>
> In all my projects I use a file of my own shortcuts:
>
> http://dpaste.com/hold/75120/
>
There is also django-annoying [1] which has (besides some IM
2009/8/3 Jacob Kaplan-Moss :
> 1. Propose a new shortcut function. Bonus points for a patch.
In all my projects I use a file of my own shortcuts:
http://dpaste.com/hold/75120/
NB. I knew as I wrote the MAGICTEMPLATE shortcut that I would never
actually use it. The idea was to eliminate ALL of t
On Tue, Aug 4, 2009 at 4:52 AM, Simon Willison wrote:
>
> On Aug 3, 3:53 am, chairface wrote:
>> Also, it is only a single video, but that video
>> is a pretty good resource for the topic of Django's future. It was
>> the topic of the entire hour. Are you implying that it's a poor
>> source for
On Tue, Aug 4, 2009 at 7:09 PM, Tom Evans wrote:
>
> Hi all
>
> A while ago, I added support for testing if an element is in a list to
> the 'if' template tag. The diff is attached to ticket 8087, complete
> with unit tests and documentation.
>
> Could a committer take a look at this change, and a
On Aug 3, 2009, at 6:53 PM, Malcolm Tredinnick wrote:
>
> On Mon, 2009-08-03 at 15:48 +0400, Ivan Sagalaev wrote:
>> Hello!
>>
>> A couple of days ago a sudden thought has struck me while thinking on
>> the matter of logging in Python libraries. I consider a good practice
>> for a library to log
Hi all
A while ago, I added support for testing if an element is in a list to
the 'if' template tag. The diff is attached to ticket 8087, complete
with unit tests and documentation.
Could a committer take a look at this change, and advise me what
additional work/changes would be required in orde
On Aug 3, 3:53 am, chairface wrote:
> Also, it is only a single video, but that video
> is a pretty good resource for the topic of Django's future. It was
> the topic of the entire hour. Are you implying that it's a poor
> source for people wondering where Django is going? It was explicitly
>
> I have a patch I've been holding over for 1.2 that reduces the current
> > debug wrapper's log method to a ring buffer to avoid the accidental
> > massive memory usage case.
>
> Actually this is not the main issue... I saw the discussion about
> limiting the buffer. My main concern is that loggin
Malcolm Tredinnick wrote:
> Adrian, in particular, has been historically against adding logger
> module hooks in Django. So you have to work around that.
Interesting... Adrian, can you elaborate?
> I have a patch I've been holding over for 1.2 that reduces the current
> debug wrapper's log metho
Russell Keith-Magee wrote:
> For the record, there is one notable use for the legacy behavior -
> debugging at the console. i.e., issue a query at the Python prompt,
> then print connection.queries[-1] to see what was executed.
Yes, and we can keep it. As I said a simple custom log handler can do
17 matches
Mail list logo
