On Mon, Oct 26, 2009 at 9:49 PM, Karen Tracey wrote:
> I don't know who maintains or has access to the buildbot machine,
It's me, probably. Buildbot's in bad shape, currently; it's basically
another part-time job just keeping the damn thing running.
I've more or less given up and am working on
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 Mon, Oct 26, 2009 at 8:23 PM, Kevin Teague wrote:
>
> It's Python which doesn't allow dots in the name of a package,
> although it's Django which is putting the name of your project name on
> sys.path. This was intentional, see the django.core.management
> package:
>
># Import the project
Latest trunk is failing:
http://buildbot.djangoproject.com/builders/django-trunk%20debian-
lenny-python2.5-sqlite3/builds/220/steps/test/logs/stdio
But I'm pretty sure that it's a bug in buildbot - the log refers to
two files which shouldn't even exist in that revision of trunk
(.../contrib/cs
It's Python which doesn't allow dots in the name of a package,
although it's Django which is putting the name of your project name on
sys.path. This was intentional, see the django.core.management
package:
# Import the project module. We add the parent directory to
PYTHONPATH to
# avoid s
I see this ticket: Ticket #6510. What if they just used the function
from IfNode?
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-developers@goog
On Mon, Oct 26, 2009 at 3:05 PM, Russell Keith-Magee
wrote:
>
> On Mon, Oct 26, 2009 at 8:46 PM, Waldemar Kornewald
> wrote:
>>
>> On Mon, Oct 26, 2009 at 1:12 PM, Russell Keith-Magee
>> wrote:
>>> To date, sql.Query is the right structure for all Django's supported
>>> backends. It might even
On Mon, Oct 26, 2009 at 8:46 PM, Waldemar Kornewald
wrote:
>
> On Mon, Oct 26, 2009 at 1:12 PM, Russell Keith-Magee
> wrote:
>> To date, sql.Query is the right structure for all Django's supported
>> backends. It might even be the right structure for a non-SQL backend
>> that provides a SQL-like
On Mon, Oct 26, 2009 at 7:42 AM, James Bennett wrote:
> On Mon, Oct 26, 2009 at 6:53 AM, kugutsumen wrote:
>> Support for non-relational databases (AppEngine, #10192) +1
>
> Repeating once again: the voting's over and done with. The proposals
> have been assigned their priorities. Time to move
On Mon, Oct 26, 2009 at 1:12 PM, Russell Keith-Magee
wrote:
> To date, sql.Query is the right structure for all Django's supported
> backends. It might even be the right structure for a non-SQL backend
> that provides a SQL-like query layer (AppEngine possibly falls into
> this category, as might
On Mon, Oct 26, 2009 at 6:53 AM, kugutsumen wrote:
> Support for non-relational databases (AppEngine, #10192) +1
Repeating once again: the voting's over and done with. The proposals
have been assigned their priorities. Time to move on.
--
"Bureaucrat Conrad, you are technically correct -- th
Support for non-relational databases (AppEngine, #10192) +1
See
http://groups.google.com/group/django-developers/browse_thread/thread/fcf501d073ae33f
for reference.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
On Mon, Oct 26, 2009 at 4:52 PM, Waldemar Kornewald
wrote:
>
> On Mon, Oct 26, 2009 at 1:46 AM, Russell Keith-Magee
> wrote:
>> The current query_class will need to change slightly to support
>> multi-db, so anything you implement against that interface will
>> require some rework later on. That
On Mon, Oct 26, 2009 at 1:46 AM, Russell Keith-Magee
wrote:
> The current query_class will need to change slightly to support
> multi-db, so anything you implement against that interface will
> require some rework later on. That said, the fundamental approach
> (i.e., the backend tells you what c
14 matches
Mail list logo
