Re: Google Summer of Code 2019

Google doesn't accept purely documentation projects for GSoC IIRC) but might be achievable if merged in parts. @Parth I am Django's GSoC fellow for 2016. If there is any way I could help you, feel free to reach me out <https://gist.github.com/akki/b438292c2c3cf199012f#5-about-me>.

Re: Introduction GSoC

Also, if Django does participate in GSoC this year, they'll have an ideas page for it eventually similar to something like this - https://code.djangoproject.com/wiki/SummerOfCode2018. The best thing that you can do today to improve your chances is start contributing! -- You received this mess

Proposal on Custom Indexes - Google Summer of Code

Hi My name is Akshesh Doshi (akki). I am a student at Indian Institute Of Technology, Roorkee (IITR). I have been contributing to Django <https://github.com/django/django/pulls/akki> for quite some time now and my experience has been really great till now. I found the community to be

Re: Proposal on Custom Indexes - Google Summer of Code

odel, the model can inject itself into the > > index, or the schema editor can use the originating model to get data it > > needs. No need to pass the model into the index type I think. Regarding > the > > name, I'm unsure if I prefer a name=Index() or an Index(na

Re: Proposal on Custom Indexes - Google Summer of Code

> Would you be able to support partial indexes as well? I am not sure if I would be able to squash it in my GSOC timeline, but yes, I will definitely incorporate it (afterwards, if not during my GSOC). It should not be very hard to implement once I am able to make functional indexes work.

Re: Proposal on Custom Indexes - Google Summer of Code

> What about calling the attribute something like "constraints" similar to > how it's done in SQLAlchemy [1]? For now the attribute can just contain a > list of Index() instances but that would also lay grounds for supporting > check constraints and other related table level options. > Since

Re: Proposal on Custom Indexes - Google Summer of Code

Hi I have updated my proposal <https://gist.github.com/akki/b438292c2c3cf199012f> and completed the timeline. I saw how expressions work and now have a clear idea of how they would be used in indexes - I have added a short description of the same in my proposal. Please have a look. I

Re: Proposal on Custom Indexes - Google Summer of Code

dexes feel more like a "Meta" property to me. Constraints can also be added to Meta (maybe merged together with indexes) whenever they arrive, but I don't how soon they will be included. Regards Akshesh Doshi (akki) On Monday, 14 March 2016 12:53:30 UTC+5:30, Anssi Kääriäinen wr

Re: Proposal on Custom Indexes - Google Summer of Code

> > > you can't have identical indexes defined in multiple ways with the same > names. > Yes, I will be checking for the duplications at the autodetector level itself. We need to take care that no two indexes are for the same fields, and none of them have a clashing name. On such an occurrenc

Re: Proposal on Custom Indexes - Google Summer of Code

Hi Tim Thanks for the feedback. Instead of aiming for one huge patch to be merged at the end of the summer, > I'd suggest to think about whether you can break up the work in chunks that > can be merged incrementally. This should decrease the risk that comes with > a huge patch going stale and

Re: Proposal on Custom Indexes - Google Summer of Code

Hi I had updated my proposal to include the various points that were discussed earlier in this thread. I have now also incorporated the changes that were recently suggested by Tim. Thanks -- You received this message because you are subscribed to the Google Groups "Django developers (Contri

Re: Proposal on Custom Indexes - Google Summer of Code

Hi I have submitted my proposal on GSoC's website. You can find it at https://summerofcode.withgoogle.com/serve/5167032660131840/. It would get locked (from any further editing) at 25 March 19:00 UTC (which is almost 11 hours from now). -- You received this message because you are subscribed

Re: Proposal on Custom Indexes - Google Summer of Code

> > > That is a bit too strict; sometimes it does make sense to provide more > than > one kind of index on one field. As a trivial example, you may want to > support > case-sensitive uniqueness as well as case-insensitive search (say, for > user- > names). > Ohh yes definitely, I meant no t

GSoC community bonding period Update

://gist.github.com/akki/73e7b0b7098e32594237749eb79a0960 Other than that, I was trying to solve a couple of bugs that I had found (but haven't found the fix); one of which I have reported recently - https://code.djangoproject.com/ticket/26624. I will report the other one as well soon. I worked on

Re: Should we require pytz for timezone support in Django?

Corresponding ticket - #26622 On Tuesday, 17 May 2016 05:51:29 UTC+5:30, Josh Smeaton wrote: > > While writing timezone tests for > https://github.com/django/django/pull/6243 I ran into some issues where > pytz seemed to be required for just about ev

Re: Should we require pytz for timezone support in Django?

Corresponding ticket - #26622 . On Tuesday, 17 May 2016 05:51:29 UTC+5:30, Josh Smeaton wrote: > > While writing timezone tests for > https://github.com/django/django/pull/6243 I ran into some issues where > pytz seemed to be required for just about e

Google Summer of Code Updates - Class based indexes

gt; is the ticket corresponding to the current checkpoint. The code can be found at https://github.com/django/django/pull/6726. Regards Akshesh (akki) -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)

Re: Google Summer of Code Updates - Class based indexes

class based index in the Meta class. The code can be seen at https://github.com/akki/django/pull/1/ Regards akki -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this grou

Re: Google Summer of Code Updates - Class based indexes

This week's work on previous PR: - Change in signature of Index class - Write tests for the Index class - Address all issues on PR The previous PR has been merged. Now indexes can be added using the AddIndex migration

Re: Google Summer of Code Updates - Class based indexes

new Index classes! > > On Monday, June 27, 2016 at 6:51:31 PM UTC-4, Tim Graham wrote: >> >> Support for more index types is planned. This is only part 1 of the work. >> Please see https://gist.github.com/akki/7fd50505928dac58dc350e6cb186a404 >> for the timeline. >&

