On 10/7/06, Mario Cintra <[EMAIL PROTECTED]> wrote:
>
> Dear Friends,
>
> i have just tried to subscribe in to the mailing list and i'm not sure
> if there's any authorization needed to become a member and so post
> messages.
No authorisation required - all are welcome!
> Since i'm already writ
On 10/11/06, Gábor Farkas <[EMAIL PROTECTED]> wrote:
>
> Michael Radziej wrote:
> hmm.. maybe i am only implementing strange web-applications, but up to
> now, i never ever needed the caching behaviour of the QuerySets...so i
> probably will have to ALWAYS use the iterator() method.
>
>
> (just fo
On 10/11/06, Aidas Bendoraitis <[EMAIL PROTECTED]> wrote:
>
> I think, you should be able to do that with the method extra() at the moment:
> http://www.djangoproject.com/documentation/db_api/#extra-select-none-where-none-params-none-tables-none
>
> Anyway I am +1 for this proposal, as it would ma
On 10/11/06, Gábor Farkas <[EMAIL PROTECTED]> wrote:
>
> Russell Keith-Magee wrote:
> sorry, but is this the description of the __iter__ case, or the
> iterator() case?
Now that you mention it (looks furiously at code...)
Ok - it doesn't work quite like I thought it
Hi All,
I've hit upon an interesting bug, which is related to ticket 2737
(currently listed as a feature request, but I think there is an
argument that the requested feature is required as a bug fix).
Consider the following model:
class Poll(models.Model):
name = models.CharField(maxlength=1
On 10/12/06, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote:
> I agree the second two cases are bugs. I'm probably -0 on making
> exact=None be the same as isnull=True, because it's a synonym for
> something you can already do (we already have isnull). Still, I guess
> it's a harmless change (which
On 10/12/06, Michael Radziej <[EMAIL PROTECTED]> wrote:
>
> Russell Keith-Magee schrieb:
> > Ticket 2737 requests a feature where __exact=None would be interpreted
> > as __isnull=True. This would fix all three problems I have described.
> > The proposed patch isn&
On 10/12/06, Michael Radziej <[EMAIL PROTECTED]> wrote:
>
> Russell Keith-Magee:
> > Sorry - I'm confused; Are you agreeing with the proposed change, or
> > saying it contradicts your expectations? (I think you are agreeing - I
> > just want to make sure)
&
On 10/14/06, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote:
>
> Hey Russell,
>
> On Sat, 2006-10-14 at 10:54 +0800, Russell Keith-Magee wrote:
> > On 10/12/06, Michael Radziej <[EMAIL PROTECTED]> wrote:
> > >
> > > Russell Keith-Magee:
> &g
On 10/18/06, GinTon <[EMAIL PROTECTED]> wrote:
>
> I see that it isn't interesting for django developers so "I go away
> with the music to another part".
>
> In the first I prefer to work with another community where there is
> more support.
Don't read too much into the lack of response; the core
On 10/17/06, Michael Radziej <[EMAIL PROTECTED]> wrote:
>
> I guess this is currently under a freeze. I just wanted to bring
> it up for discussion. If there's serious interest, I can flesh it
> out (docs, testcases) later when the winter^H^H^H^H^H^H^H freeze
> is over.
You can already specify th
On 10/25/06, Aaron Torres <[EMAIL PROTECTED]> wrote:
> Is there any way we can create a similar setup for foreign keys?
Not using the existing Django code, no.
> I have
> a few ideas about how this would work, but perhaps I'm missing
> something important?
Sounds like a reasonable idea to me.
Hi all,
It appears that some little inbred turd has decided that the ticket
submission page is a great place to drop their little nuggets of
spammy goodness, and as far as I can make out Askimet isn't blocking
them.
Is there anything we can do to remove these twits from the gene pool -
or at the
On 10/25/06, Adrian Holovaty <[EMAIL PROTECTED]> wrote:
>
> On 10/24/06, Russell Keith-Magee <[EMAIL PROTECTED]> wrote:
> I've been going through and mercilessly deleting all spam tickets and
> comments, using a script I wrote that reverts changes. (I submitted i
On 10/27/06, Adrian Holovaty <[EMAIL PROTECTED]> wrote:
> It's not 100% finished. Not all the common validators are implemented,
> nor are all of the HTML form widgets. But the basic design is there.
> I'm trying to "release" early and often to get plenty of critiques
> before things get stable.
On 10/27/06, soundseeker <[EMAIL PROTECTED]> wrote:
>
> hi,
Minor note for future reference - this question should have been sent
to Django-Users, not Django-Developers. The developers list is for
discussing changes/modifications to Django itself, not 'how do I do X'
questions.
> assuming there
On 10/28/06, Jared Kuolt <[EMAIL PROTECTED]> wrote:
>
> I haven't been able to submit anything. And I like to think I
> contribute quality material!
Please don't take it personally. We value any contribution from anyone
that isn't trying to sell us viagra. Askimet is well and truly on the
fritz.
On 10/28/06, Adrian Holovaty <[EMAIL PROTECTED]> wrote:
>
> On 10/27/06, Russell Keith-Magee <[EMAIL PROTECTED]> wrote:
> Check out my latest version (which I attached to another message to
> this thread). It lets you pass a 'widget' parameter to any Field to
On 10/29/06, Blake Winton <[EMAIL PROTECTED]> wrote:
>
> > Much nicer would be to show the list of field name that can be used:
> > TypeError: Cannot resolve keyword 'storyitem' into field, choices are:
> > tags, event, admintag, storycomment, favorite, story, storyundo,
...
>
> Even nicer would b
On 11/1/06, John Hwang <[EMAIL PROTECTED]> wrote:
> mysql complains of empty IN() when manytomany field is being saved as
> blank/empty
This looks to be a variation on ticket #2473. It's a known problem,
which I believe Malcolm is working on with his refactor of the query
code.
Yours,
Russ Mage
On 11/6/06, Matthew Flanagan <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> When I try and create a Contact and save it I get the following error.
> This worked fine up until r3960 was checked in a few days ago.
Hi Matthew,
Looks like the new Date validation code I put in to get around some
SQLite probl
On 11/7/06, Gary Doades <[EMAIL PROTECTED]> wrote:
>
> I notice that the documentation is still recommending psycopg1 and not
> psycopg2 for PostgreSQL. Psycopg2 has been in release status for quite
> a while now. The psycopg site is now firmly recommending psycopg2 and
> noting that psycopg1 is e
On 11/7/06, Ramiro Morales <[EMAIL PROTECTED]> wrote:
>
> The message also contained a couple of patches to fix some
> brokeness I found in the code. I don't dare to submit a patch for a branch to
> the main Django Trac, (btw, what's the policy in this respect?) but I could
> post the patch here.
On 11/11/06, Alex Dedul <[EMAIL PROTECTED]> wrote:
>
> Hi there,
>
> Akismet rejects ticket as spam, so posting it here.
Thanks for the report, Alex.
Some changes have been made to our ticket setup to get around these
spam rejections; if you go to the settings page (link on the bottom
ri
On 11/14/06, Victor Ng <[EMAIL PROTECTED]> wrote:
>
> Is there a way to tell runtests.py to test just one module?
Yes. Pass in the app name, not the full app path. For example
(ommitting the pythonpath and settings bits):
python runtests.py basic
will run just the 'basic' modeltest;
python run
On 11/14/06, Antonio Cavedoni <[EMAIL PROTECTED]> wrote:
>
> BTW, for Russ: the testing framework is amazing, it changed completely
> how I go about designing models for my own apps. Thanks for that! I'm
> looking forward to the fixtures support.
Cheers - I'm glad I could help.
As for the fixtur
On 11/29/06, James <[EMAIL PROTECTED]> wrote:
>
>
> This bug was submitted a couple of months ago:
>
> http://code.djangoproject.com/ticket/2828
>
> but unfortunately I just got bitten by it :( Is there a fix, or will
> one be forthcoming? Or is there a workaround (the one in the ticket
> doesn't w
On 11/30/06, Brian Beck <[EMAIL PROTECTED]> wrote:
>
> Anyway, the key point is
> that anything using get_accessor_name() should take None into account,
> or None should never be returned.
The former approach would be correct. get_accessor_name() shouldn't
return a value if the m2m relation is sy
On 11/30/06, James <[EMAIL PROTECTED]> wrote:
>
> > Any help you can provide in tracking the problem (and/or fixing
> > it) would be greatfully accepted.
>
> I had a brief look at the code, and (despite my limited Python
> knowledge) was going to pitch in if I could. Given Brian's detailed
> respo
On 11/30/06, James <[EMAIL PROTECTED]> wrote:
>
>
> Brian, splendid stuff :) Seems to work so far, at least in terms of
> keeping database integrity and actually doing what it's supposed to.
> Thanks very much for taking the time to post this solution.
>
> Now how do I write a regression test? Any
On 12/2/06, Michael Patrick O'Keefe <[EMAIL PROTECTED]> wrote:
>
> SUMMARY OF PROPOSAL:
> For Django application modules, I find it easier to have the URL
> information for a view coupled with the function that is going to
> display that view. Why? This further supports the DRY (Don't Repeat
> You
On 12/4/06, Jacob Kaplan-Moss <[EMAIL PROTECTED]> wrote:
>
> I'm taking this to django-dev for more discussion; it'll get seen by more the
> right people there.
>
> Thoughts, anyone?
Ok; here's my thoughts.
1. Introduction
~~~
Consider the following pseudo-model:
class Book(Model):
On 12/6/06, Riquelme <[EMAIL PROTECTED]> wrote:
>
>
> as the title
> and is there a written code about unittest on django?
> plz share me.
This question should be directed to the users mailing list. The developers
list is for discussion of development of Django itself, not for answering
end-user
On 12/6/06, Lakin Wecker <[EMAIL PROTECTED]> wrote:
> I am also interested in helping with this situation. I've run into quite a
> few patches that are reportedly working for some people.How do we help
> get these triaged?
Yes, there are 175 active tickets with patches in the database.
How
On 12/6/06, Russell Keith-Magee <[EMAIL PROTECTED]> wrote:
>
> A well triaged patch has the following characteristics:
>
One more thing that I forgot - if the patch adds a new feature, or a
new option, there needs to be documentation of that feature (or at the
very least, a dec
On 12/6/06, limodou <[EMAIL PROTECTED]> wrote:
>
> > [1] Note that 'non-trivial' doesn't just mean 'only affects 1-2 lines
> > of code' - it also includes the fact that the lines that are being
> > modified don't have a significant follow-on effect on the overall
> > design of Django.
> >
> All ab
On 12/6/06, Sergey Kirillov <[EMAIL PROTECTED]> wrote:
>
> URL: http://code.djangoproject.com/ticket/1541
>
> Can someone integrate it into trunk?
Read the thread on the ticket - Jacob has stated what is standing
between the ticket and acceptance - documentation of the feature.
Write some docume
On 12/7/06, limodou <[EMAIL PROTECTED]> wrote:
>
> On 12/7/06, Russell Keith-Magee <[EMAIL PROTECTED]> wrote:
> >
> > On 12/6/06, limodou <[EMAIL PROTECTED]> wrote:
> > >
> > > > [1] Note that 'non-trivial' doesn't just m
On 12/8/06, Deryck Hodge <[EMAIL PROTECTED]> wrote:
>
> Hi, all.
>
> Regarding the join table that is created on ManyToMany relationships,
> there doesn't seem to be a way to override the name given to the
> table. Am I overlooking this somehow? If not, does anyone else think
> a join_table opti
First off - apologies on taking so long to get around to answering
your question - I've been doing a lot of travelling for work, and I've
been away from my Django development machine.
On 12/11/06, Matias Hermarud Fjeld <[EMAIL PROTECTED]> wrote:
> I've made a stab at writing a test for this, att
On 12/16/06, ogghead <[EMAIL PROTECTED]> wrote:
>
> Is this a fair test? Using the Oracle backend in the
> boulder-oracle-sprint branch, I get this:
> [, ]
> which fails because the doctest expected them in the opposite order.
...
> Should I fix the doctest(s) to be more accomodating, or am I mis
On 12/16/06, ogghead <[EMAIL PROTECTED]> wrote:
>
> Adding this to the lone model in tests/modeltests/basic/models.py fixes
> it:
>
> class Meta:
> ordering = ('id',)
>
> But it seems a bit strange to specify explicitly an ordering for a
> column that was implicitly created. Do others
On 12/17/06, Yasushi Masuda <[EMAIL PROTECTED]> wrote:
>
> Dear django developers,
>
> I'd like to notify that I have triaged ticket #3118 created by
> mtsuyuki[at]gmail.com. The ticket is reporting errata in 'UPDATE/INSERT'
> section of DB-API document.
Thanks for the triage! I've committed your
On 12/17/06, Fernando Gutierrez <[EMAIL PROTECTED]> wrote:
>
> This also excludes the integer 0 that evaluates to False. That is a
> problem, some legacy databases use 0 as the first pk for some tables, in
> that case you can't modify the objects that have this primary key.
Ok; ticket #2160 is tw
Hi all,
Time for the long promised phase 3 of the Django testing framework -
fixtures - to make an appearance. I've attached the changes as a
single patch to ticket #2333
(http://code.djangoproject.com/tickets/2333 )
The idea here is to exploit the serialization framework to provide a
mechanism
On 12/19/06, ogghead <[EMAIL PROTECTED]> wrote:
>
> Thanks for the guidance, Russ. Adding ordering = ('pub_date',) fixes
> the issue and also seems to match the intent of the doctests. I
> submitted a bug and a patch at
> http://code.djangoproject.com/ticket/3164 .
Fixed in [4228]. There was a
On 12/19/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>
> after a bit of tweaking with the MEDIA_ROOT i am able to post files
> through my custom manipulator. I still have to work on the validation
> scheme on the manipulator but this works for abeta launch.
I should point out at this poin
On 12/20/06, Jacob Kaplan-Moss <[EMAIL PROTECTED]> wrote:
I'm +1 on checking this into trunk right away -- as far as I can tell it's
completely backwards-compatible, right? Unless anyone objects -- and of
course after Adrian's given the OK -- are you happy enough with this to check
it in?
Th
On 12/20/06, Matthew Flanagan <[EMAIL PROTECTED]> wrote:
Hi Russell,
I've been using Hugo/Georg's stuff.testing [1] framework for quite a
while and some of the things I like about it are:
a. I can have fixtures located anywhere in my python path and load
them. I have project wide fixtures tha
On 12/18/06, Afternoon <[EMAIL PROTECTED]> wrote:
A little while ago there was a discussion[1] about test cases that post
raw data such as XML or JSON to a view. Russ suggested adding a
raw_post method to the test Client to facilitate such tests. I've
created a ticket and uploaded a patch that
On 12/19/06, Afternoon <[EMAIL PROTECTED]> wrote:
Currently any exception raised by a view or other request machinery
while handling a request from the test client is hidden from the
requesting test case by Django's exception views (500, error debug). I
have created a patch and a ticket for an
On 12/20/06, Gary Wilson <[EMAIL PROTECTED]> wrote:
Patch and a few tests added. Can someone please review and test on
something other than postgres.
http://code.djangoproject.com/ticket/2473
I use postgres myself as well, so I can't help out there. On the face
of it, it seems ok, but like
On 12/20/06, Jacob Kaplan-Moss <[EMAIL PROTECTED]> wrote:
On 12/19/06 5:12 PM, Russell Keith-Magee wrote:
> There are only two things that could be considered non-backwards
> compatible:
> 1) The renaming of the inital_data targets to custom_sql
How about we keep the initi
On 12/21/06, Ace Gopher <[EMAIL PROTECTED]> wrote:
Just wanted to note I created a patch to floatformat to make it more
generally useful. Please let me know what you think:
http://code.djangoproject.com/ticket/3176
Nice addition.
However, if you want this patch to be considered for inclusi
On 1/3/07, medhat <[EMAIL PROTECTED]> wrote:
Is there any update on including this into trunk?! I have been checking
the ticket daily :-)
Not yet. I'm still waiting for clearance from Adrian, and there are
one or two small outstanding issues (like support for databases that
don't have support
On 1/3/07, Robert Myers <[EMAIL PROTECTED]> wrote:
line 2548, in regressiontests.forms.tests
Failed example:
print w.render('mydate', '2010-04-15')
Thanks for the heads up. Fixed in [4272].
Yours,
Russ Magee %-)
--~--~-~--~~~---~--~~
You received this mes
On 1/3/07, Robert Myers <[EMAIL PROTECTED]> wrote:
http://code.djangoproject.com/ticket/3217
Currently the tests all pass, but if you look at my test there are a
few invalid options which are not being caught. And a few that are not
working or cause a different error to occur. I have commented
On 12/22/06, Gary Wilson <[EMAIL PROTECTED]> wrote:
Russell Keith-Magee wrote:
> If you can get some confirmation that this approach works on other
> backends, I'll put it in as an interim measure; and if nothing else,
> the tests are most helpful - Thanks for those.
In
On 12/22/06, Ace Gopher <[EMAIL PROTECTED]> wrote:
Thanks Russ,
Very good point. I added to the template filter regression tests and
modified the documentation to document the new functionality. I've
attached the patch files to the ticket.
Committed as [4274]. Thanks for the contribution.
On 12/24/06, Suriya <[EMAIL PROTECTED]> wrote:
This is regarding ticket #1541
http://code.djangoproject.com/ticket/1541
...
I'd like to see this functionality in Django :) Is there anything else
stopping this ticket from being closed?
Read the thread on the ticket - Jacob has stated what is
On 12/28/06, Gary Wilson <[EMAIL PROTECTED]> wrote:
code and tests attached, requesting eyes...
http://code.djangoproject.com/ticket/2756
Committed as [4275]. Thanks for the patch.
Yours,
Russ Magee %-)
--~--~-~--~~~---~--~~
You received this message because
On 1/4/07, Gary Wilson <[EMAIL PROTECTED]> wrote:
Russell Keith-Magee wrote:
> I just tested this on SQLite, and it fails with:
> OperationalError: no such column: false
Ok, I added a new patch [1] that uses where 0=1 instead of where false.
This seems to work with postgresql
Hi All,
I've been using newforms in anger recently, and I've hit a bit of a
hurdle. There might be an obvious way around this, but I can't see it.
If you define a form, you can instantiate it with no data, or you can
instantiate it with complete data (binding the form). However, what if
you onl
On 1/6/07, Adrian Holovaty <[EMAIL PROTECTED]> wrote:
On 1/5/07, Honza Král <[EMAIL PROTECTED]> wrote:
> see the 'initial' parameter for field...
> it is failry new, so you might want to run svn up...
Yes, and I just added documentation for that feature last night:
http://www.djangoprojec
On 1/6/07, Adrian Holovaty <[EMAIL PROTECTED]> wrote:
# Unbound form with dynamic initial data
f = MyForm(initial={'foo': 'initial value'})
# Bound form with dynamic initial data
f = MyForm({'foo': 'bar'}, initial={'foo': 'initial value'})
In the last case, the initial paramet
On 1/4/07, Suriya <[EMAIL PROTECTED]> wrote:
Russell Keith-Magee wrote:
>
> Read the thread on the ticket - Jacob has stated what is standing
> between the ticket and acceptance - documentation of the feature.
>
> Write some documentation (or at least get an intitial draf
On 1/9/07, inflector <[EMAIL PROTECTED]> wrote:
That whole discussion seems like it should have taken place here to me
but I'm a noob so perhaps I've missed the disctinction between users
and developers.
There is no formal distinction - users are the set of people
interested in using Django t
On 1/9/07, Victor Ng <[EMAIL PROTECTED]> wrote:
I've already emailed Jacob last week to open the branch for me.
Ok.
As it turns out - I've got *lots* of spare programming cycles since
I'm stuck in an entirely unholy quagmire of bureaucratic sludge right
now. :)
Delicious :-).
In the mea
On 1/14/07, Yasushi Masuda <[EMAIL PROTECTED]> wrote:
Adrian:
Thank you for comment.
I understood the policy not to creep the features, but let
me explain a bit about why I see benefit to have
proj_name/sql/app_name/obj_name.sql.
Just imagine we have an application comes with initial sql
dat
On 1/15/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
My proposal is a database data dumper based on django ORM - It would
not produce SQL but python code that would insert the data. Something
like (example dump):
You might want to check out the phase 3 patches associated with ticket
#2333
On 1/13/07, medhat <[EMAIL PROTECTED]> wrote:
Ok,
When writing unit tests, in a similar way to having fixtures as
proposed in http://code.djangoproject.com/ticket/2333 I would like to
have custom settings data for each test.
...
Does that make sense, or am I missing something?!
Broadly spe
On 1/14/07, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote:
Trac's non-feature of not automatically sending changes to the reporter
(which follows from not requiring a valid reporter email) doesn't help
here, either.
I'd always wondered about this.. er... feature. Is it possible to
filter the s
On 1/13/07, Jacob Kaplan-Moss <[EMAIL PROTECTED]> wrote:
Howdy folks --
I think it's time to start a push towards releasing Django 1.0. What follows
are my thoughts about how I'd like this process to work.
...
== Other must-haves ==
* Test fixtures. I think we're just waiting on Adrian's
On 1/16/07, Michael Radziej <[EMAIL PROTECTED]> wrote:
Hi,
Victor Ng schrieb:
>
> Hey - any chance I'll get a schema evo-branch before 1.0?
What's the point in making Victor wait all the time? He has asked
multiple times for a branch, and nobody makes any decision :-(
You're attributing to
On 1/16/07, CosyGlow42 <[EMAIL PROTECTED]> wrote:
I'm getting the following error, doesn't matter what I'm doing to fix
it. I've already used all the advice given in simular topic and scanned
my sys.path for the Python24 path multple time. I've also compared my
sys.path by going through the Exp
Sorry this has taken a while to look at - hopefully I'm not too late
to make a meaningful contribution...
On 1/12/07, James Bennett <[EMAIL PROTECTED]> wrote:
Other than the fact that it's currently a tuple, is there any reason
not to change this to a dictionary? That'd feel cleaner and make it
On 1/17/07, Michael Radziej <[EMAIL PROTECTED]> wrote:
I wouldn't have thought that it could raise feelings like this. Please
accept my apologies. English isn't my first language, and the usual
communication culture in Germany is very direct without people feeling
bad about it. It obviously loo
On 1/23/07, Adrian Holovaty <[EMAIL PROTECTED]> wrote:
>
> Could somebody provide some unit tests that isolate the problem? I've
> never mucked with the GenericForeignKey code -- perhaps Jacob or
> Russell could chime in here for the fix?
I've never really played with GenericRelations, so I don't
On 1/23/07, Russell Keith-Magee <[EMAIL PROTECTED]> wrote:
> On 1/23/07, Adrian Holovaty <[EMAIL PROTECTED]> wrote:
> >
> > Could somebody provide some unit tests that isolate the problem? I've
> > never mucked with the GenericForeignKey code -- perhaps Ja
On 1/23/07, Russell Keith-Magee <[EMAIL PROTECTED]> wrote:
>
> I've just attached a unit test to the ticket. It seems to be the same
> issue described in #2749 and #3081. I think I understand the problem;
> the patch on #3081 is pretty much correct. I should have this
On 1/24/07, Sean Perry <[EMAIL PROTECTED]> wrote:
> I could care less about most of the keywords. However, having Rev or
> Id set is handy for the sysadmin down the road trying to figure out
> where the bug came from.
Isn't that what `svn blame` is for?
Count me -1 on keywords expansion, too.
Y
On 1/25/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?
Magnificent stuff, guys! You're all doin
On 1/25/07, Sean Perry <[EMAIL PROTECTED]> wrote:
>
> For example, admin A finds out about Django downloads a tarball /
> checks out svn. He installs it to /usr/local/blah and writes some web
> apps. At some point in the future admin B has to find out why an app
> is not working and it turns out t
On 1/23/07, Russell Keith-Magee <[EMAIL PROTECTED]> wrote:
> On 1/23/07, Russell Keith-Magee <[EMAIL PROTECTED]> wrote:
> >
> > I've just attached a unit test to the ticket. It seems to be the same
> > issue described in #2749 and #3081. I think I understand
On 1/25/07, Gary Wilson <[EMAIL PROTECTED]> wrote:
>
> a shiny new title.
This one needs a little bit more than a shiny title to get some
attention. The problem description refers to pre-magic removal syntax,
and the discussion that follows doesn't leave me with a clear and
obvious idea of what e
On 1/26/07, James Bennett <[EMAIL PROTECTED]> wrote:
>
> On 1/25/07, Russell Keith-Magee <[EMAIL PROTECTED]> wrote:
> > My jetlag has worn off, so now I can see the obvious problem that I
> > missed on Tuesday. I've checked in the fix as [4428].
>
> It
On 1/26/07, Rob Hudson <[EMAIL PROTECTED]> wrote:
>
> Wow, I didn't even know those existed. Besides this bug, are these
> considered stable?
Stable in operation, but not fully featured - they aren't represented
in the Admin view, and I don't know what form field would be (or
should be) automati
On 1/26/07, Honza Král <[EMAIL PROTECTED]> wrote:
> On 1/25/07, Jorge Gajon <[EMAIL PROTECTED]> wrote:
> >
> > On 1/24/07, Russell Keith-Magee <[EMAIL PROTECTED]> wrote:
> > >
> I would like to see the revision number SOMEWHERE, preferably
> so
Hi all,
I've just uploaded a revised test fixtures patch to ticket #2333,
rolling in the changes suggested by Jacob and others. A description of
the changes is on the ticket [1].
There is one outstanding issue - database support. Oracle and ADO
support is untested (due to a lack of availability
Hi All,
I've just created two new tickets - #3389 and #3390.
http://code.djangoproject.com/ticket/3389/
http://code.djangoproject.com/ticket/3390/
They both have patches attached, but the ideas are not completely
trivial, so I thought I'd throw them out for comment before I did
anything damagin
On 1/29/07, Jacob Kaplan-Moss <[EMAIL PROTECTED]> wrote:
>
> On 1/29/07 7:22 AM, Russell Keith-Magee wrote:
> > I've just created two new tickets - #3389 and #3390.
>
> I'm +1 on #3390 (the ``DEFERRABLE INITIALLY DEFERRED`` bit); that makes a few
>
On 1/30/07, Ivan Sagalaev <[EMAIL PROTECTED]> wrote:
>
> Article.authors = [Author(id) for id in [4,7]]
>
> I.e. Author(id) creates some strange incomplete object that can be
> nonetheless used for m2m relations since only an id is needed. Would
> this suffice?
I hadn't considered that appro
On 1/30/07, David Larlet <[EMAIL PROTECTED]> wrote:
> I'm +1 on this option. Before making decision what about at least add
> a warning message on the documentation page?
This is kind of the point. Which documentation page? Generic relations
exist, but they aren't documented - specifically becaus
On 2/3/07, Adrian Holovaty <[EMAIL PROTECTED]> wrote:
>
> Regarding "edit inline," a couple of decisions need to be made. Ticket
> #2248 (http://code.djangoproject.com/ticket/2248) has an interesting
> suggestion: you define the inline stuff within the admin class. I'll
> copy and paste from that
Hi All,
Has anyone else noticed that since the changes to Trac were rolled
out, Subversion checkin messages don't seem to be firing the Trac
triggers?
The standard 'Fixed #1234 -- Did blah` checkin messages don't seem to
be registering on Trac or closing the tickets. As a result, I have had
to m
On 2/7/07, Michael Radziej <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> we are still waiting for confirmation, but it seems that with
> changeset 4459, adding inline items in the admin is broken. See
> ticket #3447. The resulting error looks like this:
I've reverted [4459]. Admin should be back to norm
On 2/9/07, Gary Wilson <[EMAIL PROTECTED]> wrote:
>
> ohloh thinks so too [1]:
> "Across all Python projects on Ohloh, 13% of all source code lines are
> comments. For Django, this figure is only 6%.
... and yet, for all the lack of documentation, I discovered Django in
late November 2005, and by
On 2/8/07, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote:
>
> Your plan seems sensible: let's make sure all the external stuff is
> documented. Let's also look at stuff that is on the boundary between
> internal and external -- an obvious one here is the Field class, since
> we've talked previously
On 2/9/07, Gary Wilson <[EMAIL PROTECTED]> wrote:
>
> Now, that's actually useful. I think Django developers would benefit
> from more comments like these.
Granted. However, what this discussion needs is the specific, not
abstract. We're all agreed that "missing comments bad, helpful
comments go
On 2/9/07, Gary Wilson <[EMAIL PROTECTED]> wrote:
>
> Anyone have opinions on what would be best, file new tickets for each
> instance, or maybe collect everything on a wiki page?
Open tickets. Reporting problems is what tickets are for, and there is
already a value of documentation for the compo
801 - 900 of 2850 matches
Mail list logo
