Fellow Reports -- March 2019

2019-03-21 Thread Carlton Gibson 
Hi all. 


Calendar Week 10 -- ending 10 March.


Triaged:

https://code.djangoproject.com/ticket/30238 -- Exception when saving model 
created with string for DateField (Invalid)
https://code.djangoproject.com/ticket/30233 -- Add 
get_queryset_with_parent_obj to InlineModelAdmin to support access 
parent_model's instance (wontfix)



Reviewed:

https://code.djangoproject.com/ticket/30226 -- Add base authentication 
backend to ease custom backend creation.
https://code.djangoproject.com/ticket/30237 -- Admin check for 
AuthenticationMiddleware should allow subclasses
https://code.djangoproject.com/ticket/30242 -- Double spaces before 
limit/offset clause in as_sql() of SQLCompiler
https://code.djangoproject.com/ticket/30186 -- Show applied datetime in 
showmigrations
https://code.djangoproject.com/ticket/29956 -- Allow formset form widget 
override for the ORDER field
https://code.djangoproject.com/ticket/30014 -- Initialising disabled 
ModelChoiceField yields 'Select a valid choice'-error despite 
initialised option being valid
https://code.djangoproject.com/ticket/29834 -- Union queryset with ordering 
breaks on ordering with derived querysets
https://code.djangoproject.com/ticket/30064 -- Admin search with a null 
character crashes with "A string literal cannot contain NUL (0x00) 
characters." on PostgreSQL




Calendar Week 11 -- ending 17 March.


Triaged:

https://code.djangoproject.com/ticket/30249 -- Deprecate re-raising view 
exceptions from test client in tests. (wontfix)
https://code.djangoproject.com/ticket/30248 -- Implement case insensitive 
fields in Sqlite (needsinfo)
https://code.djangoproject.com/ticket/30247 -- ModelMultipleChoiceField Bug 
- Initial Values has to be in queryset, does not make sense (Invalid)
https://code.djangoproject.com/ticket/30245 -- Run tests matching a filter 
(Python 3.7 -k option) (Accepted)



Reviewed:

https://code.djangoproject.com/ticket/30172 -- Incorrect migration applying 
for new Meta.constraints/indexes and field check/unique or 
unique/index_together constraints with same fields for postgres.
https://code.djangoproject.com/ticket/30199 -- get_or_create documentation 
encourages unsafe usage
https://code.djangoproject.com/ticket/30064 -- Admin search with a null 
character crashes with "A string literal cannot contain NUL (0x00) 
characters." on PostgreSQL
https://code.djangoproject.com/ticket/30014 -- Added model instance cast in 
ModelChoiceField.to_python().
https://code.djangoproject.com/ticket/30237 -- Admin check for 
AuthenticationMiddleware should allow subclasses
https://code.djangoproject.com/ticket/30237 -- admin check for 
AuthenticationMiddleware should allow subclasses



Kind Regards,

Carlton


-- 
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/3c3ddbcb-0725-4068-9aab-cd18ff179ca7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: GSoC Proposal

2019-03-21 Thread Carlton Gibson 
Also, sorry, this was the key thread here, plus links 
therein 
https://groups.google.com/d/topic/django-developers/zfred27yVPg/discussion

On Thursday, 21 March 2019 16:27:14 UTC+1, Carlton Gibson wrote:
>
> Hey Marcio. 
>
> If you can demonstrate that your abilities are sufficient in your 
> proposal, I'm sure we can mentor you through the pull request bit. (It's 
> just "contributor" implies knowledge of the internals, and the ORM **is** 
> the scariest bit, so... it's a bit 😬 this close to starting.) 
>
> You've read the contributing guide right, and had a mooch around? Jump in! 
> https://docs.djangoproject.com/en/dev/internals/contributing/
>
>
> On the Timeline 
>  applications 
> go from 25/3 to 9/4 so there's time to work on a draft, but Tim's right, we 
> do need that effort. 
>
> Standout areas for me:
>
> 1. So we ship a JSONField. With SQLite in mind, most people can't use it, 
> so we need a How-To of some kind on compiling SQLite   with the json1 
> extension and putting it in the right place so Python can find it. 
> 2. For the SQLite PoC, I'd like to see a more aggressive timeline right at 
> the beginning. The base field with save and load shouldn't be Too Hardâ„¢ 
> (c.f. jsonb.py 
> 
> )
>
> The issue is (3) the lookups and how to handle integrating those with the 
> existing postgres ones, the MySQL package and, the Oracle example. 
> A decent sketch of an answer there and we have a proposal I think.  (Maybe 
> it's an simple as `as_sqlite()`, `as_oralce()` etc, as with the existing 
> functions implementations, but...) 
>
> Kind Regards,
>
> Carlton
>
>

-- 
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/0f9f5f98-a3ae-49e4-8da3-443191e56e78%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: GSoC Proposal

