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 no
On Wed, Aug 12, 2009 at 8:03 AM, Russell Keith-Magee wrote:
>
> On Wed, Aug 12, 2009 at 9:45 AM, SmileyChris wrote:
> >
> > http://code.djangoproject.com/ticket/11461
> >
> > DebugNodeList catches all exceptions, sticks them in a
> > TemplateSyntaxError, and stuffs the original exception in the n
Please don't crosspost to both django-users and django-developers. Pick the
right list and post there, in this case -users.
Karen
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to
Please don't crosspost to both django-users and django-developers. Pick the
right list (in this case -users) and post there.
Karen
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post t
On Sun, Sep 6, 2009 at 12:16 AM, vegas wrote:
>
> Hi guys,
>
> I was just doing some work, and I noticed that passing args and kwargs
> to reverse raises an exception which explicitly tells me not to do
> that:
>if args and kwargs:
>raise ValueError("Don't mix *args and **kwar
On Fri, Sep 11, 2009 at 9:40 AM, drozzy wrote:
>
> Just dug up a 2year old ticket on this:
> http://code.djangoproject.com/ticket/2891
>
> Can some core-developer modify the trunk or merge it in?
> SmileyChris's patch looks good:
>
> http://code.djangoproject.com/attachment/ticket/2891/2891-backw
On Fri, Sep 11, 2009 at 9:29 AM, Jerome Leclanche wrote:
>
> Could someone give some feedback on #11521?
> (http://code.djangoproject.com/ticket/11521)
> It's been sitting for almost 3 months without any kind of answer. The
> current patch is a 2-line change which looks very reasonable, but I'd
>
On Fri, Sep 11, 2009 at 10:06 AM, Jerome Leclanche wrote:
>
> On Fri, Sep 11, 2009 at 5:03 PM, Karen Tracey wrote:
> > Mentioning in the description that the fix may be a hack might not have
> been
> > the best idea.
>
> It's not "may", it's "
On Wed, Sep 16, 2009 at 9:11 AM, Vladimir Prudnikov wrote:
> Hello,The default behaviour for saving object is very hard for big models,
> especially if it contain TextField. For example if I change one small field
> in a model and that run save() method it will generate UPDATE query for all
> of t
On Mon, Sep 21, 2009 at 10:53 AM, Léon Dignòn wrote:
>
> Hello,
>
> today I browsed to the group django-developers in Google Groups. The
> navigation bar with the adverts, which is normally on the right side,
> covers all the discussion topics on the left. The layout is broken,
> but only in this
On Wed, Sep 23, 2009 at 4:59 PM, David Cramer wrote:
>
> I haven't brought this up for quite a while, but ``to_field`` still
> does not function properly (at least as of 1.1, I haven't noticed any
> changes addressing it though). The issue is that anywhere you do a GET
> lookup, it doesn't proces
On Tue, Oct 6, 2009 at 1:24 PM, Marcob wrote:
>
> I saw these tickets:
>
> http://code.djangoproject.com/ticket/9484 (closed: duplicate)
> Admin, raw_id_fields, not int value
> Msg: #8746 covers this.
>
> http://code.djangoproject.com/ticket/8746 (closed: fixed)
> Data entered in raw_id_fields ne
On Sat, Oct 10, 2009 at 8:21 PM, Russell Keith-Magee wrote:
> One thought that has occurred to me is that rather than using msg as
> the complete literal error string, we could use it as a prefix to the
> literal.
>
> i.e., to take line 124 that you used as an example:
>
> > def assertFormError(s
On Sun, Oct 11, 2009 at 7:07 PM, Wolf.Halton wrote:
>
> Ticket #10050 (closed: fixed)
>
> Opened 9 months ago
>
> Last modified 3 minutes ago
> Documentation bug in tutorial / admin manual? 'AdminSite' object has
> no attribute 'urls'
>
> Here is what I need to ask. What trivial issue did I miss
I don't know who maintains or has access to the buildbot machine, but I can
confirm the failure is due to leftover .pyc files. I saw the same thing on
my own machine until I deleted all the .pyc files in the tree. Then it ran
clean.
Karen
--~--~-~--~~~---~--~~
Yo
On Fri, Nov 20, 2009 at 1:14 AM, Alex Gaynor wrote:
> Hey all,
>
> Russ and I have been working on getting the multi-db work ready for
> merge (final stretch here hopefully!), and I just ported the Oracle
> backend to the slightly updated backend arcitecture so it could use
> some testers. If yo
>
> Just running the Oracle tests is enough for now. I've fixed the error
> you spotted with the stray import left over and pushed that to github.
>
I get 6 failures and 26 errors but I do not know if any of them have
anything to do with multidb. The output is here:
http://pastebin.com/m2c76367
Note Oracle had the same problem:
http://code.djangoproject.com/ticket/5087
I can't actually read Oracle but I think the fix involves adding a cast that
extracts the first 4000 chars of data from the field for comparison. They
override the field_cast_sql method in the Oracle DatabaseOperations t
On Tue, Nov 24, 2009 at 7:09 PM, Russell Keith-Magee wrote:
> This is a slightly moot point, though; Django defines the admin log
> object_id using a TextField, and changing this would be a big
> backwards incompatibility.
>
>
Also I believe there's at least one other place in Django that does si
I slightly prefer class-based configuration.
Karen
--
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 group, send email to
django-developers+un
I think ticket #399 could make it into 1.2, but there's a -1 vote (from
James) to overcome first: Patch on the ticket (which is over a year old)
indicates how easy this is to do yourself if you need it.
The patch is no longer a year old, it's been updated a few times recently,
fixing tests to get
2009/12/10 Tomáš Kopeček
>
> We've fixed all issues (like incomplete tests and few bugfixes), so
> patch is now ready to be included into trunk.
>
> I partially agree with -1 vote. It is easy. What is against: Included in
> trunk we address all backends (and it looks to be easy to maintain them)
On Tue, Dec 15, 2009 at 7:33 PM, Dave Peck wrote:
> Hello,
>
> I notice that Django's multipart form parser expects CRLF-style line
> endings. Specifically,
> django.http.multipartparser::parse_boudary_stream has a hardcoded
> expectation of '\r\n\r\n' to end a part header.
>
> Is this line endin
I've uploaded what I think is a commit-ready patch for adding
BigIntegerField. Barring any major objections I'd like to commit this in
the next day or two.
Karen
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send
On Fri, Dec 18, 2009 at 5:44 PM, Ian Kelly wrote:
> We just changed our test database to Oracle 11gR2 and discovered that
> the unicode test case in the basic test is now failing. This may just
> be something wrong with our installation, because we're seeing the
> same problem performing the sam
On Mon, Dec 21, 2009 at 11:12 AM, Tobias McNulty wrote:
> http://code.djangoproject.com/ticket/11843
>
> This is a simple fix to a rather bothersome problem; if you need to do
> anything with those hidden inputs in JavaScript there's no way to uniquely
> identify them without extending the widget
>
> (1)
> http://code.djangoproject.com/attachment/ticket/12403/syndication-views-4.diff(Why
> aren't my diffs showing? Are they too large for trac?)
>
>
It's likely the six of these:
\ No newline at end of file
in the diff.
Karen
--
You received this message because you are subscribed to the
I'm listed as one of the interested committers on GSoC-6 (test
improvements). Unfortunately I have not had time to devote to moving that
along, and so far as I know nobody else has either -- I have not seen any
activity or patches or discussion that would indicate anyone was hoping to
get something
On Tue, Jan 5, 2010 at 11:53 AM, Elias Torres wrote:
>
> I'm not a security expert by any means, but I really the fact that
> you're making use of HMACs in your design.
>
There seems to be a key word missing here: really the fact...
(One might guess based on the rest of the message, but still
On Wed, Jan 6, 2010 at 12:16 PM, Jeremy Dunck wrote:
> On Wed, Jan 6, 2010 at 10:24 AM, Amit Upadhyay wrote:
> > http://docs.djangoproject.com/en/dev/ref/templates/api/#loader-types, I
> > looked and could not find "cached.py"
> > in Django-1.1.1/django/template/loaders.
>
> There is a section f
On Fri, Jan 8, 2010 at 1:42 PM, Rebekah wrote:
> I've searched but don't seem to see anyone else experiencing this
> issue. I think it must be a django bug, I just want to know is this a
> known issue, and if so, if there is a patch already in the works.
>
> I have a view which displays a form a
On Sat, Jan 9, 2010 at 8:52 AM, Waldemar Kornewald wrote:
> Hi,
> the model validation layer checks for uniqueness of the primary_key
> (in base.py: _perform_unique_checks()). But what if the pk value is
> None (indicating for an AutoField that it should get an id from the
> DB)?
>
> Currently, it
On Sat, Jan 9, 2010 at 2:24 PM, aditya wrote:
> From what I can see, the following ticket:
>
> http://code.djangoproject.com/ticket/4092
>
> is addressing the same issue as this ticket:
>
> http://code.djangoproject.com/ticket/10969
>
>
> Ticket #10969 is closed, but ticket #4092 is still marked
On Wed, Jan 13, 2010 at 4:21 AM, Hanne Moa wrote:
> 2010/1/13 Tobias McNulty :
> > I am by no means an expert on the matter, but I remember seeing a comment
> > awhile back suggesting that it generally makes more sense to fix the 2to3
> > script than to maintain two branches of the same library.
On Thu, Jan 14, 2010 at 10:50 AM, Pablo López wrote:
> I *did* search in this group... not in others :-)
>
>
Note django-users is the more appropriate group for this question.
Questions about using Django should go to django-users, django-developers if
for discussions focused on developing Django
On Thu, Jan 14, 2010 at 11:07 AM, Pablo López wrote:
> I know, but it looked a django bug, that is why I posted here, because
> I think it makes more sense discussing about _potential_ django bugs
> with their developers than doing it with their users. I'll search
> better for next time.
>
>
Note
On Thu, Jan 14, 2010 at 2:17 PM, Marty Alchin wrote:
> 2010/1/14 Łukasz Rekucki :
> > It is possible to write 3.x code that is backwards-compatible with
> > python 2.6+. There are some rough edges like, names of stdlib modules,
> > instance checks for strings and some introspection details. In my
On Wed, Jan 27, 2010 at 12:17 PM, Alex Gaynor wrote:
> I'm almost positive this is a dupe of another ticket, in the 3000-6000
> range I think.
>
The one I found was #901.
Karen
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to
Please direct questions about using Django to the django-users list.
django-developers is for discussion of developing Django itself.
Karen
--
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
Please ask questions about use of django on the django-users list.
django-developers is for discussion of developing Django itself.
Karen
--
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..
Please post questions about using Django to django-users. django-developers
is for discussion of developing Django itself.
Karen
--
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...@google
On Sun, Jan 31, 2010 at 1:59 AM, Suno Ano wrote:
> I see, I have not been aware any such discussion took place plus,
> searching through the mail archives, issue tracker and wiki, there had
> also been no sign of any such discussions/work in this regard. I just
> wanted to know the status on HTML
Please post questions about using Django to django-users. This list is for
discussion of developing Django itself.
Karen
--
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.c
And now I see you posted there a couple of minutes before posting here.
Please don't do that either. Choose the right list and post once.
Karen
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-de
On Wed, Feb 3, 2010 at 3:21 PM, kanu wrote:
> Hi,
>
> My Ticket http://code.djangoproject.com/ticket/12760 Titled : "related
> models with Foreignkey.null=True must not get deleted on delete of
> their relation" was marked as dublicate today.
>
> I don't aggree that this is a dublicate. i filed t
Is starting the deprecation process for something a feature or a bug? If
feature, we should start the process for the psycopg1 backend (discussed
here:
http://groups.google.com/group/django-developers/browse_thread/thread/ac7874cac8ece97)
before Thursday. Near as I can tell it hasn't been marked pe
On Fri, Feb 5, 2010 at 7:03 PM, FeatherDark wrote:
> Good? :)
> Just trying to help.
> The errors sure felt real enough, I hope no one else has this problem.
>
Alex did not say the errors were not real, he said he doubted the problem is
the fault of Django and was probably more likely a bug in t
On Mon, Feb 8, 2010 at 5:31 PM, Luc Saffre wrote:
> [snip]
Okay, it's obvious that Luke's and Luc's understandings of that problem
> are quite different. We both explained our points of views. The next
> step would be to hear other people's opinions.
>
I agree with Luke. I'm also puzzled by you
On Mon, Feb 8, 2010 at 8:44 AM, Luke Plant wrote:
> What do people think?
>
Ugh. Assuming no one can come up with a brilliant fix so that the auto_adapt
stuff can work when combined with arbitrary other decorators (I can't), I
favor switching to a system that requires different decorators for me
On Mon, Feb 8, 2010 at 6:39 PM, Vitaly Babiy wrote:
> Hey Guys,
> So 1.2 is almost out the door so I wanted to raise an issue that I would
> love to start working to fix for 1.3.
>
Not to discourage you, but be aware the focus of most attention until 1.2
actually goes out is still 1.2. Feature f
On Tue, Feb 9, 2010 at 3:02 AM, Luc Saffre wrote:
> "Closed" as "Invalid", as I understand it, means that this ticket is not
> worth to get more consideration and that further comments are not welcome.
>
> "Open" with a triage stage of "Someday/Maybe" would help people who
> stumble on this behav
On Wed, Feb 10, 2010 at 2:22 AM, Russell Keith-Magee wrote:
> It certainly doesn't look right; .exists() should be faster than
> .count(), and having all the extra columns in the query looks a little
> weird.
>
> However, to say for sure, we need a few more details:
>
> * Does this only happen w
On Fri, Feb 12, 2010 at 10:25 PM, Gleber wrote:
> I don't know if this is a bug.
If you are not sure it is a bug, the right place to ask is django-users, not
here. See:
http://docs.djangoproject.com/en/dev/internals/contributing/#id1
Karen
--
You received this message because you are subsc
This list is for discussion of the development of Django itself. Please ask
usage questions on django-users.
Karen
--
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
On Mon, Feb 15, 2010 at 9:08 PM, Gary Reynolds
wrote:
> There is already a ticket for this (and possibly others).
>
> http://code.djangoproject.com/ticket/11244#comment:4
>
> It has been closed and marked wontfix, see the comments for why.
I believe the request here is to reconsider that wontfix
2010/2/17 Václav Řehák
> the changeset 10693 fixing #11030 (File uploads break on non english
> filesystem encoding) introduced a problem with non english filenames
> in my setup (Windows XP or 2003, Python2.6, Apache). If I upload a
> file with czech characters (e.g. čeština.txt - the first char
Please ask question related to using Django on django-users, not here. This
list is for discussion of development of Django itself.
Karen
--
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.
Please ask usage questions on django-users, not here. This list is for
discussion of developing Django itself.
Karen
--
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.
T
On Thu, Feb 25, 2010 at 3:05 PM, SmileyChris wrote:
>
> But I do think it's critical to see a new 1.1 release before 1.2 is
> out - if for no other reason than having {% csrf_token %} in a 1.1
> official release.
>
>
Before 1.2 is out or at the same time as 1.2 goes out? We normally do a
final m
On Mon, Mar 1, 2010 at 6:59 AM, George Karpenkov wrote:
> Thanks for the reply.
>
> If it wouldn't take too much time, can you please point me to those
> discussions?
>
>
This ticket is one I recall:
http://code.djangoproject.com/ticket/10768
Karen
--
You received this message because you are
On Mon, Mar 1, 2010 at 9:47 AM, Luca Sbardella wrote:
> Hi there,
>
> I just switch from 1.2 beta 1 to svn version and the
> ModelAdmin.response_action is not working as before
Yes, this has been reported at least twice in the tracker (see
http://code.djangoproject.com/ticket/12962) and at least
Please send questions about using Django to django-users. This list is for
discussions about developing Django itself.
Karen
--
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...@googlegrou
Please ask questions about using Django on django-users. This list is
for discussion of the development of Django itself.
Karen
--
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...@googlegro
PLEASE direct questions about using Django to the django-users list. Usage
questions are not on-topic for the django-developers list.
Karen
--
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
On Wed, Mar 3, 2010 at 12:33 PM, Jared Forsyth wrote:
> As a general "best practices" question: When I update a ticket w/ a test
> case and better patch, do I uncheck 'needs better patch' and 'needs
> testcases'? Or do I leave that to the person who originally checked them?
>
If you believe you h
This question is off-topic for the django-developers list, which is a list
about developing Django itself. Please ask questions about using Django on
django-users.
Karen
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group,
On Fri, Mar 5, 2010 at 11:35 AM, stherrien wrote:
> What I'm suggesting is that we setup something to allow everyone to
> improve the docs with help from the core django group. I think this
> would be very helpful to everyone. if one of the core group would like
> to help us get setup to do this
On Fri, Mar 5, 2010 at 11:40 AM, Karen Tracey wrote:
> ... open a ticket and attach the patch.
>
>
And, as for all other tickets, it'll help if you search the tracker first
and make sure that whatever ticket you're planning on opening isn't already
open.
Karen
--
Y
Please ask questions about using Django on django-users. The topic of this
list is development of Django itself.
Karen
--
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.
Questions about using Django should be sent to django-users. The topic of
this list is the development of Django itself.
Karen
--
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...@googlegrou
Please don't crosspost to both django-users and django-developers. Pick the
right list and post once. This sounds like a usage question, so it belongs
on django-users.
Karen
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this g
On Fri, Mar 19, 2010 at 10:47 AM, Jacob Kaplan-Moss wrote:
> On Fri, Mar 19, 2010 at 7:39 AM, Sh4wn wrote:
> > I want to refactor the QuerySet and other databases related API's,
> > which adds an additional method of selecting records, and provides
> > more control of what data you'll select, but
On Mon, Mar 22, 2010 at 12:00 AM, Marcob wrote:
> Please, does anybody know which patch I need to apply to 1.1.1 to fix
> this strange problem?
> Obviously (and unfortunately) I can't install 1.1.2 Alpha.
>
(A question like this more properly belongs on django-users.)
While I can recreate your
On Mon, Mar 22, 2010 at 4:07 AM, Raffaele Salmaso <
raffaele.salm...@gmail.com> wrote:
> Marcob wrote:
> > Please, does anybody know which patch I need to apply to 1.1.1 to fix
> > this strange problem?
> http://code.djangoproject.com/changeset/12807 ?
>
>
No, turns out it was a change made farthe
The topic of this list is discussion of the development of Django itself.
Please ask questions about using Django on django-users.
Karen
--
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...
On Mon, Apr 5, 2010 at 10:35 AM, Dennis Kaarsemaker
wrote:
> Not a criticism per se, but I am wondering why the next 1.1.x is
> released alongside 1.2 instead of as a release on its own. I've yet
> again seen a case of python 2.6.5 breaking django tests, so I would
> welcome a new release of 1.1.x
On Sun, Apr 11, 2010 at 11:10 PM, Russell Keith-Magee <
freakboy3...@gmail.com> wrote:
> On Mon, Apr 12, 2010 at 10:15 AM, orokusaki
> wrote:
>
> >
> > The only idea I have for a solution is:
> >
> >class Meta:
> >unique_together = (('account', 'name', 'You already have a
> > Widget w
Questions about using Django should be sent to django-users, not here. The
topic of this list is the development of Django itself.
Karen
--
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...
This question should be posted to django-users, not here. The topic of this
list is the development of Django itself.
Karen
--
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...@googlegroup
On Fri, Apr 16, 2010 at 11:00 PM, Tom X. Tobin wrote:
> [snip details of run times]
>
> Sticking out like a sore thumb is API_TESTS under
> modeltests.fixtures.models.__test__, which clocks in at 1090
> seconds(!). The serializer tests also seem to take a pretty chunk of
> time at about 1-3 minut
Please direct questions about using Django to the django-users mailing list.
The topic of this list is the development of Django itself.
Karen
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-deve
On Mon, Apr 19, 2010 at 10:26 AM, Shawn Milochik wrote:
> So, I'm asking for anyone in the core (or close to it) to specifically
> point out any low-hanging fruit.
Off the top of my head, a ticket I saw some activity on recently but have
not had time to look into making a test/fix for:
http://
On Tue, Apr 20, 2010 at 3:44 PM, Anssi Kaariainen wrote:
> I am trying to run some doc tests, but can't figure out how.
> Specifically I would like to run the doc tests in regressiontests/
> forms/widgets.py.
>
> Running "./runtests.py --settings=test_sqlite forms" from the tests
> directory it ru
On Tue, Apr 20, 2010 at 5:03 PM, Alex Gaynor wrote:
>
> Do you have any idea how that caused the fail, it should be completely
> innocuous?
>
>
I'm guessing it's got something to do with the ... at the beginning of the
line making it appear to be a shell continuation line, not ellipsis for
output
The topic of this list is the development of Django itself: questions about
how to use Django should be directed to django-users.
Karen
--
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...@
On Thu, Apr 29, 2010 at 11:57 AM, xRobot wrote:
>
> How can I do that ?
>
"How can I?" type questions should be sent to django-users. This list is
for the discussion of the development of Django itself.
Karen
--
You received this message because you are subscribed to the Google Groups
"Djang
On Wed, May 5, 2010 at 12:46 PM, Kevin Howerton wrote:
> What I was suggesting in my post though, was that we alter the default
> CRITICAL error handling behavior ... as it stands (by default) all of
> my ERRORs are being suppressed in production. This is pretty
> confusing for new users (there w
On Tue, May 18, 2010 at 12:45 AM, SmileyChris wrote:
> Can't investigate too much more until tomorrow, but it's a pretty big
> regression so I thought I'd bring it up here for discussion as well as
> starting a ticket.
>
> http://code.djangoproject.com/ticket/13556
>
I cannot recreate given the
On Fri, May 21, 2010 at 8:38 AM, tiemonster wrote:
> Is there a reason that the default ordering on the User model is by
> pk? Would it be a reasonable request to ask that the default ordering
> for this model be username? I have several models that have a m2m to
> the User model, and it's very h
On Fri, May 21, 2010 at 8:46 AM, Jeremy Dunck wrote:
> Even so, you could create a custom ModelAdmin for User, specifying the
> ordering option:
>
> http://docs.djangoproject.com/en/1.2/ref/contrib/admin/#django.contrib.admin.ModelAdmin.ordering
>
>
The default model admin for the User model alre
Please send questions about using Django to django-users. The topic of this
list is the development of Django itself.
Karen
--
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
On Mon, May 24, 2010 at 3:39 PM, Raffaele Salmaso <
raffaele.salm...@gmail.com> wrote:
>
> but when the releases/1.2.X branch will be created?
When it's needed. That is, when we get to the point of wanting to check in
features for 1.3 that should not go into the next 1.2.X release. Until we
get
I've noticed a lot of people lately updating the trac version field of to be
more recent. For example changing version from 1.0 to 1.2 or 1.1 to SVN. I
thought this field was supposed to track the version against which a problem
was written -- that is, the version of code in use by the reporter of
Please ask questions related to using Django on django-users. The topic of
this list is the development of Django itself.
Karen
--
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...@googlegr
Please do not crosspost questions to both django-developers and
django-users: pick the right list and send the question there. Questions
about using Django, such as this one, belong on django-users.
Karen
--
You received this message because you are subscribed to the Google Groups
"Django devel
On Mon, Jun 14, 2010 at 1:59 PM, Hooshyar wrote:
> I am new to this group, although I am 4 years old with Django. I have
> a question. If this is not the right place, I apologize in advance.
> Please refer me to a proper mailing list. Please reply here or you can
> e-mail me directly, if you wish
On Mon, Jun 14, 2010 at 12:39 PM, Peter Bengtsson wrote:
> I'm happy to submit a ticket but wanted to check first that I'm doing
> the right thing. I think this used to work in Django 1.1 but not now
> in trunk.
>
> I can better explain it with code:
>
> [snip details]
> The point of this is that
On Tue, Jun 15, 2010 at 10:46 AM, Arthur Koziel wrote:
> 4. Also in the same changeset, the 'nesting_level' and 'can_postpone'
> variables were introduced. These fixed a problem where the package is still
> being imported by Python and the model module isn't available yet. Again, I
> couldn't repr
On Mon, Jun 21, 2010 at 4:37 AM, Massimiliano della Rovere <
massimiliano.dellarov...@gmail.com> wrote:
> Anyway, my idea is the following:
> reference fields shown in the change list page (not change view) shown
> as links to the edit page of the instance.
> I tried to implement this on my own, s
Please send questions about how to use Django to django-users. The topic of
this list is the development of Django itself.
Karen
--
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...@googleg
1 - 100 of 464 matches
Mail list logo