Re: Google Summer of Code Updates - Class based indexes

l/6857> so I will send a PR once indexes are added to Meta class; Current work on my local branch - https://github.com/akki/django/commits/gsoc-indexes-inspectdb On Tuesday, 5 July 2016 11:54:00 UTC+5:30, akki wrote: > >- Restructure index migrations >PR - https://github.c

Re: Google Summer of Code Updates - Class based indexes

Other comments about the issue on the ticket - https://code.djangoproject.com/ticket/26180. Resolved a similar issue that had crept up for Meta.indexes - updated !6857 <https://github.com/django/django/pull/6926> accordingly. On Tuesday, 12 July 2016 14:17:21 UTC+5:30, a

Re: Google Summer of Code Updates - Class based indexes

rdering (ASC/DESC) in class based indexes Somewhat provides the feature requested in #20888 <https://code.djangoproject.com/ticket/20888#comment:10> WIP code on my branch - https://github.com/akki/django/commits/gsoc-indexes-order Modifying introspection of all databases to retu

Re: Google Summer of Code Updates - Class based indexes

the feature is in progress but the introspection-related work is mostly complete. Regards Akshesh(akki) On Tuesday, 26 July 2016 16:47:32 UTC+5:30, Jani Tiainen wrote: > > Hi, > > On 26.07.2016 04:28, akki wrote: > > > >- Fixed #24442 <http://code.djangoproject.c

Re: Google Summer of Code Updates - Class based indexes

ns but haven't started the implementation yet. On Wednesday, 27 July 2016 20:26:38 UTC+5:30, akki wrote: > > Hi Jani > > Thanks a lot for offering help. I did face some issues with the Oracle > setup in the beginning but was able to resolve them yesterday. :) > You are most

Re: Trac spam attack / spam filter reactivated

Hi Recently, I would say since the past week, many of my activities on Trac are being reported as spam. Even trying to add myself to cc takes me to an error page. I got the following message when I last tried to modify a ticket. I was changing the summary of one of the tickets: > > > Submissi

Re: Trac spam attack / spam filter reactivated

ment still > might be considered spam (spammers were completing the captchas to submit > their content). You could look into if there's some other spam prevention > measures in Trac that might be more effective. > > On Saturday, August 6, 2016 at 7:55:18 AM UTC-4, akki wrote: >

Re: Google Summer of Code Updates - Class based indexes

Add *GinIndex* to *contrib.postgres.indexes* Ticket - https://code.djangoproject.com/ticket/27030 PR - https://github.com/django/django/pull/7046 On Tuesday, 2 August 2016 11:12:27 UTC+5:30, akki wrote: > > > >- Add support for column ordering (ASC/DESC) in class based

Re: Google Summer of Code Updates - Class based indexes

Ticket - https://code.djangoproject.com/ticket/27060 PR - https://github.com/django/django/pull/7083 On Tuesday, 9 August 2016 01:30:54 UTC+5:30, akki wrote: > > >- Introduce Meta.indexes - !6857 ><https://github.com/django/django/pull/6857>, #26808 >

Take index type into account in inspectdb command

ally. Please let me know if any other clarification is required on this. Thanks for any help. Regards akki -- 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 r

Re: Google Summer of Code Updates - Class based indexes

Hi The GSoC 2016 period has almost reached it's completion and I have completed my submission. You can find my work submission here - https://gist.github.com/akki/f45c7cf5db30c025f49d862d82dd259a. I enjoyed a lot working on this project and am very excited about everyone making use of

Re: Google Summer of Code Updates - Class based indexes

Thanks a lot Josh! Actually it was this mail <https://groups.google.com/d/msg/django-developers/3c8AvB3X6mk/gbkbbwEuCAAJ> sent by you that made me interested in this idea and later take it up as a project for GSoC, so a big THANK YOU to you. :) Great work, akki! > > > I think

Re: Take index type into account in inspectdb command

ype is a guess" next to unknown > fields) it would be okay. The comment might say the backend doesn't support > index type introspection. Let's put out a call for help to try to get index > introspection done on the other databases for 1.11. > > On Wednesday, Augu

Project idea for GSoC page - Support for expressions in indexes

Hi This is in regards of this thread that was posted a few days back - https://groups.google.com/forum/#!topic/django-developers/8qvrKfZaP2o I think "extending support for expressions into indexes" would make a good candidate for the ideas page. This post

Re: Google Summer of Code 2017

I have posted a project idea here - https://groups.google.com/forum/#!topic/django-developers/QXYalFV90UU. On Saturday, 21 January 2017 02:27:33 UTC+5:30, Tim Graham wrote: > > I've submitted our organization application for this year. > > Anyone interested in mentoring, please indicate your inte

Re: Project idea for GSoC page - Support for expressions in indexes

Ian Foote, > who has contributed some precursor work to make the idea possible > (deconstructed expressions). The current PR is > https://github.com/django/django/pull/8056 > > On Saturday, 4 March 2017 05:39:11 UTC+11, akki wrote: >> >> Hi >> >> This is in

Re: Project idea for GSoC page - Support for expressions in indexes

On Saturday, 4 March 2017 17:42:26 UTC+5:30, Florian Apolloner wrote: > > On Saturday, March 4, 2017 at 6:52:01 AM UTC+1, akki wrote: >> >> @Josh Absolutely correct. I meant since this involves a lot of things (a >> couple of them are listed by Markus on the ticket itself)

Re: Project idea for GSoC page - Support for expressions in indexes

On Sunday, 5 March 2017 01:53:28 UTC+5:30, Florian Apolloner wrote: > > On Saturday, March 4, 2017 at 7:10:57 PM UTC+1, akki wrote: >> >> First of all let's not call the work done by the 1000s of GSoC mentors >> every year "putting down hands and doing nothi