Re: FYI: added a proper "easy" field to Trac

2011-06-15 Thread Julien Phalip 
On Jun 16, 10:32 am, Julien Phalip  wrote:
> On Jun 16, 3:08 am, Alex Kamedov  wrote:
>
> > Django documentation page Contributing to Django [1] has the same problem
> > too
> > [1]https://docs.djangoproject.com/en/1.3/internals/contributing/
>
> I've fixed the link in the wiki page. The doc is already fixed in
> trunk.

By the way, anybody with a Trac account should have edit access to the
wiki, so feel free to make the change directly next time you find an
inconsistency ;)

Julien

-- 
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 unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Re: FYI: added a proper "easy" field to Trac

2011-06-15 Thread Julien Phalip 
On Jun 16, 3:08 am, Alex Kamedov  wrote:
> Django documentation page Contributing to Django [1] has the same problem
> too
> [1]https://docs.djangoproject.com/en/1.3/internals/contributing/

I've fixed the link in the wiki page. The doc is already fixed in
trunk.

Thanks,

Julien

-- 
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 unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Re: FYI: added a proper "easy" field to Trac

2011-06-15 Thread Russell Keith-Magee 
Hi Alex,

If you open a ticket to report these problems, we'll make sure they get fixed.

Yours
Russ Magee %-)

On Thu, Jun 16, 2011 at 1:08 AM, Alex Kamedov  wrote:
> Django documentation page Contributing to Django [1] has the same problem
> too
> [1] https://docs.djangoproject.com/en/1.3/internals/contributing/
>
> On Wed, Jun 15, 2011 at 10:47 PM, Alex Kamedov  wrote:
>>
>> Wiki StartPage [1] has link on Custom Query page with keyword tag
>> "easy-pickings" with title ""Easy Pickings" Tickets"
>> [1] https://code.djangoproject.com/wiki#Gettinginvolved
>>
>> On Thu, Apr 21, 2011 at 3:39 AM, Jacob Kaplan-Moss 
>> wrote:
>>>
>>> Hi folks --
>>>
>>> Just as a quick FYI, I added an official "Easy pickings" field to Trac
>>> to replace the current keyword-tagging thing. I wanted something a bit
>>> more obvious; figured it couldn't hurt.
>>>
>>> Jacob
>>>
>>> --
>>> 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 unsubscribe from this group, send email to
>>> django-developers+unsubscr...@googlegroups.com.
>>> For more options, visit this group at
>>> http://groups.google.com/group/django-developers?hl=en.
>>>
>>
>>
>>
>> --
>> Alex Kamedov
>> skype: kamedov    www: kamedov.ru
>
>
>
> --
> Alex Kamedov
> skype: kamedov    www: kamedov.ru
>
> --
> 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 unsubscribe from this group, send email to
> django-developers+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/django-developers?hl=en.
>

-- 
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 unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

[GSoC form-rendering] Weekly Check-in

2011-06-15 Thread Gregor Müllegger 
Hi,

I unfortunatelly missed the last weekly check-in. However during this time I
was already on my travel to Amsterdam for DjangoCon Europe. During this
Conference and mostly during the sprints have I spoken to some of the core
contributors to get their opinion about my current form rendering proposal in
person. Idan had some really fantastic ideas about how we can improve on what
Carl and I came up with. He is also a professional designer and really knew
what was bugging him with forms he is writing.

He is also volunteering in writing up a description on how this will look
like and sending it to this mailinglist. So stay tuned and look out for his
message!

I got also some small work done during the sprints in improving the test
suite. Peter van Kampen and I removed the last remaining doctest in django's
test suite. I also mocked the tests for URLField's with verify_exists=True.
They used to access the internet which made the tests fail if you are on a
plane (for example ;-)

So let's see how Idan's wrap up will look like. This will be open for
discussion at the time its posted. If there are no major concerns with it I
will start writing documentation for this approach at the end of next week.

I cannot response to any message in the next five days since I'm involved in a
trip for university and a paper I need to write.

Thanks again to the really well organized Djangocon and espescially the
sprints. It was a great place to get things done.

--
Servus,
Gregor Müllegger

-- 
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 unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Re: FYI: added a proper "easy" field to Trac

2011-06-15 Thread Alex Kamedov 
Django documentation page Contributing to Django [1] has the same problem
too
[1] https://docs.djangoproject.com/en/1.3/internals/contributing/

On Wed, Jun 15, 2011 at 10:47 PM, Alex Kamedov  wrote:

