On Sun, Sep 26, 2010 at 6:40 PM, Waldemar Kornewald
wrote:
> On Sun, Sep 26, 2010 at 6:54 AM, Russell Keith-Magee
> wrote:
>> Also, you say a "huge" amount of analysis -- at the moment, *any*
>> analysis would be a step in the right direction. I haven't seen *any
On Sun, Sep 26, 2010 at 8:45 PM, Florian Apolloner
wrote:
> Hi,
> Another question that came into my mind, after reading
> http://www.reddit.com/r/Python/comments/ddkal/django_vs_web2py_what_do_you_use_and_why/c0zmxqz
> (actually the whole thread, but that's the relevant post): Is there an
> easy
Hi all,
I've just uploaded a patch for #12991, adding support for unittest2 to Django.
This is a very big patch (500kb, 12k lines). For this reason, I've
uploaded the patch compressed. Trac won't allow attachments greater
than 200k, and given past history, large diffs break Trac anyway.
However,
On Mon, Sep 27, 2010 at 4:28 AM, Vinay Sajip wrote:
> On Sep 26, 2:16 pm, Florian Apolloner wrote:
>> I am aware of those; but let's imagine a 3rd party library which has
>> no idea what a request is. In my logs I still want to know the request
>> (even if it's just for formatting purposes…); so
On Mon, Sep 27, 2010 at 6:24 AM, Karen Tracey wrote:
> I've run it on Python 2.4 & 2.5 (Ubuntu, sqlite DB) with no problems.
>
> I do have some feedback on the @skipIfDB addition: I'd really like if this
> could be used to distinguish between the different MySQL storage backends.
> From a very bri
On Monday, September 27, 2010, Patrick Altman wrote:
>
> On Sep 26, 2010, at 7:44 PM, Russell Keith-Magee wrote:
>
>> On Mon, Sep 27, 2010 at 6:24 AM, Karen Tracey wrote:
>>> I've run it on Python 2.4 & 2.5 (Ubuntu, sqlite DB) with no problems.
>>>
&g
On Monday, September 27, 2010, Chuck Harmston wrote:
> I just ran it on Python 2.4, 2.5, 2.6, and 2.7 with each of SQLite, MySQL,
> and PostgreSQL on Debian with no problems.
Awesome! Thanks for that, Chuck.
Yours,
Russ Magee %-)
--
You received this message because you are subscribed to the
On Mon, Sep 27, 2010 at 1:43 PM, Mathieu Leduc-Hamel wrote:
> Hi all,
>
> I'm curious to know if it's planned in the future to force the use of
> the complete name of the applications and the templatestags. I'll
> explain myself.
>
> Imagine you have an application called
>
> hello.world
>
> with
On Tue, Sep 28, 2010 at 1:51 AM, Mark Bucciarelli wrote:
> On Sat, Sep 25, 2010 at 10:21:06PM +0800, Russell Keith-Magee wrote:
>>
>> The number 4 wasn't actually the important bit - it was that I want
>> to see a range of noSQL approaches represented. I don't want
On Mon, Sep 27, 2010 at 11:16 PM, Luke Plant wrote:
> Hi Russell,
>
> On Sat, 2010-09-25 at 14:16 +0800, Russell Keith-Magee wrote:
>
>> At this point, I'm calling for feedback, particularly on the following:
>>
>> * logging config as the last stage of set
On Tue, Sep 28, 2010 at 8:31 AM, David P. Novakovic
wrote:
> This has probably been discussed at great length previously... but my
> 2c follows:
>
> If you are using a column/doc store you are trying to solve a
> different problem than if you are using an SQL db.
>
> How important is 100% interop?
On Tue, Sep 28, 2010 at 7:43 PM, Luke Plant wrote:
> On Sat, 2010-09-25 at 14:16 +0800, Russell Keith-Magee wrote:
>
>> * The default logging configuration. Have I got the
>> propagate/override options right for sensible defaults (both in global
>> and new-project setti
2010/9/29 Łukasz Rekucki :
> On 28 September 2010 17:45, Ian Lewis wrote:
>> Hi,
>>
>> On Tue, Sep 28, 2010 at 9:19 AM, Nick Phillips
>> wrote:
>>> I'm worried by the use of "warning" for all 4xx statuses. I think it
>>> still makes sense to use the "original" syslog level definitions[*] as a
>>>
On Tue, Sep 28, 2010 at 11:45 PM, Ian Lewis wrote:
> Hi,
>
> On Tue, Sep 28, 2010 at 9:19 AM, Nick Phillips
> wrote:
>> I'm worried by the use of "warning" for all 4xx statuses. I think it
>> still makes sense to use the "original" syslog level definitions[*] as a
>> guide, and on there I'd sugge
On Wed, Sep 29, 2010 at 9:40 AM, Nick Phillips
wrote:
> On Wed, 2010-09-29 at 09:00 +0800, Russell Keith-Magee wrote:
>
>> These all strike me as messages appropriate for a warning -- they're
>> all slightly concerning indications that you're either under some sort
On Wed, Sep 29, 2010 at 5:43 PM, Ian Lewis wrote:
> Not sure I ever understood what Bikeshedding means properly, but fair
> enough.
For the history and meaning of the term, see here:
http://bikeshed.com/
Yours,
Russ Magee %-)
--
You received this message because you are subscribed to the Goog
On Thu, Sep 30, 2010 at 7:26 AM, Luke Plant wrote:
> On Thu, 2010-09-30 at 01:32 +0400, Ivan Sagalaev wrote:
>
>> My suggestion is about this unfortunate ticket status -- 'Accepted'.
>> This now works as a sort of a dusty shelf: when anyone of the core team
>> looks at the patch and decides that t
On Thu, Sep 30, 2010 at 9:14 AM, Waylan Limberg wrote:
> On Wed, Sep 29, 2010 at 7:46 PM, Russell Keith-Magee
> wrote:
>> On Thu, Sep 30, 2010 at 7:26 AM, Luke Plant wrote:
>>> On Thu, 2010-09-30 at 01:32 +0400, Ivan Sagalaev wrote:
>>>
>>>> My suggesti
On Thursday, September 30, 2010, Ivan Sagalaev
wrote:
> On 09/30/2010 03:46 AM, Russell Keith-Magee wrote:
>
> Accepted tickets can be:
>
> * Purely accepted, indicating that someone has verified that the
> problem exists, but not how to solve it
>
> * Accepted with
Hi all,
A final call for comment before I commit #12012 to trunk. Barring
objection, my intention is to commit this early next week.
I've integrated the suggestions that have arisen since the first draft:
* This patch has docs :-) There aren't any tests though, and I think
it's going to have to
On Thu, Sep 30, 2010 at 10:03 PM, Jacob Kaplan-Moss wrote:
> On Thu, Sep 30, 2010 at 8:56 AM, Russell Keith-Magee
> wrote:
>> If you have any objections, now is the time to raise them.
>
> This isn't an objection, per se -- don't let it stop you committing --
>
On Fri, Oct 1, 2010 at 6:15 AM, Laurent Luce wrote:
> I updated the be localflavor patch to use unit tests instead of
> doctests as requested. Can you check if this is what you want. There
> was no unit tests in regressiontests/forms/localflavor/ so I am not
> 100% sure I did what is expected. I t
On Fri, Oct 1, 2010 at 1:53 AM, Andy McCurdy wrote:
> Russ,
> This will be a welcomed addition to debugging Django apps. I have a question
> about startup.py. I notice that startup runs after settings are loaded, but
> before models. Does this mean that code within startup.py cannot safely
> acces
Hi all,
I've just added a summary of the last thread on class-based views [1].
This summary isn't 100% complete -- any contributions from interested
parties are welcome. Try to keep opinions to a minimum; this page is
about documenting the strengths and weaknesses of various approaches,
not about
ing.
These are fairly minor modifications, so I'm still intending to commit
early next week, barring major objections.
Yours,
Russ Magee %-)
On Thu, Sep 30, 2010 at 9:56 PM, Russell Keith-Magee
wrote:
> Hi all,
>
> A final call for comment before I commit #12012 to trunk. Barring
&g
On Fri, Oct 1, 2010 at 6:46 PM, burc...@gmail.com wrote:
> Hi Russell,
>
> Few more questions I haven't seen answers yet.
>
> How should urls() work for such views? Should they?
Erm... no. A view doesn't have a collection of URLs. A view is a view.
What we're debating here is a way to construct g
On Fri, Oct 1, 2010 at 6:42 PM, David Larlet wrote:
>
> Russell Keith-Magee a écrit :
>
>> * Conversion of the github project into a patch on trunk.
>
> Do you see that as a total replacement of actual views.generic or should we
> go for a old/new dance?
Unless you&
On Fri, Oct 1, 2010 at 6:17 PM, Luke Plant wrote:
> On Fri, 2010-10-01 at 11:12 +0200, Hanne Moa wrote:
>> On 1 October 2010 07:26, Russell Keith-Magee wrote:
>> > I already have one specific piece of API feedback: the current
>> > implementation requires that all vie
On Fri, Oct 1, 2010 at 6:16 PM, Johannes Dollinger
wrote:
> Am 01.10.2010 um 07:26 schrieb Russell Keith-Magee:
>> I've just added a summary of the last thread on class-based views [1].
>> This summary isn't 100% complete -- any contributions from interested
>> p
On Fri, Oct 1, 2010 at 11:20 PM, Alex Gaynor wrote:
> On Fri, Oct 1, 2010 at 11:16 AM, Russell Keith-Magee
> wrote:
>> On Fri, Oct 1, 2010 at 6:16 PM, Johannes Dollinger
>> wrote:
>>> Am 01.10.2010 um 07:26 schrieb Russell Keith-Magee:
>>>> I've just
On Saturday, October 2, 2010, David P. Novakovic
wrote:
> My problem with all of this is that it feels like a hell of a lot of
> hoopjumping to deal with something that could be solved in the
> Resolver.
>
> I may be missing something obvious here, so please tell me if I am..
> but couldn't the re
On Saturday, October 2, 2010, Vinay Sajip wrote:
>
> On Oct 1, 4:16 pm, Russell Keith-Magee
> wrote:
>
>> "Don't use instance variables on a class" isn't advice you're going to
>> see printed very often. Yet that would be the advice that would
On Sat, Oct 2, 2010 at 12:56 PM, Carl Meyer wrote:
>
>
> On Oct 1, 10:00 pm, Russell Keith-Magee
> wrote:
>> Now, I'm sure the counterargument is going to be that copy() will be
>> just as error prone and FAQ inducing. My argument to this is:
>
> Yes.
>
>
2010/10/2 Łukasz Rekucki :
> On 2 October 2010 10:34, Russell Keith-Magee wrote:
>>
>> Another option would be to use copy-on-call, but raise an error if
>> they provide any arguments to __init__(). This would be annoying and
>> counter to Python idiom, but it strik
On Sat, Oct 2, 2010 at 6:08 PM, Patryk Zawadzki wrote:
> On Fri, Oct 1, 2010 at 3:55 PM, Alex Gaynor wrote:
>> On Fri, Oct 1, 2010 at 9:53 AM, Vinay Sajip wrote:
>>> On Oct 1, 11:16 am, Johannes Dollinger
>>> wrote:
Could you (or anyone knowledgable) add a section, that explains why each
On Sat, Oct 2, 2010 at 7:05 PM, Patryk Zawadzki wrote:
> On Sat, Oct 2, 2010 at 12:49 PM, Russell Keith-Magee
> wrote:
>> Python classes have state. People *will* assign variables to self,
>> because that's something they have done with every other Python class
>>
Hi all,
I've just uploaded a second alpha of the patch introducing unittest2
into Django's core [1]. As with last time, help is requested running
the test suite on different Python versions and different databases.
Particular attention is needed for the Oracle and GeoDjango changes,
as I don't hav
On Sat, Oct 2, 2010 at 8:01 PM, Carl Meyer wrote:
>
>
> On Oct 2, 4:34 am, Russell Keith-Magee
> wrote:
>> I can't argue with the fact that setting variables in __init__() is a
>> common idiom in Python generally, and this is certainly a weakness of
>> copy o
On Sun, Oct 3, 2010 at 12:20 AM, George Sakkis wrote:
> On Oct 1, 7:26 am, Russell Keith-Magee
> wrote:
>>
>> I've just added a summary of the last thread on class-based views [1].
>
> Thanks for writing this up. Having missed the discussion on that
> thread, the
2010/10/3 Łukasz Rekucki :
> On 2 October 2010 12:32, Russell Keith-Magee wrote:
>> 2010/10/2 Łukasz Rekucki :
>>> On 2 October 2010 10:34, Russell Keith-Magee
>>> wrote:
> To sum this up, I think the important questions are:
>
> 1) Do View instances
On Sat, Oct 2, 2010 at 8:59 AM, Kevin Howerton wrote:
> Definitely agree. Caught the missing nullhandler behavior when
> logging is off too... though didn't make the connection that this was
> likely intended to handle that case.
>
> It might make more sense to put this logic in conf/__init__.py
2010/10/3 Łukasz Rekucki :
> On 3 October 2010 04:44, Russell Keith-Magee wrote:
>> 2010/10/3 Łukasz Rekucki :
>>>>> def with_args(view_cls, **kwargs):
>>>>> return type(view_cls.__name__, (view_cls,), kwargs)
>>>>>
>>>>&g
On Sun, Oct 3, 2010 at 12:12 PM, Ian Lewis wrote:
> On Sun, Oct 3, 2010 at 11:20 AM, Russell Keith-Magee
> wrote:
> While I'm in the "one singleton view instance is best" camp and think
> that storing some state on the request and some on the view is a bit
>
On Sun, Oct 3, 2010 at 5:58 PM, Marcob wrote:
> On 30 Set, 07:34, "subs...@gmail.com" wrote:
>> Hello all,
>> I was browsing the tickets and saw a few of them nagging about some
>> restrictions to raw_id_fields.
>
> Since my first Django installation, a couple of years ago, I fixed and
> used thi
On Sun, Oct 3, 2010 at 6:09 PM, Marcob wrote:
> I think that #6903 ticket http://code.djangoproject.com/ticket/6903
> (together with http://code.djangoproject.com/ticket/12241) should be
> considered to be in 1.3 release.
> Every single person I know that use admin without this patch asks for
> th
2010/10/4 Łukasz Rekucki :
> On 3 October 2010 20:53, Laurent Luce wrote:
>> Am I supposed to commit the patch? I don't think I have the privileges
>> to do that.
>
> No, only core developers can commit changes. The patch is marked RFC
> and has milestone 1.3, so it's pretty sure it won't be forgo
On Mon, Oct 4, 2010 at 4:53 AM, Sean Brant wrote:
> I know this has come up over the last few years[1] and people are
> mixed on the action that should be taken. I would like to bring it up
> again as it has bitten me a few time lately.
>
> I seems the biggest concern is backwards compatibility of
On Mon, Oct 4, 2010 at 8:56 AM, Sean Brant wrote:
>
> On Oct 3, 2010, at 7:37 PM, Russell Keith-Magee wrote:
>
>> On Mon, Oct 4, 2010 at 4:53 AM, Sean Brant wrote:
>>> I know this has come up over the last few years[1] and people are
>>> mixed on the action that
On Mon, Oct 4, 2010 at 10:11 AM, Laurent Luce wrote:
> Hello,
>
> I added the localflavor for Belgium as my first contribution. I would
> like to contribute more code wise. I looked at the tickets with
> milestone 1.3 and with no patch. It is hard to know what is critical
> and where help is the m
On Oct 2, 11:27 pm, Russell Keith-Magee
wrote:
> Hi all,
>
> I've just uploaded a second alpha of the patch introducing unittest2
> into Django's core [1]. As with last time, help is requested running
> the test suite on different Python versions and different database
On Tuesday, 5 October 2010 at 12:17 AM, Sean Brant wrote:
On Oct 3, 8:08 pm, Russell Keith-Magee
wrote: On Mon, Oct 4, 2010 at 8:56 AM, Sean Brant
wrote: > Thanks for the feedback Russ. I know it couldn't be that straight
forward. I'
On Tue, Oct 5, 2010 at 2:55 AM, Laurent Luce wrote:
> Hello,
>
> I am looking at ticket #14268 on reset and sqlreset management
> commands should raise PendingDeprecationWarning for 1.3.
>
> I added some code to django/core/management/commands/reset.py and
> django/core/management/sql.py to raise
On Tue, Oct 5, 2010 at 7:27 AM, SmileyChris wrote:
> Just throwing the idea out there, it would be possible to keep the tag
> completely backwards compatible by using a slightly different syntax
> for variables.
>
> Standard non-variable access stays the same: {% url home %}, {% url
> edit-profile
On Tue, Oct 5, 2010 at 8:16 AM, Tai Lee wrote:
> Hi Jacob,
>
> Thanks for your feedback.
>
>> For (1) check out http://code.djangoproject.com/wiki/Reports(it's
>> linked in the nav). If there's anything missing there, please feel
>> free to add it -- it's a wiki page. Let me know if you need help
On Tue, Oct 5, 2010 at 9:58 AM, Tai Lee wrote:
> Hi Russ,
>
> On Oct 5, 11:48 am, Russell Keith-Magee
> wrote:
>
>> > Perhaps we need another triage stage for these tickets, "Needs final
>> > review" or something?
>>
>> That's e
On Tue, Oct 5, 2010 at 10:02 AM, Laurent Luce wrote:
> Thanks for those details. In case someone is using those commands and
> is kind of happy with them, what would be the alternative? sql_reset =
> sql_delete + sql_add but those commands are not exposed so I am
> wondering.
It depends a little
On Tue, Oct 5, 2010 at 5:43 AM, George Sakkis wrote:
> On Oct 4, 10:55 pm, "David P. Novakovic"
> wrote:
>> On Tue, Oct 5, 2010 at 5:21 AM, George Sakkis
>> wrote:
>>
>> > Since dispatch is going to be defined on the base View class, can't we
>> > omit it from the urlconf and have the URLresolv
On Tue, Oct 5, 2010 at 3:16 AM, Luke Plant wrote:
> On Mon, 2010-10-04 at 13:08 -0400, Alex Gaynor wrote:
>
>> Last idea, I swear,
>
> I didn't swear, so here is another slight variation :-) You actually
> *call* the classmethod in your URLconf, passing any constructor
> arguments to it:
>
> url(r
On Tue, Oct 5, 2010 at 1:22 PM, ptone wrote:
>
>
> On Oct 4, 7:37 pm, Russell Keith-Magee
> wrote:
>> On Tue, Oct 5, 2010 at 10:02 AM, Laurent Luce
>> wrote:
>> > Thanks for those details. In case someone is using those commands and
>> > is
On Tue, Oct 5, 2010 at 12:59 PM, Russell Keith-Magee
wrote:
> On Tue, Oct 5, 2010 at 3:16 AM, Luke Plant wrote:
>> On Mon, 2010-10-04 at 13:08 -0400, Alex Gaynor wrote:
>>
>>> Last idea, I swear,
>>
>> I didn't swear, so here is another slight variation :
On Wednesday, October 6, 2010, Tom Eastman wrote:
> Hey guys,
>
> I'm using Django to create an interface for a legacy PostgresQL database.
> The primary keys for my tables use sequences that aren't named the way django
> expects them to be (i.e. '__seq'), this means I can't call
> them AutoFi
2010/10/6 Łukasz Rekucki :
> Hi,
>
> I'm getting a whole bunch of errors related to logging on Python 2.4::
>
> ERROR: Missing templates are correctly reported by test client
> --
> Traceback (most recent call last):
> File
> "/h
Dang - accidentally hit send. Let's try that again.
2010/10/6 Russell Keith-Magee :
> 2010/10/6 Łukasz Rekucki :
>> Hi,
>>
>> I'm getting a whole bunch of errors related to logging on Python 2.4::
>>
>> ERROR: Missing temp
On Wed, Oct 6, 2010 at 8:33 AM, Luke Plant wrote:
> On Tue, 2010-10-05 at 22:29 +0100, I wrote:
>
>> Russell - beware - I think bitbucket has managed to create a very broken
>> clone. I did a fork as well, and both of our repositories are missing
>> thousands of commits. I can do a pull from djan
On Wed, Oct 6, 2010 at 7:43 AM, Gabriel Hurley wrote:
> There has been repeated talk of putting together resources for new
> contributors in a way that's more accessible and to-the-point than the
> current contributing docs. Most recently Russell mentioned it in this
> thread:
>
> http://groups.go
On Wed, Oct 6, 2010 at 6:46 PM, Luke Plant wrote:
> On Wed, 2010-10-06 at 12:24 +0800, Russell Keith-Magee wrote:
>
>> Monkeypatching isn't a particularly attractive option to me - there's
>> just too much .
>>
>> A fourth option would be to include Python
On Wed, Oct 6, 2010 at 8:08 PM, Luke Plant wrote:
> On Wed, 2010-10-06 at 12:24 +0800, Russell Keith-Magee wrote:
>
>> A fourth option would be to include Python's logging module, much as
>> we do with doctest, simpleJSON, and we're about to do with unittest2.
>>
On Wed, Oct 6, 2010 at 9:02 PM, Luke Plant wrote:
> On Wed, 2010-10-06 at 07:42 -0400, Karen Tracey wrote:
>> On Wed, Oct 6, 2010 at 6:53 AM, Russell Keith-Magee
>> wrote:
>> That approach works (as in - it doesn't raise errors), but it
>> means
On Wed, Oct 6, 2010 at 9:23 PM, Vinay Sajip wrote:
>
> On Oct 6, 11:53 am, Russell Keith-Magee
> wrote:
>> On Wed, Oct 6, 2010 at 6:46 PM, Luke Plant wrote:
>> > On Wed, 2010-10-06 at 12:24 +0800, Russell Keith-Magee wrote:
>
> There are other possibilities. For e
On Wed, Oct 6, 2010 at 9:40 PM, Vinay Sajip wrote:
>
> On Oct 6, 2:29 pm, Russell Keith-Magee
> wrote:
>> On Wed, Oct 6, 2010 at 9:23 PM, Vinay Sajip wrote:
>>
>> > On Oct 6, 11:53 am, Russell Keith-Magee
>> > wrote:
>> >> On Wed, Oct 6, 2010
On Thu, Oct 7, 2010 at 11:15 AM, Adrian Holovaty wrote:
> On Wed, Oct 6, 2010 at 10:09 PM, Owen Nelson wrote:
>> Moving forward, I'll be skipping the comment-specific setting and simply
>> setting PROFANITIES_LIST to (). Any chance we'll see the setting removed in
>> the near future?
>
> Yes, it
On Thu, Oct 7, 2010 at 11:42 AM, Owen Nelson wrote:
> On Wed, Oct 6, 2010 at 11:30 PM, Russell Keith-Magee
> wrote:
>>
>> Strictly, it needs to be put on a deprecation path, because it *is*
>> documented, in ref/settings.txt. So the earliest we can truly remove
On Thu, Oct 7, 2010 at 1:57 AM, Shai Berger wrote:
> Hi all,
>
> I am developing an application which needs to write an audit log to a
> database. I want the committing of log records to be independent of the
> committing of other database writes (so user actions can be audited even if
> they caus
On Thu, Oct 7, 2010 at 6:15 PM, Luke Plant wrote:
> On Thu, 2010-10-07 at 11:30 +0800, Russell Keith-Magee wrote:
>
>> Strictly, it needs to be put on a deprecation path, because it *is*
>> documented, in ref/settings.txt. So the earliest we can truly remove
>&g
On Thu, Oct 7, 2010 at 7:33 PM, Luke Plant wrote:
> On Thu, 2010-10-07 at 18:50 +0800, Russell Keith-Magee wrote:
>
>> The set of people that will be affected here are are all opt-in --
>> they've had to set COMMENTS_ALLOW_PROFANITIES=True -- so I would have
>> ass
On Fri, Oct 8, 2010 at 11:28 AM, Laurent Luce wrote:
> I noticed that create_user() is currently setting password to unusable
> if it is None or empty. However, set_password() is accepting an empty
> password. I decided to follow the first rule in the patch I submitted
> but I am kind of confused
On Fri, Oct 8, 2010 at 10:09 AM, Jacob Burch wrote:
> Bringing this back for more design decision discussion. I've started a
> (very basic) wiki page with a brief summation of the situation here:
> http://code.djangoproject.com/wiki/PylibmcSupport
>
> Of note from that wiki page are three main iss
On Thu, Oct 7, 2010 at 5:30 PM, George Sakkis wrote:
> There are at least three open tickets related to OneToOneFields
> (#10227, #14043, #14368) that, even if deemed invalid, hint at lack of
> adequate documentation. After reading the docs on OneToOneField, I
> don't think one can easily answer t
Hi all,
This is a final call for comment on #12991, the introduction of
unittest2. Barring objection, my intention is to commit this on
Monday.
I've now had confirmation that the suite passes under GIS, and a
couple more reports of successful test passes under different Python
versions and databa
My apologies, Simon. This has been on my list of things to look at,
but people keep putting more things on top of that list :-)
I've had a cursory look at the patch, and it looks good. I'll need to
take a much closer look before I commit anything, but it certainly
looks to be on the right path. Th
On Sat, Oct 9, 2010 at 5:13 PM, George Sakkis wrote:
> Thanks for the thorough reply, it was helpful, even without replying
> directly to any of the specific questions about the leakiness of the
> abstraction :-)
Damn. You noticed :-)
> I'll try to come up with patches+tests for #14043 and #1436
On Sat, Oct 9, 2010 at 2:25 AM, Michel Thadeu Sabchuk
wrote:
> Hi guys, how are you?
>
> I had problems with DecimalField and localize input/output. I found
> the bug and I'm working on it:
>
> http://code.djangoproject.com/ticket/14101
>
> While I digging to find the bug, I see that the DecimalFi
2010/10/11 Filip Gruszczyński :
> I am not very familiar with all this, but I took a look at the code
> and have a question. Would it be enough to make a following validation
> before setting up test databases: for each two connections using the
> same backend names of the test databases are differ
On Mon, Oct 11, 2010 at 12:43 PM, Alex Gaynor wrote:
> On Mon, Oct 11, 2010 at 12:41 AM, Henrique Bastos wrote:
>> Alex,
>> Is there any specific branch on unit testing migration? It would be useful
>> to understand the work in progress before submitting patches.
>> All the best,
>> --
>> Henriqu
2010/10/11 Mikhail Korobov :
> Hi all,
>
> If it will be a contextmanager then it can also be extended to perform
> like a decorator: http://gist.github.com/573536
> I think this can be useful.
Alex and I have spoken about this (and a couple of other places that
context managers would be useful, l
On Mon, Oct 11, 2010 at 6:17 AM, Alex Gaynor wrote:
> Hey all,
>
> I've been spending some time with ticket #5416[0], which is a request
> for assertNumQueries in tests. The primary objection Russ had to the
> previous patch in this vein was that It uses connection.queries as
> opposed to the pro
On Mon, Oct 11, 2010 at 4:35 PM, Andrew Godwin wrote:
> On 11/10/10 07:05, Alex Gaynor wrote:
>>
>> I think the solution there is something like:
>>
>> @skipUnless(sys.version>= (2, 5))
>> def test(self):
>> exec """
>> from __future__ import with_statement
>> with self.assertNum
On Wed, Oct 13, 2010 at 10:20 AM, Ian Lewis wrote:
> Hi all,
> I am a member of the Japanese Django community which is maintaining a
> somewhat(read very) outdated version of the Django documentation
> here: http://djangoproject.jp/doc/ja/1.0/
> I'm trying to kickstart a project to update the docu
Hi all,
With the deadline for 1.3 alpha rapidly approaching, it's getting to
crunch time for class-based views.
The wiki page [1] now contains a good summary of the debate so far,
showing why we have ended up at the "ClassBasedView.as_view()"
deployment solution. I've also got a implementation up
2010/10/15 Łukasz Rekucki :
> On 14 October 2010 18:19, Russell Keith-Magee wrote:
>>
>> The following things are still needed:
>>
>> * An audit of create/update views.
>> * An audit of date views.
>
> I was planning on hacking onto this on today/tomorrow
On Fri, Oct 15, 2010 at 1:59 PM, Yo-Yo Ma wrote:
> I realize this is a bit late and not even the "right" discussion, bit
> I just stumbled across this and the wiki, and I feel a bit sick to my
> stomach.
>
> 1) self.request?
>
> Whatever gains come from this will be offset by loss in design. A
> m
On Fri, Oct 15, 2010 at 8:30 PM, David De La Harpe Golden
wrote:
> On 15/10/10 07:11, Russell Keith-Magee wrote:
>
>> We're happy to entertain design suggestions, but only if they're
>> enlightened by the extensive discussions that have proceeded the
>> implement
On Fri, Oct 15, 2010 at 1:09 AM, Justin Lilly wrote:
> Because you asked, I think this sounds like a great idea.
>
> When you have decided you like the API for create/update
> views, please send another email to the list, so that we
> know we've hit a stable API to write documentation
> against.
On Sunday, October 17, 2010, Yo-Yo Ma wrote:
> Gabriel
>
> You don't have to go to thesaurus.com with the intention of generating
> a more formidable argument. I was merely offering my opinion. Playing
> devil's advocate should be regarded as counter constructive. If I see
> a man about to throw a
On Sat, Oct 16, 2010 at 12:45 AM, Russell Keith-Magee
wrote:
> On Fri, Oct 15, 2010 at 1:09 AM, Justin Lilly wrote:
>> Because you asked, I think this sounds like a great idea.
>>
>> When you have decided you like the API for create/update
>> views, please send another
On Mon, Oct 18, 2010 at 2:00 AM, legutierr wrote:
>
>
> On Oct 17, 11:58 am, Russell Keith-Magee
> wrote:
>> On Sat, Oct 16, 2010 at 12:45 AM, Russell Keith-Magee
>>
>> I should also be able to port the tutorial before I commit -- which,
>> barring objecti
On Tue, Oct 19, 2010 at 10:29 AM, Will Hardy wrote:
> Whilst I agree that messing with contrib.auth is likely to break
> something and create more work, I think it would be good for Django if
> everyone in the Django community went and needlessly ported their real
> world views to CBV, to expose a
On Wed, Oct 20, 2010 at 1:25 AM, Valentin Golev wrote:
> Hello,
>
> I'm trying to use brand new Class Based Views and I have a question
> about implementation.
>
> Let's take a look at SingleObjectMixin.get_object():
> http://code.djangoproject.com/browser/django/trunk/django/views/generic/detail.
On Wed, Oct 20, 2010 at 6:01 PM, Valentin Golev wrote:
> Awesome, thank you!
>
> I've asked about @login_required and class based views in
> django-users, and I'd like to ask here: are something like
> LoginRequiredMixin's planned?
No, nothing like that is planned. This is a situation were decora
On Wed, Oct 20, 2010 at 6:43 PM, Klaas van Schelven
wrote:
> Hi,
>
> I'm not sure I'm following protocol here, but here it goes...
The best way to report this is to open a ticket [1] which describes
the problem in detail (which is what you've done here). This ensure
that we have a formal way of t
1501 - 1600 of 2850 matches
Mail list logo
