Hi Elita, On Fri, Feb 6, 2015 at 1:39 PM, Elita Lobo <[email protected]> wrote:
> Hello, > > I am a 3rd year student of NIT Durgapur , India as well as a Gnome > Developer . I have worked on many Python projects as well. I would like to > start contributing to django. > Django does not allow bulk_create of objects with many_to_many field nor > does it allow bulk update. Also it does not call save function which may be > a bit of a problem if the save method has been overriden. I would like to > work on finding a way around to eliminate these limitations. > > Kindly let me know if this is feasible and if I can submit a patch for the > same. > Well, it's probably *feasible*, but not going to be *simple*. If you exclude many-to-many fields, bulk_create() and update() can be implemented with a single SQL call. If you allow m2m fields as well, you're going to need at *least* 1+N calls, where N is the number of m2m fields. I'm not saying it can't be done - prefetch_related has similar 1+N mechanics. However, if you're looking for a simple first issue to tackle, this probably isn't it. Calling save() on update is a completely separate issue. Again, if you follow the mapping from Django ORM API to SQL, you'll understand why save() isn't invoked on update(), and why it would be difficult to make that change. > Also I would be grateful if you could point out a few bugs that could help > me get started with contributing to django. > The list of all open tickets is here: https://code.djangoproject.com/query You can filter this on many different facets - e.g., a topic of interest (database backend, template system); ticket status (e.g., patch needs improvement); or, there's a flag for "easy pickings": https://code.djangoproject.com/query?status=assigned&status=new&easy=1&desc=1&order=id These are tickets that have been evaluated as "easy first tickets" by a reviewer. That doesn't necessarily mean they *will* be easy - it's possible that when you dig into the problem it will turn out to be more complex - but at least on first inspection, they should be. If you want to get involved contributing to Django, I'd also suggest reading our contribution guide: https://docs.djangoproject.com/en/1.7/internals/contributing/ This fills in a lot of details about how our development process works, and has some other suggestions for how to get started contributing. Yours, Russ Magee %-) -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAJxq84_3La1id7KU2LCTAk38g-fgsGwoMwDEMkaE%2B5Mqs9RBqw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