> Wiki StartPage [1] has link on Custom Query page with keyword tag
> "easy-pickings" with title ""Easy Pickings" Tickets"
>
> [1] https://code.djangoproject.com/wiki#Gettinginvolved
>
>
> On Thu, Apr 21, 2011 at 3:39 AM, Jacob Kaplan-Moss wrote:
>
>> Hi folks --
>>
>> Just as a quick FYI, I added an official "Easy pickings" field to Trac
>> to replace the current keyword-tagging thing. I wanted something a bit
>> more obvious; figured it couldn't hurt.
>>
>> Jacob
>>
>> --
>> 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 unsubscribe from this group, send email to
>> django-developers+unsubscr...@googlegroups.com.
>> For more options, visit this group at
>> http://groups.google.com/group/django-developers?hl=en.
>>
>>
>
>
> --
> Alex Kamedov
> skype: kamedovwww: kamedov.ru
>
>


-- 
Alex Kamedov
skype: kamedovwww: kamedov.ru

-- 
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 unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Re: FYI: added a proper "easy" field to Trac

2011-06-15 Thread Alex Kamedov 
Wiki StartPage [1] has link on Custom Query page with keyword tag
"easy-pickings" with title ""Easy Pickings" Tickets"

[1] https://code.djangoproject.com/wiki#Gettinginvolved

On Thu, Apr 21, 2011 at 3:39 AM, Jacob Kaplan-Moss wrote:

> Hi folks --
>
> Just as a quick FYI, I added an official "Easy pickings" field to Trac
> to replace the current keyword-tagging thing. I wanted something a bit
> more obvious; figured it couldn't hurt.
>
> Jacob
>
> --
> 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 unsubscribe from this group, send email to
> django-developers+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/django-developers?hl=en.
>
>


-- 
Alex Kamedov
skype: kamedovwww: kamedov.ru

-- 
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 unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Re: ImportError catching in urlresolvers.py

2011-06-15 Thread Bas Peschier 


On 15 jun, 07:36, Russell Keith-Magee  wrote:
> In this case, the underlying problem is that ImportError is actually
> catching 2 different errors:
>  1) The view specified doesn't exist
>  2) The module containing the view contains an error.

Agreed, in this case this information is lost in get_callable, where
the code does know the difference between 1) and 2), but the exception
raised does not convey that.

It might be a better idea to move the ViewDoesNotExist into the
get_callable function, which get triggered with an AttributeException
or an ImportError when the owning module can be imported. All other
conditions are not caught.

Bas

-- 
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 unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Django on Microsoft IIS

2011-06-15 Thread Yaroslav Govorunov 
Hello!

We have recently developed a solution to install and run Django
applications on Microsoft IIS. Here is the link:  
http://www.helicontech.com/zoo/

Currently IIS 7, 7.5 and IIS Express are supported.  We expect to
demonstrate production level performance in this environment on
release. To use the solution you will need to install Web Platform
Installer, as shown on the page, then click on "Blank Django Project"
and after installation is completed overwrite this blank project with
a real one or start development from this point.

Please help us to beta-test our solution. We need to collect some
statistic on how real Django application is operating in IIS
environment.  Please direct either success or fail reports to
supp...@helicontech.com or tweet using #heliconzoo hashtag:
http://twitter.com/?status=%23heliconzoo


Thanks in advance!

Yaroslav Govorunov
Helicon Tech
http://www.helicontech.com

-- 
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 unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Re: Customizable serialization. (Finally?)

2011-06-15 Thread Tom Christie 
> A suggestion though, is to be able to declare serializers in a
> similar fashion as models or forms.

Actually that's a fair point, yup - the proposal could be made a little 
closer to the existing Forms and Models APIs.
Something along these lines...

class ModelPKField(SerializerField):
def get_value(self, obj, key):
return unicode(obj.pk)

class ModelNameField(SerializerField):
def get_value(self, obj, key):
return unicode(obj._meta)

class ModelFieldSetField(SerializerField):
def get_value(self, obj, key):
return FieldsSerializer().serialize(obj)

class RelatedPKField(SerializerField):
def get_value(self, obj, key):
return unicode(getattr(obj, key).pk)


class FieldsSerializer(Serializer):
"""
Serializes only the fields on a model.
"""
class Meta:
exclude = ('id', 'pk')
default_related_field = RelatedPKField()


class DjangoSerializer(Serializer):
"""
Serializes into the existing django style.
"""
pk = ModelPKField()
model = ModelNameField()
fields = ModelFieldSetField()


-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/django-developers/-/wm9YOnddZ3EJ.
To post to this group, send email to django-developers@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.