On Sunday, 5 May 2013 01:23:51 UTC+10, Shai Berger wrote:
>
> I've been going through what I've missed on the list, and found this
> 2-month-
> old message that seems to have gone unanswered. I'm sorry for being so
> late to
> the party, but...
>
Thanks all the same for your reply -- better
On Thu, May 9, 2013 at 11:43 PM, Daniele Procida wrote:
> On Mon, Apr 29, 2013, Daniele Procida wrote:
>
> >At the start of the sprints at DjangoCon Europe next month, I'll be
> >holding a workshop called "Don't be afraid to commit" for people who'd
> >like to get involved in Django projects (in
On Thu, May 9, 2013 at 11:30 PM, Carl Meyer wrote:
> Hi Russ,
>
> On 05/09/2013 04:51 AM, Russell Keith-Magee wrote:
> > Great work Carl and Preston! (And everyone else who had a hand in the
> > patch - I know this has been kicking around for a while now)
>
> Thanks for the reminder; I should hav
Thanks, Aymeric. I grabbed the latest Django code and things worked like a
charm.
Now, I have a decision to make: Stay on the Django/Python 3 bleeding edge
or back off to Python 2.7. My project's timeline says I won't release
until after Django 1.6 (even with some slop for slipping releases),
I'd like to have a go at fixing this bug, but I'm not sure where to start.
The problem seems to be that there's only a single instance of the field
per model, so field.model is always the abstract class. I can't see a way
to access the concrete class from the field instance. If the field only ha
On Mon, Apr 29, 2013, Daniele Procida wrote:
>At the start of the sprints at DjangoCon Europe next month, I'll be
>holding a workshop called "Don't be afraid to commit" for people who'd
>like to get involved in Django projects (including Django itself of course).
I've written up the tutorial for
On 05/09/2013 07:50 AM, Andrew Godwin wrote:
> Just want to say that I'm happy with a "fast transition".
>
> Is there a possibility we can detect the case where the tests might be
> broken (how might they be?) and print a helpful error message?
Two kinds of potential breakage:
- The most common
Hi Russ,
On 05/09/2013 04:51 AM, Russell Keith-Magee wrote:
> Great work Carl and Preston! (And everyone else who had a hand in the
> patch - I know this has been kicking around for a while now)
Thanks for the reminder; I should have mentioned that Mahdi Yusuf did
the initial draft patch, based o
Hi Tom,
On 05/09/2013 03:27 AM, Tom Christie wrote:
> * Will it be possible to globally configure the default file/path pattern?
> Jannis's django-discover-runner includes support for a
> `TEST_DISCOVER_PATTERN` - is there anything similar, or just the command
> line `--patterns` option? The us
Just want to say that I'm happy with a "fast transition".
Is there a possibility we can detect the case where the tests might be
broken (how might they be?) and print a helpful error message?
Andrew
On Thu, May 9, 2013 at 11:51 AM, Russell Keith-Magee <
russ...@keith-magee.com> wrote:
>
> On T
On Thu, May 9, 2013 at 5:00 AM, Carl Meyer wrote:
> Hi all,
>
> Preston Timmons and I have been working the last several weeks to get
> the test discovery branch (#17365) ready for merge, and I think we now
> have a pull request ready for consideration:
> https://github.com/django/django/pull/105
Hi Carl,
Excellent, excellent stuff - many thanks to both yourself and Preston.
Couple of questions:
* Will it be possible to globally configure the default file/path pattern?
Jannis's django-discover-runner includes support for a
`TEST_DISCOVER_PATTERN` - is there anything similar, or just
12 matches
Mail list logo
