This message is inappropriate for this list. Before sending mail to
Django discussion lists in the future, please read up on the
difference between the django-developers list and the django-users
list.
--
"Bureaucrat Conrad, you are technically correct -- the best kind of correct."
--
You re
First, here's the problem I'm having, and then I'll bring up my
request. I have a model that looks like this (using dev version):
class SecretModel(models.Model):
some_unique_field = models.CharField(max_length=25, unique=True)
# Notice this is unique.
class MyModel(models.Model):
secret_
On Fri, Mar 12, 2010 at 5:16 AM, ab3 wrote:
> Hello
>
> I am a cs student from belgium. I worked on the camera module of
> pygame for last years gsoc.
> I have used Django for 2 projects and would like to contribute as part
> of gsoc.
> I have taken a look at the SummerOfCode2010 page, and I am in
Hello
I am a cs student from belgium. I worked on the camera module of
pygame for last years gsoc.
I have used Django for 2 projects and would like to contribute as part
of gsoc.
I have taken a look at the SummerOfCode2010 page, and I am interested
and capable to do
the folowing projects:
* auth
This was the initial question:
On Feb 26, 8:11 am, Jared Forsyth wrote:
> I have been looking around for a way of managing user-configurable
> application settings
In this discussion we must IMHO different between "low-level
settings", "admin configurable settings" and "user configurable
settin
On Wed, Mar 10, 2010 at 6:31 PM, Matt Boersma wrote:
> On Wed, Mar 10, 2010 at 7:51 AM, Brian Rosner wrote:
>>
>> On Mar 10, 2010, at 7:16 AM, Joan Miller wrote:
>>
>>> It's a disaster from the maintenance view point. If it were not so,
>>> then people would not be proposing to refactor the setti
I'd suggest using PasteDeploy:
http://packages.python.org/twod.wsgi/manual/paste-factory.html
I can't see a reason to reinvent the wheel with a Django-specific
thing, while this widely used method is rock-solid. It's the one used
in frameworks like Pylons and TurboGears,
On Feb 26, 7:11 am, Jared
On 11/03/10 01:05, Russell Keith-Magee wrote:
We have an incentive to fix it too -- #12977 points out that Django's
own test suite runs foul of this problem.
Ah, that's not good.
Just documenting the problem isn't really a solution, IMHO. MySQL is
the fly in the ointment here, because it