On Wed, Jul 2, 2008 at 1:10 PM, Paul Kenjora <[EMAIL PROTECTED]> wrote:
> So whats the best way to get involved in proving myself to the group? Are
> there bugs I can pick up, code I can contribute?
At the moment, all eyes are focused on getting Django 1.0 out the door
in early September. The
Please send usage questions to django-users - this list is for the
development of django itself.
--
Collin Grady
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group,
Sounds good, I've been porting the patch since version 0.95 on my own
personal blog, comments seem fairly positive. I've also been a contributing
community member for over a year, as well as having implemented close to 12
sites in Django over the past year with a few million hits this year alone.
On Wed, Jul 2, 2008 at 2:56 PM, George Vilches <[EMAIL PROTECTED]> wrote:
> On Jul 2, 2008, at 1:24 PM, Paul Kenjora wrote:
>
>> I understand the resistance but you've got demand, you've got a
>> willing developer, and you've got a clean fix that significantly
>> improves the adaptability of the
> I could clean this up as a patch to the GIS branch, but there seems to
> be some confusion as to whether such functionality should be in the
> core product.
>
> What is the right way forward here?
>
File a ticket with your patch -- I'm +1 because it doesn't make sense
to support GPolygon and
Hi,
right now I'm working on one model and it looks like this
class Area(models.Model):
region = models.CharField(max_length = 2, choices =
SLOVAK_REGION_CHOICES,
radio_admin = True, db_index = True, blank = True, null = True)
city = models.CharField(max_length = 4,
The Google maps creation facility in the GIS branch does not support
the display of points (only polylines and polygons).
I have a working version that supports points and displays them as
GMarkers on the map, which is in IMHO just a straightforward extension
of the existing model to points.
On Jul 2, 2008, at 1:24 PM, Paul Kenjora wrote:
> I understand the resistance but you've got demand, you've got a
> willing developer, and you've got a clean fix that significantly
> improves the adaptability of the framework. What better reason
> would you need?
Someone who has a
Thanks Brian,
Reposted:
http://groups.google.com/group/django-users/t/2ccf2bb1dc06058e
On Jul 2, 8:47 am, Brian Rosner <[EMAIL PROTECTED]> wrote:
> On Jul 2, 2008, at 9:08 AM, John Boxall wrote:
>
>
>
> > But in NFA - it seems the save method isn't called!
>
> It works for me. If the print
On Wed, Jul 2, 2008 at 1:24 PM, Paul Kenjora <[EMAIL PROTECTED]> wrote:
> Reasons why an alternate backend or view is not good:
> 3. Maintaining my own back end, means others are doing the same, again poor
> re-use.
Not if you:
1. Write it well
2. Distribute it freely
3. Make its presence known
Right, but it makes me think that if this has come up before its not a minor
feature request. The fact that huge numbers of well known sites are using
email based authentication suggests its time for the 4 lines of code to be
added to contrib/auth. Files in contrib are not written in stone.
I
Paul,
I believe this issue has been brought up in various ways before. I'd
suggest searching the list archives and old closed tickets. You'll
likely find your answer there.
More generally, there is already a mechanism in place to override the
default behavior and implement your own (building
On Jul 2, 8:48 am, "Paul Kenjora" <[EMAIL PROTECTED]> wrote:
> I've been using Django for a while and recently started contributing to the
> trunk. Previously I ran my own branch but sooner or later that gets
> tiresome. So I created a ticket the other day:
>
>
I've been using Django for a while and recently started contributing to the
trunk. Previously I ran my own branch but sooner or later that gets
tiresome. So I created a ticket the other day:
http://code.djangoproject.com/ticket/7591
The ticket suggests a patch to contrib/auth that will allow
On Jul 2, 2008, at 9:08 AM, John Boxall wrote:
>
> But in NFA - it seems the save method isn't called!
>
It works for me. If the print statement is not working then see about
tracking it down and post a detailed ticket with what is happening.
Also you will want to make sure you are
On Wed, Jul 2, 2008 at 7:17 AM, Arien <[EMAIL PROTECTED]> wrote:
>
> Can we get back to our regular program now and move personal problems
> to private communication, please? Thank you.
Insofar as referencing particular individuals goes, I agree. I should
have raised any issues with particular
On Wed, Jul 2, 2008 at 10:47 AM, Steve Holden <[EMAIL PROTECTED]> wrote:
> Rob van der Linde wrote:
> > I see there is now a link to the registration page when you go to file a
> > ticket, but why not put it on page where the login/settings links are
> > (just underneath the search box). This is
Hey Marc - that's what I thought!
But in NFA - it seems the save method isn't called!
For instance:
class ModelUserAdmin(admin.ModelAdmin):
form = ModelUserForm
...
class ModelUserForm(forms.ModelForm):
def clean(self):
# This method will successfully be
Eric wrote:
> Well, you can teach someone to fish without telling them to "get an
> f'n fishing pole".
>
>
"Give a man a fish and he will eat for a day. Teach him how to fish and
for the rest of his life he will bore you with stories about the one
that got away".
regards
Steve
Rob van der Linde wrote:
> I see there is now a link to the registration page when you go to file a
> ticket, but why not put it on page where the login/settings links are
> (just underneath the search box). This is where it is by default in Trac
> and people might expect to see it there, like I
On Wed, Jul 2, 2008 at 9:48 PM, vcc <[EMAIL PROTECTED]> wrote:
> I port MS SQL pyodbc backend (django-pyodbc) to newforms-admin r7671, tested
> on ubuntu 8.04 and with SQL Server 2005.
> I found sql server need convert boolean value to integer (BooleanField), so
> need add a new feature like
I port MS SQL pyodbc backend (django-pyodbc) to newforms-admin r7671, tested on
ubuntu 8.04 and with SQL Server 2005.
I found sql server need convert boolean value to integer (BooleanField), so
need add a new feature like 'needs_bool_to_integer' to DatabaseFeatures,
deafult to False.
Since
Can we get back to our regular program now and move personal problems
to private communication, please? Thank you.
Arien
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this
The guy is rude. I never go in the IRC channel to help because he's
there being an ass.
The reason why I fell in love with Django way back in 2005 was because
of the community in #django and I'm worried that he's stunting
adoption because he's turned the channel into #linux.
E.
On Jul 2, 7:41
May be better way to use ``OneToOneField`` with proper
``related_name`` like "profile" for example. Than profile can be
accessed very simple ``user.pofile``. and its creation machinery leave
to profile app author?
On Jul 2, 12:38 pm, David Danier <[EMAIL PROTECTED]> wrote:
> This basically
Russell Keith-Magee wrote:
> On Tue, Jul 1, 2008 at 5:25 PM, Kenneth Gonsalves
> <[EMAIL PROTECTED]> wrote:
>> Let him be as rude as he wants, as long as he is there.
>
> Lets stop this idea before it grows legs. One of the strengths of
> Django is the community, and one of the reasons the
On Tue, Jul 1, 2008 at 5:25 PM, Kenneth Gonsalves
<[EMAIL PROTECTED]> wrote:
>
>Let him be as rude as he wants, as long as he is there.
Lets stop this idea before it grows legs. One of the strengths of
Django is the community, and one of the reasons the community is
strong is because it is
On Wed, Jul 2, 2008 at 12:55 AM, Kenneth Gonsalves
<[EMAIL PROTECTED]> wrote:
> actually this debate belongs on django-users (which is why I put in
> my 2 paise) - I think if taken there we can get a real measure of the
> pros of his help against the cons of his curtness at times (I
> wouldn't
Sure,
just remember to return
super(YourModelForm, self).save(commit)
in it.
On Jul 2, 9:10 am, John Boxall <[EMAIL PROTECTED]> wrote:
> Hi everyone!
>
> I'm just trying out newforms admin - it's fantastic. I can't wait
> until this makes it's way into trunk -
>
> A question -
> I'd like to
On Tue, Jul 1, 2008 at 9:00 PM, Waylan Limberg <[EMAIL PROTECTED]> wrote:
>
> On Tue, Jul 1, 2008 at 8:28 PM, Arien <[EMAIL PROTECTED]> wrote:
>>
>> On Tue, Jul 1, 2008 at 6:10 PM, Waylan Limberg <[EMAIL PROTECTED]> wrote:
>>>
>>> On Tue, Jul 1, 2008 at 5:59 PM, David Durham, Jr.
>>> <[EMAIL
This basically started as a ticket suggesting adding some way to create
a default profile for users which don't have one, moving the need to
catch DoesNotExist-exceptions out of the applications using get_profile().
-> http://code.djangoproject.com/ticket/7584
julien did suggest some
Hi everyone!
I'm just trying out newforms admin - it's fantastic. I can't wait
until this makes it's way into trunk -
A question -
I'd like to add custom behavior when a object is saved in the admin
console.
I'm following this example of how to add custom behaviour to validate
an object:
Hi,
On Wed, 02 Jul 2008 05:55:26 +0200, Gary Wilson Jr.
<[EMAIL PROTECTED]> wrote:
> Jeremy Dunck wrote:
[Pagintor problems]
>> Is there some other way we can point the gun away from our foot?
>
> I, for one, would be in favor of doing away with QueryPaginator and
> bringing back the
33 matches
Mail list logo
