Hi,
I am Vivek Narayanan, a sophomore undergraduate student from India. I
am interested in contributing to the Django project, through GSoC
(Google Summer
of Code) or otherwise. I have been using Django for a while and have
developed a few applications on social
networking sites . I have
On Feb 3, 3:07 am, Gabriel Hurley wrote:
> Hi Vivek,
>
> It's great to hear you're interested in contributing! This year's GSOC is
> just getting underway and while Django will likely participate as it has in
> years past, we're not quite at that stage yet.
>
> However, if you're serious about G
Hi,
I am new to the Django community and I would like to implement a patch
for the ticket #8809 - "Better error message when can't import url
callback".
http://code.djangoproject.com/ticket/8809
This ticket basically requires the error message, when a callback
function in urlpatterns is not foun
Hi,
I was looking at the ticket at http://code.djangoproject.com/ticket/15040
in which 0 or 1 are returned instead of boolean values in a
BooleanField when MySQL is used with select_related(). Since MySQL
handles them as 0 or 1, they need to be converted.
>From my understanding, when select_relat
Hi,
I am Vivek Narayanan, an undergrad student at IIT, Varanasi in India
and am interested in participating in this year's SoC
Problem
Django provides a serialization framework that is very useful for
loading and saving fixtures, but not very flexible if one wants to
provide a
def meta2_pk(self, model):
'''This method is not required to be overridden as a default
method would be provided'''
def meta2_model(self, model):
...
In XML
class XMLSerializer(Serializer):
mode = "xml"
wrap_fields = "fi
piquemal wrote:
> Ok ... I have to admit I was not very clear. Here is what I meant,
> illustrated with some code examples :
>
> http://readthedocs.org/docs/django-serializers-draft/en/latest/index
>
> These are my "dream" django-serializers !
>
> On Mar 1
On Mar 6, 11:54 am, Russell Keith-Magee
wrote:
> On Sun, Mar 6, 2011 at 2:41 PM, Vivek Narayanan wrote:
> > @Sebastien: I got your point about using a dict as an intermediate
> > structure and the use of recursion, and I looked at your
> > implementation which is somew
On Mar 6, 11:54 am, Russell Keith-Magee
wrote:
> On Sun, Mar 6, 2011 at 2:41 PM, Vivek Narayanan wrote:
> > @Sebastien: I got your point about using a dict as an intermediate
> > structure and the use of recursion, and I looked at your
> > implementation which is somew
On Mar 8, 3:14 pm, Tom Evans wrote:
> Splitting down your project into small chunks will also demonstrate to
> people reading your proposal that you understand the subject matter,
> and they can have a high confidence of the project being delivered.
Thanks, I didn't know this and I don't have
Integrate with Models API and field options.
3. Add permission_level argument to serialize().
Weeks 9 - 10
1. Write documentation for the project and provide many examples.
2. Write a few tutorials on how to use the framework.
3. Write some project-level tests, do some extensive final testin
>From a previous discussion on this list (
http://groups.google.com/group/django-developers/browse_thread/thread/2da69b9e24cf3438/17d87e3b27d4395d
) I gather that modifying the field options of a Model is not
desirable due to a loss in orthogonality. Here is a modified
permissions framework for ser
> I also haven't seen any proposals or examples of how I'd use the API as
> an end user - are people going to be able to register serialisers to
> models (since they're apparently tied to specific models anyway)?
There will be different types of serializers like JSONSerializer,
YAMLSerializer, XML
Hi Russ,
Thanks for the long reply and all the suggestions. My comments are
inline.
> What if you need to support both? e.g.,
>
>
> the bar value
>
>
> It seems to me that you would be better served providing a way to
> annotate each individual metadata value as (and I'm bikeshedding a
> nam
Hi Russ,
Thanks for the suggestions once again, I've thought of changing the
model for handling nested fields.
Each model can have a no of serializers, and they can be plugged in to
other serializers
and in this way nested models can be handled instead of cycling
through a tree of arbitrary depth
Hi,
I've added a patch that provides functionality for selecting a custom
manager in a reverse relation , rather than the default manager. For
example:
author = Author.objects.get(id=1)
# Selects the manager 'foobar' of Post.
mgr = author.post_set.managers("foobar")
ht
e changed. In the tests there is an example
does this.
>
> Cheers.
> Tai.
>
> On Oct 3, 3:25 pm, Vivek Narayanan wrote:
>
>
>
>
>
>
>
> > Hi,
>
> > I've added a patch that provides functionality for selecting a custom
> > manager i
17 matches
Mail list logo