2019-03-21 Thread Carlton Gibson 
Hey Marcio. 

If you can demonstrate that your abilities are sufficient in your proposal, 
I'm sure we can mentor you through the pull request bit. (It's just 
"contributor" implies knowledge of the internals, and the ORM **is** the 
scariest bit, so... it's a bit 😬 this close to starting.) 

You've read the contributing guide right, and had a mooch around? Jump 
in! https://docs.djangoproject.com/en/dev/internals/contributing/


On the Timeline  
applications 
go from 25/3 to 9/4 so there's time to work on a draft, but Tim's right, we 
do need that effort. 

Standout areas for me:

1. So we ship a JSONField. With SQLite in mind, most people can't use it, 
so we need a How-To of some kind on compiling SQLite   with the json1 
extension and putting it in the right place so Python can find it. 
2. For the SQLite PoC, I'd like to see a more aggressive timeline right at 
the beginning. The base field with save and load shouldn't be Too Hardâ„¢ 
(c.f. jsonb.py 

)

The issue is (3) the lookups and how to handle integrating those with the 
existing postgres ones, the MySQL package and, the Oracle example. 
A decent sketch of an answer there and we have a proposal I think.  (Maybe 
it's an simple as `as_sqlite()`, `as_oralce()` etc, as with the existing 
functions implementations, but...) 

Kind Regards,

Carlton

-- 
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/11826bbe-53cc-412c-8003-009031cbb09c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: GSoC 2019 proposal - Easy Ethereum Blockchain integration

2019-03-21 Thread Carlton Gibson 
Hi Diego. 

> Do you have any suggestion for bringing this proposal into GSoC's scope?

No. Sorry. 🙂

Django is a web framework. So stuff in that area would be in-scope. 

Likely it's just my lack of imagination but, I think blockchain is a 
totally different area of tech. 
Equally if you'd have suggested "django-tensorflow" (say) I'd guess I'd 
think, "good luck but not for Django itself". 

I hope that makes sense. 

Kind Regards,

Carlton

-- 
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/cff57ad7-b351-424b-867c-3678bf06bfff%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Django 2.2 release candidate 1 released

2019-03-21 Thread Mohammad Etemaddar 
Ryan and Adam, Thank you very much.
The links was so helpful.
I liked to find the best way to contribute.

Sincerely,
Mohammad Etemaddar



On Wed, Mar 20, 2019 at 7:39 PM Adam Johnson  wrote:

> Hi Mohammed,
>
> Thanks for making a suggestion, but this is not the thread to bring such
> an issue up on. If you want to make a suggestion, it's best to make a new
> thread.
>
> Ryan is also right, 2.2 is feature frozen, so it won't be possible to make
> such a change, only to fix bugs before it gets its full release.
>
> As to the change you are suggesting, it is not backwards compatible.  It's
> a good idea to read the contributing documentation (
> https://docs.djangoproject.com/en/dev/internals/contributing/ ) and
> importantly the deprecation policy (
> https://docs.djangoproject.com/en/dev/internals/release-process/#internal-release-deprecation-policy
> ) before suggesting something of such magnitude.
>
> Hope that helps,
>
> Adam
>
> On Wed, 20 Mar 2019 at 16:03, Ryan Hiebert  wrote:
>
>> That won't be possible, Django 2.2 has been feature-frozen for a while
>> now. You might want to follow the following issue which is related to what
>> you're suggesting.
>>
>> https://code.djangoproject.com/ticket/10227
>>
>> On Wed, Mar 20, 2019 at 10:52 AM Mohammad Etemaddar <
>> mohammad.etemad...@gmail.com> wrote:
>>
>>> Is it possible to have this option in Django 2.2?
>>> When we select a OneToOne object by related_name, rises DoesNotExists
>>> when have no object related.
>>> Is it possible to add the behaviour to return None instead of
>>> DoesNotExists?
>>>
>>> Thank you
>>>
>>> On Monday, March 18, 2019 at 12:33:15 PM UTC+3:30, Carlton Gibson wrote:

 We've made the final (hopefully) release on the way to Django's next
 major release, Django 2.2! Check out the blog post:
 https://www.djangoproject.com/weblog/2019/mar/18/django-22-rc1/

>>> --
>>> 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/ba861ea5-8916-4293-82c0-89461418af89%40googlegroups.com
>>> 
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>> --
>> 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/CABpHFHR1H%3Dii6tQD9f7MULmxNvTuoCKCC8b1tnOsO06Bi7QcFQ%40mail.gmail.com
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
> --
> Adam
>
> --
> 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/CAMyDDM30Z4LR%2BMpXKzEh7vNoQPo8Cnn7VcNxbyNfAa4jE4tQGg%40mail.gmail.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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/CALJt1nuSTUwf-CQE64DGZNBuD2_aKGbrArSJXjFEuhQRce8sUw%40mai