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

[Florian Apolloner]

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) to do, they can 
> use a helping hand from a student developing full-time.
>

The GSoC program does not allow for something like that. If that would 
happen Markus and Ian would be required to put their hands down and do 
nothing basically.

-- 
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 django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at https://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/b8478fef-b0d8-4dd1-adf4-95eb110f6b31%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

[Tim Graham]

There is probably a summer's worth of work to do outside of the work that's 
already happening, so if you want to add something to the ideas page, that 
sounds good to me.

On Saturday, March 4, 2017 at 12:52:01 AM UTC-5, 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) to do, they can 
> use a helping hand from a student developing full-time.
> It's just a suggestion of mine, they are doing an incredible job and it's 
> totally their call (they can mentor the project as well since they have 
> already come so far with the ticket). :)
>
> Other than that there are many more things related to indexes that are 
> remaining like implementing a RenameIndex migration operation 
> , making db_index use class 
> based indexes under the hood (2nd point of the post mentioned in my last 
> mail), deprecating index_together 
> , bring indexes under 
> inspectdb , etc. which the 
> students can involve in there project. There are even more things to do 
> related to db-indexes than these, checkout the tickets having 
> "db-indexes" in their keywords 
> 
>  
> for them.
>
> This project can be thought more of getting "Django indexes into Spartan 
> mode" than just "extending expressions into indexes" as I had called it 
> earlier, as it would power Django to do much more with indexes via class 
> based indexes. So if it looks good to the community this can be included in 
> the ideas page of Django's GSoC page.
>
> On Saturday, 4 March 2017 07:33:57 UTC+5:30, Josh Smeaton wrote:
>
>> I think Markus is currently working on this idea, along with 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 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 
>>> 
>>>  by 
>>> Josh mentions steps to be followed to accomplish this task in a nutshell 
>>> (1st point had been completed in last year's GSoC). The ticket for the same 
>>> is https://code.djangoproject.com/ticket/26167.
>>> For the complexity of this task I would suggest that it's between 
>>> medium-hard as it requires good knowledge about how both expressions and 
>>> class based indexes work in Django.
>>> As far as mentoring the project is concerned I am currently not in a 
>>> situation to state if I'll be free for the task after a couple of months so 
>>> can't commit on that right now. I'll definitely help out the student with 
>>> any queries if anyone does pick up this project this year.
>>>
>>>

-- 
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 django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at https://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/a6dcdd5c-8fcc-4bbe-8023-707eccf51b1c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: feature request: include optional html_message in send_mass_mail tuple

[Tim Graham]

Hi Michael, it looks like we're not enhancing send_mass_mail() as per the 
docstring [0]: "The API for this method is frozen. New code wanting to 
extend the functionality should use the EmailMessage class directly." 
Perhaps the documentation could be clarified.

[0] 
https://github.com/django/django/commit/d5d2072bbfc38015a93d6e13136c3f1dbf125d87

On Friday, March 3, 2017 at 7:26:48 PM UTC-5, Michael Scheper wrote:
>
> It seems I'm not the only one 
> 
>  
> who wants to include HTML in messages sent via send_mass_mail() 
> . It 
> also seems an easy feature to add; if the tuple has a fifth element, assume 
> it's an html_message.
>
> Actually, I feel like I'm reinventing the wheel by passing it though 
> django.template.loader.render_to_string() 
> ,
>  
> too. I've copied the same six-line function to numerous projects already.
>
> I'm suggesting these features here, as per Requesting features 
> 
>  
> in the docs.
>
> Thanks!
>

-- 
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 django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at https://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/915c59f9-c811-4c6a-94c6-1f1f334f79f2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

[akki]

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) to do, they can 
>> use a helping hand from a student developing full-time.
>>
>
> The GSoC program does not allow for something like that. If that would 
> happen Markus and Ian would be required to put their hands down and do 
> nothing basically.
>

First of all let's not call the work done by the 1000s of GSoC mentors 
every year "putting down hands and doing nothing".
Second of all, since Markus and Ian are actively working on this task and 
there is not requirement of more help to complete it, I (undoubtedly) take 
back this suggestion of mine.
Lastly, if there is no work going on by anybody on the other tickets that I 
mentioned earlier (2nd paragraph of my last mail), I think they can be 
added to the ideas page with everyone's consent.

-- 
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 django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at https://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/37eac965-5b8f-46ab-a4de-b31b446446d2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

[Florian Apolloner]

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 nothing".
>

I am pretty sure I did not say that, please don't put words into my mouth. 
That said, the fact remains that we have to be careful with GSoC since 
students are required to more or less work alone in their area. This has 
been an issue in the past for us (iirc) because the mentors should really 
be like mentors and not "colleagues" with the same workload in the same 
area.

Cheers,
Florian

-- 
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 django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at https://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/6991c37d-3826-4aec-b174-f8bddac4ef2b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Fellow Report - March 4, 2017

[Tim Graham]

Triaged

---

https://code.djangoproject.com/ticket/27882 - Allow template fragment 
caching for unlimited time (accepted)

https://code.djangoproject.com/ticket/27884 - Document that validators 
needs to be an iterable since Django 1.11 (wontfix)

https://code.djangoproject.com/ticket/27888 - Add a button to clear all 
admin filters (accepted)

https://code.djangoproject.com/ticket/27897 - Searching for foreign key's 
pk in the admin crashes with FieldDoesNotExist (accepted)

https://code.djangoproject.com/ticket/27896 - In Django 1.10 when sqlite is 
used and TIME_ZONE=None a django.db.utils.OperationalError error is raised 
when filtering by __date on a DateTimeField (worksforme)

https://code.djangoproject.com/ticket/27893 - Make it possible to disable 
exception re-raising in test client (duplicate)

Authored

--

https://github.com/django/django/pull/8132 - Fixed #27887 -- Fixed URLs 
check crash with namespaced URLs inside non-nonspaced URLs.

https://github.com/django/django/pull/8141 - Fixed #27900 -- Made escapejs 
escape backticks for use in ES6 template literals.

Reviewed/committed

--

https://github.com/django/django/pull/8065 - Fixed #27842 -- Added protocol 
kwarg to GenericSitemap.__init__().

https://github.com/django/django/pull/8115 - Fixed #27862 -- Fixed 
incorrectly quoted table aliases in Subquery SQL.

https://github.com/django/django/pull/8095 - Improve test coverage for 
django.contrib.auth.

https://github.com/django/django/pull/8125 - Fixed #26911 -- Removed 
NoReverseMatch silencing in RedirectView.

https://github.com/django/django/pull/8133 - Fixed #27889 -- Fixed 
incorrect check error if ModelAdmin.ordering refers to 'pk'.

https://github.com/django/django/pull/7763 - Fixed #27656 -- Updated 
docstring verbs according to PEP 257.
https://github.com/django/django/pull/8145 - Refs #27795 -- Removed 
unneeded force_text calls

-- 
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 django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at https://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/1f179c20-e966-44a2-814f-e91af8b75e1e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.