Yep, commit if you see something that you think is worthwhile. Most of
my commits are random gibberish notes.
In regards to clean. The originaly concept was it would delete the
cache key, reset would refresh it. With memcache you don't need to
delete them for the most part. The methods/organizati
On Jan 23, 2008 7:35 PM, David Cramer <[EMAIL PROTECTED]> wrote:
>
> Some notes I shoved into a commit today:
...
>
> If you understand by gibberish, tell me what you think
I don't understand that gibberish, but am starting to poke at the code a bit.
Quick question on CacheManager.clean's commen
I plan to attend, and I may be able to stay for the sprints this year.
Model inheritance is much on my wants list as well.
On Jan 25, 4:04 pm, "Tom Tobin" <[EMAIL PROTECTED]> wrote:
> Over at The Onion, we're working on a major new project in Django.
> (By "major", well, let's just say that it do
On Jan 26, 2008 3:19 AM, Martin Ostrovsky <[EMAIL PROTECTED]> wrote:
>
> I posted in this in the Users group, but thought somebody here might
> want to see this as well ...
Please don't do this. Django-developers isn't the 'hard questions that
couldn't be answered on django-users' mailing list -
First, sorry for my english.
I think that a very good idea would be having multilingual content. I
searched the google and I found django-multilingual very usefull
(http://code.google.com/p/django-multilingual/), but since it is not
working well with complex models I think that django should nativ
Over at The Onion, we're working on a major new project in Django.
(By "major", well, let's just say that it doesn't end in
"theonion.com" or "avclub.com".) We absolutely *love* Django to
pieces ... especially me, considering that Django's the reason I was
hired. ^_^ Just like everyone, though,
Hey Richard --
On 1/25/08, Wyley <[EMAIL PROTECTED]> wrote:
> So, with this discussion in mind, here's my idea: allow an optional
> user-defined function (call it "map") to be passed to the
> deserialize() function. This function, if passed, will be called with
> DeserializedObjects as an argum
Hi everyone,
Below is an idea I've got for how to make the deserialization
interface a bit more flexible, since I and other users have expressed
a need for it. I am willing to work on implementing this idea
(indeed, I will probably need to, even if it's just for my own
project), but I wanted to
Forgot to add, I'm using Django from trunk, latest revision.
--~--~-~--~~~---~--~~
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@googlegroups.com
To unsubs
I posted in this in the Users group, but thought somebody here might
want to see this as well ...
I'm trying to run syncdb on a clean database (no other tables etc.)
in
postgres. It produces the standard Postgres error:
psycopg2.ProgrammingError: current transaction is aborted, commands
ignored
> *The issue with where documentation should go -- I threw together a
> patch for the auth doc in django/docs/, but the auth document is already
> long. Does the documentation want to live somewhere else, or is it happy
> there?
How about a docs/auth_backends.txt?
Collin
--~--~-~--~
11 matches
Mail list logo
