On Wed, Sep 24, 2008 at 3:54 AM, Brian Beck <[EMAIL PROTECTED]> wrote:
>
> On Sep 23, 3:40 pm, "Adam J. Forster" <[EMAIL PROTECTED]> wrote:
>> Hi Eric,
>>
>> That's what I have done at the moment, but as you say it's a bit of a
>> hack and I'm not sure that I'm happy with it.
>
> I ran across this
On Sep 23, 3:40 pm, "Adam J. Forster" <[EMAIL PROTECTED]> wrote:
> Hi Eric,
>
> That's what I have done at the moment, but as you say it's a bit of a
> hack and I'm not sure that I'm happy with it.
I ran across this bug the other day too; quite annoying. It's ticket
#3310 and there appears to be
Hi Eric,
That's what I have done at the moment, but as you say it's a bit of a
hack and I'm not sure that I'm happy with it.
--
Adam J. Forster
On 23 Sep, 20:33, "Eric Holscher" <[EMAIL PROTECTED]> wrote:
> You can just put a models.py there that is empty. A slight hack, but it
> should work ju
You can just put a models.py there that is empty. A slight hack, but it
should work just fine. (Think of it as __init__.py's big brother :))
Eric
On Tue, Sep 23, 2008 at 2:27 PM, Adam J. Forster <[EMAIL PROTECTED]>wrote:
>
> Firstly I'm sorry if I have posted this in the wrong place, but I
> thi
Firstly I'm sorry if I have posted this in the wrong place, but I
think that it belongs here and not on the django-users list.
Here's my problem, in most of our projects at work we have an app
called 'core' which contains modules that are either used by several
other apps or are not specific/larg
