On Tue, Aug 11, 2009 at 11:06 PM, Russell
Keith-Magee wrote:
>
> On Wed, Aug 12, 2009 at 10:55 AM, David wrote:
>>
>>
>>
>> On Aug 11, 10:29 pm, Russell Keith-Magee
>> wrote:
>>
>>> There are any number of ways to solve this
On Aug 12, 12:06 am, Russell Keith-Magee
wrote:
> Another cause for hesitation is that it would be an admin-specific
> solution to the problem. A generic solution that would work for all
> ModelForms would be nice if it is possible.
Agreed. I shall look at that first
On Wed, Aug 12, 2009 at 10:55 AM, David wrote:
>
>
>
> On Aug 11, 10:29 pm, Russell Keith-Magee
> wrote:
>
>> There are any number of ways to solve this problem by adding a field
>> to the model (autofield with an 'edit number', timestamp tracking
For those, like me, wondering what this proposal was about, it's
concerning changing sorting in the admin interface to initially use the
full set of fields specified in Meta.ordering on the model.
What I can't work out yet, due to difficulty in reviewing the patch,
mentioned below, is whether it
On Tue, 2009-08-11 at 04:39 -0700, Ole Laursen wrote:
> Hi!
>
> There are a couple of bugs open/closed about what happens when you
> upload a new file to a file field that already has a file:
>
> http://code.djangoproject.com/ticket/11663
> http://code.djangoproject.com/ticket/2983
>
On Tue, 2009-08-11 at 10:21 -0700, Richard Davies wrote:
> > I don't agree the current savepoint use within Django is inconsistent. As
> > far as I can tell, savepoints are used internally in the one case where
> > Django itself catches and suppresses an IntegrityError.
> ...
> > Right now it is
On Aug 11, 10:29 pm, Russell Keith-Magee
wrote:
> There are any number of ways to solve this problem by adding a field
> to the model (autofield with an 'edit number', timestamp tracking last
> edit time etc). However, these aren't really candidates for a general
>
On Wed, Aug 12, 2009 at 9:24 AM, David wrote:
>
> After being unable to get any advice or further information via
> google, #django or the users' mailing list, I opened
> http://code.djangoproject.com/ticket/11652 regarding the admin
> interface not preventing simultaneous
http://code.djangoproject.com/ticket/11461
DebugNodeList catches all exceptions, sticks them in a
TemplateSyntaxError, and stuffs the original exception in the new
exception. I'm not sure why this is done, but it breaks debugging and
exception handling.
What is the advantage of swallowing the
On Wed, Aug 12, 2009 at 9:02 AM, Jerome Leclanche wrote:
> Might be slightly off-topic, but, if that's the main criterion, are we ever
> going to include django-tagging in contrib?
"Ever" is a very long time. I wouldn't be surprised if _eventually_
django-tagging is added to
After being unable to get any advice or further information via
google, #django or the users' mailing list, I opened
http://code.djangoproject.com/ticket/11652 regarding the admin
interface not preventing simultaneous editing of the same record (or
at least not providing that as an option). I
Might be slightly off-topic, but, if that's the main criterion, are we ever
going to include django-tagging in contrib?
J. Leclanche / Adys
On Wed, Aug 12, 2009 at 3:20 AM, Russell Keith-Magee wrote:
>
> Regardless of my opinion, this is a feature that can happily live
I would like to see the code for this. I have been waiting for something like
it.
TIA
-- Sent from my Palm Pre
Mark Ferrer wrote:
Hi everyone,
This is my first time here, and I've been holding on to some code for a custom
model field type for a little while now. I call it a DictionaryField
On Wed, Aug 12, 2009 at 3:11 AM, Mark Ferrer wrote:
> Hi everyone,
> This is my first time here, and I've been holding on to some code for a
> custom model field type for a little while now. I call it a DictionaryField
> and it takes a Python dictionary object and stores it in
On Wed, Aug 12, 2009 at 2:56 AM, mitch wrote:
>
> As a heavy SimpleDB user, I would love to see a way to use Django and
> SimpleDB together and I would certainly be willing to devote time to
> helping make that happen. I think I can contribute on the SimpleDB
> side
On Wed, Aug 12, 2009 at 1:49 AM, Waldemar Kornewald wrote:
>
> On Aug 11, 10:01 am, Malcolm Tredinnick
> wrote:
>> On Tue, 2009-08-11 at 00:03 -0700, Waldemar Kornewald wrote:
>> > And these are just the first few issues we've run into when
On Tue, Aug 11, 2009 at 11:58 PM, Mark Ferrer wrote:
>
> You're right. I forgot about JSON. I guess it can be encoded and
> stored as a JSON string and then decoded afterward.
>
See django-jsonfield:
http://github.com/bradjasper/django-jsonfield/tree/master
Personally I use
You're right. I forgot about JSON. I guess it can be encoded and
stored as a JSON string and then decoded afterward.
On Aug 11, 3:19 pm, Javier Guerra wrote:
> On Tue, Aug 11, 2009 at 2:11 PM, Mark Ferrer wrote:
> > I call it a DictionaryField and it
On Tue, Aug 11, 2009 at 11:20 PM, Andrew Gwozdziewycz wrote:
>
> On Tue, Aug 11, 2009 at 10:50 AM, Richard
> Davies wrote:
>>
> I'm a fan of having more if tags, but am not a fan of having if tags that
> require me to remember all of the
On Tue, Aug 11, 2009 at 2:11 PM, Mark Ferrer wrote:
> I call it a DictionaryField and it takes a Python dictionary object and
> stores it in a database as a text field
i usually just encode it as JSON. not as dense; but more universal
syntax, so you get faster decoders in
Dear Django Project developer,
within the scope of my diploma thesis at the University of Paderborn, Germany,
with the title "Study about communication and collaboration in software
development in teams" I am conducting a survey of members of software
development teams.
I would be very
Hi everyone,
This is my first time here, and I've been holding on to some code for a
custom model field type for a little while now. I call it a DictionaryField
and it takes a Python dictionary object and stores it in a database as a
text field. The default storage format is "key1=foo;key2=bar".
As a heavy SimpleDB user, I would love to see a way to use Django and
SimpleDB together and I would certainly be willing to devote time to
helping make that happen. I think I can contribute on the SimpleDB
side (boto has supported SimpleDB for over a year and I'm very
familiar with the service)
On Tue, Aug 11, 2009 at 7:46 PM, Rock wrote:
>
> Yes. I have a project that could use this immediately. Looking forward
> to seeing the ticket and a patch I can try out.
Ok, let me know what you think.
http://code.djangoproject.com/ticket/11695
Yes. I have a project that could use this immediately. Looking forward
to seeing the ticket and a patch I can try out.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this
I just wanted to toss this out there before creating the ticket. I've
tweaked the change list sort handling so that by default it uses the
full list of sort columns defined in the model. It sets all of the
headers as unselected and then behaves as it currently does if someone
selects a header
On Aug 11, 10:01 am, Malcolm Tredinnick
wrote:
> On Tue, 2009-08-11 at 00:03 -0700, Waldemar Kornewald wrote:
> > And these are just the first few issues we've run into when analyzing
> > the source.
>
> Most of those are the kind of incremental changes that are part of
I thought one of the more recent patches to DDT made it run Jquery in
compatability mode, which should resolve these clashes, probably isn't on
all branches though.
mat
On Tue, Aug 11, 2009 at 6:09 PM, Ulrich Petri wrote:
>
>
> Am 11.08.2009 um 16:50 schrieb Alex Gaynor:
> >
> >
> I don't agree the current savepoint use within Django is inconsistent. As
> far as I can tell, savepoints are used internally in the one case where
> Django itself catches and suppresses an IntegrityError.
...
> Right now it is pretty simple: if your app code catches a database error it
>
Am 11.08.2009 um 16:50 schrieb Alex Gaynor:
>
> This is still true IMO, but there's another issue here. DDT uses
> jQuery, and AFAIK the official position is still that we aren't
> choosing a JS lib (although clearly Zain's work is rapidly moving us
> to the point where a decision has to be
On Tue, Aug 11, 2009 at 09:50:35AM -0500, Alex Gaynor wrote:
> Right now django-debug-toolbar has a pretty stable panel interface and
> I actually can't recall it changing since release. A possibly more
> interesting issue is that some of the debug information it get's is
> somewhat of a hack,
> This leads naturally to pretty scare feature creep. If we have
> startswith, why not ifendswith? ifcontains? ifdoesntcontain?
> ifcontainssomewhereinthemiddleafterthethirdcharacter?
Jacob, there is a ticket for ifin and ifnotin tags in DDN state [1].
Maybe it's time to close it in favour of
On Tue, Aug 11, 2009 at 11:24 AM, Richard Davies <
richard.dav...@elastichosts.com> wrote:
>
> Hi all,
>
> I've got two open tickets against database savepoints (#11156 and
> #9205) and think this is an area which we should take a look at for
> 1.2 - it is currently inconsistent, IMHO.
>
>
I've
On Tue, Aug 11, 2009 at 7:01 AM, Russell
Keith-Magee wrote:
> Firstly, there is the simple issue of ownership and copyright.
> Obviously, those that have written DDT components that are to be
> included need to be onboard with this idea.
On this point I've strived to be
On Tue, Aug 11, 2009 at 10:32 AM, Andrey Fedorov wrote:
> Sorry, new to the group - is there an easy way to search old threads? Google
> keeps pointing me to the docs...
It's in the footer that Google adds to every message:
> For more options, visit this group at
>
>
> This has been discussed ad nauseam in the past, and has been rejected
> repeatedly.
>
Sorry, new to the group - is there an easy way to search old threads? Google
keeps pointing me to the docs...
- Andrey
On Tue, Aug 11, 2009 at 11:20 AM, Andrew Gwozdziewycz wrote:
>
> On
On Tue, Aug 11, 2009 at 9:50 AM, Richard
Davies wrote:
> With 1.1 out of the door (great!), here's a thought for 1.2...
Actually, it's about six thoughts. I'll give you my quick thoughts
below, but if you're serious about discussing this stuff you'll want
to have
Hi all,
I've got two open tickets against database savepoints (#11156 and
#9205) and think this is an area which we should take a look at for
1.2 - it is currently inconsistent, IMHO.
Savepoints are described here:
http://docs.djangoproject.com/en/dev/topics/db/transactions/#savepoints
There
On Tue, Aug 11, 2009 at 10:50 AM, Richard
Davies wrote:
>
> Hi all,
>
> With 1.1 out of the door (great!), here's a thought for 1.2...
>
> I often end up writing the same couple of template tags and filters. I
> think some of these are general enough and useful
>
> Filter: get
>
+1, I've also written this filter (lambda d, v: d.get(v, None)). Would be
nice to have it standard.
No opinions on the others.
- Andrey
On Tue, Aug 11, 2009 at 10:50 AM, Richard Davies <
richard.dav...@elastichosts.com> wrote:
>
> Hi all,
>
> With 1.1 out of the door
Hi all,
With 1.1 out of the door (great!), here's a thought for 1.2...
I often end up writing the same couple of template tags and filters. I
think some of these are general enough and useful enough that they
should be considered for basic Django 1.2, even though they're fairly
easy to write as
On Tue, Aug 11, 2009 at 9:01 AM, Russell
Keith-Magee wrote:
>
> On Tue, Aug 11, 2009 at 8:32 PM, Mat Clayton wrote:
>> Hey all,
>>
>> For us of the most useful developments in the django community recently has
>> been the django debug toolbar.
>>
>>
On Tue, Aug 11, 2009 at 8:32 PM, Mat Clayton wrote:
> Hey all,
>
> For us of the most useful developments in the django community recently has
> been the django debug toolbar.
>
> http://github.com/robhudson/django-debug-toolbar/tree/master/debug_toolbar
>
> This seems to be
Hey all,
For us of the most useful developments in the django community recently has
been the django debug toolbar.
http://github.com/robhudson/django-debug-toolbar/tree/master/debug_toolbar
This seems to be branching and growing very rapidly on github, however lots
of branches are appearing
There is another work on this, apart from
http://code.google.com/p/app-engine-patch/
, which is at http://code.google.com/p/google-app-engine-django/
Regards,
On Aug 10, 12:19 pm, Waldemar Kornewald wrote:
> Hi,
> now that 1.1 is out we can finally discuss App Engine
Hi!
There are a couple of bugs open/closed about what happens when you
upload a new file to a file field that already has a file:
http://code.djangoproject.com/ticket/11663
http://code.djangoproject.com/ticket/2983
http://code.djangoproject.com/ticket/4339
Progress is currently halted
Thanks for clearing this up for me. I just "remembered" (or imagined ...
or dreamed) that the 1.0 documentation label came pretty quick after the
initial release, so I assumed that was the preferred way.
Marc
Malcolm Tredinnick wrote:
> On Tue, 2009-08-11 at 10:45 +0200, Marc Remolt wrote:
>
On Tue, 2009-08-11 at 10:45 +0200, Marc Remolt wrote:
> Hi,
>
> browsing the online docs, I stumbled over two minor issues:
>
> The online documentation under http://docs.djangoproject.com/en/ still
> redirects to http://docs.djangoproject.com/en/dev/, which should be
> .../1.1/ I suppose.
Hi,
browsing the online docs, I stumbled over two minor issues:
The online documentation under http://docs.djangoproject.com/en/ still
redirects to http://docs.djangoproject.com/en/dev/, which should be
.../1.1/ I suppose. The index page also still tells "This document is
for Django's SVN
> This is what CSS is for. If you look at the rendered HTML for the
> label on a required field, it already has a 'required' class - for
> example:
>
> Title:
>
> By default, the admin makes required fields bold; if you want to apply
> a trailing asterisk, you should be able to use the 'content'
On Tue, 2009-08-11 at 00:03 -0700, Waldemar Kornewald wrote:
> Hi,
>
> On Aug 11, 1:55 am, Russell Keith-Magee
> wrote:
> > > In conclusion, no on is currently working on, but for all the people
> > > who seem to ask for this I've seen almost no code written, which
> > >
Hi,
On Aug 11, 1:55 am, Russell Keith-Magee
wrote:
> > In conclusion, no on is currently working on, but for all the people
> > who seem to ask for this I've seen almost no code written, which
> > suprises me since this is something that can exist 100% external to
> >
52 matches
Mail list logo