Ticket #29015

[askpriyansh]

Greetings !

I am looking to start contributing to the project, through ticket #29015 
(https://code.djangoproject.com/ticket/29015).

How should the erroneous database-name be handled ? I am planning to abort 
database-creation, with an appropriate error-message on the console. Is that 
the correct way of doing this ? And if it is, what details should be present on 
the console ?

Thanks !
Priyansh Saxena

-- 
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/e5ccacb4-7990-430c-8d74-82013c501514%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Ticket #29015

[askpriyansh]

Hello !

I have made a simple change to the django/db/backends/postgresql/base.py and 
added a NotSupportedError for the database-name. The result of the 
makemigrations command currently looks like this:

Traceback (most recent call last):
  File "manage.py", line 15, in 
execute_from_command_line(sys.argv)
  File "/home/priyansh/django/django/core/management/__init__.py", line 373, in 
execute_from_command_line
utility.execute()
  File "/home/priyansh/django/django/core/management/__init__.py", line 367, in 
execute
self.fetch_command(subcommand).run_from_argv(self.argv)
  File "/home/priyansh/django/django/core/management/base.py", line 288, in 
run_from_argv
self.execute(*args, **cmd_options)
  File "/home/priyansh/django/django/core/management/base.py", line 335, in 
execute
output = self.handle(*args, **options)
  File 
"/home/priyansh/django/django/core/management/commands/makemigrations.py", line 
92, in handle
loader.check_consistent_history(connection)
  File "/home/priyansh/django/django/db/migrations/loader.py", line 274, in 
check_consistent_history
applied = recorder.applied_migrations()
  File "/home/priyansh/django/django/db/migrations/recorder.py", line 61, in 
applied_migrations
if self.has_table():
  File "/home/priyansh/django/django/db/migrations/recorder.py", line 44, in 
has_table
return self.Migration._meta.db_table in 
self.connection.introspection.table_names(self.connection.cursor())
  File "/home/priyansh/django/django/db/backends/base/base.py", line 255, in 
cursor
return self._cursor()
  File "/home/priyansh/django/django/db/backends/base/base.py", line 232, in 
_cursor
self.ensure_connection()
  File "/home/priyansh/django/django/db/backends/base/base.py", line 216, in 
ensure_connection
self.connect()
  File "/home/priyansh/django/django/db/backends/base/base.py", line 193, in 
connect
conn_params = self.get_connection_params()
  File "/home/priyansh/django/django/db/backends/postgresql/base.py", line 155, 
in get_connection_params
"Database names longer than 63 characters are not supported by PostgreSQL. "
django.db.utils.NotSupportedError: Database names longer than 63 characters are 
not supported by PostgreSQL. Please supply a shorter NAME value in 
settings.DATABASES.

However, there are some issues that I would like to address here.

1. Is the NotSupportedError appropriate here ?
2. Should there be a newline after "... supported by PostgreSQL." ?
3. From the info given at 
http://www.postgresql.org/docs/current/interactive/sql-syntax-lexical.html#SQL-SYNTAX-IDENTIFIERS,
 it is possible to modify this default limit of 63 characters. However, this is 
to be done by hacking the source code and recompiling PostgreSQL. How should I 
handle the situation when this limit is modified in the PostgreSQL source-code ?

Any advice, suggestion or comment would be really helpful :)

Thanks !
Priyansh

-- 
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/8640611c-2114-4e10-aebc-3bbe50b430a8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Ticket #29015

[askpriyansh]

Hello Adam !

I created a PR as per your suggestion, and updated the ticket with the 'has 
patch' flag. Please review the patch, and do give your suggestions.

Thanks !
Priyansh

-- 
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/7bb2be66-a9e9-4450-a52e-970138f2bfa6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Ticket #29015

[askpriyansh]

Hello !

I updated the PR as per your comments, and I have run into the problem of 
failing checks, while they run fine on my system. I have fixed the problem of 
flake8 build-failure. However, I am unable to resolve the issue of 
ImportFailure of psycopg2.

Is it because of some environment changes that I have to accommodate ? Do I 
need to supply more information about this ?

Thanks !
Priyansh

-- 
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/70b08dd4-acef-4f53-8b83-559f880d5aed%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Ticket #29015

[askpriyansh]

Hello !

I have updated the PR as per Adam's review. However, I have not changed 
L155 in backends/postgresql/base.py from 

if settings_dict['NAME'] is not None

to

if 'NAME' in settings_dict


*None may be used to connect to the default 'postgres' db. *

*However, "if 'NAME' in settings_dict" prevents KeyError, but would still 
return True if 'NAME' is assigned a 'NoneType'. *

(Referred test_default_name method in tests/backends/base/test_creation.py)

I tried testing Adam's suggestion on this, but it results in the following 
error:

TypeError: object of type 'NoneType' has no len()

The PR is still open and needs review.

Thanks and regards !

-- 
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/a494f2b1-3923-405b-8eed-55f75497a239%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Ticket #29015

[askpriyansh]

Hello !

Sorry for the trouble. I'll keep this in mind.

Thanks
Priyansh

-- 
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/3e6c3317-e064-47eb-8ad0-b92b9a026952%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Want to contribute

[askpriyansh]

Hello !

You can find some info about contributing to Django at this link 
. Look for 
tickets 
marked "easy pickings" 
 for a start. 
The details for writing your first patch can be found here 
.

Regards
Priyansh

On Tuesday, January 23, 2018 at 12:43:44 AM UTC+5:30, Anurudhbalajee 
Srikanthan wrote:
>
> Hi, I want to contribute...can someone suggest me from where to get 
> started ?
>

-- 
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/41295724-90d6-472c-847b-302ae629f6ba%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Ticket #29048

[askpriyansh]

Hello !

I am looking to work on ticket #29048. However, it is still in the 
"Unreviewed" stage, and requires a second-opinion. The description of the 
ticket says:

Func inherits from SQLiteNumericMixin, which added an extra argument to 
as_sqlite: **extra_context. Based on feedback from other developers, it 
seems we should add this argument to each as_vendor method.

If it has already been discussed, is it alright to move the ticket to 
"Accepted" stage now ?

Thanks !
Priyansh

-- 
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/63c46562-0afd-434c-b0df-d3ac2508ef84%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Ticket #29066

[askpriyansh]

Hello everyone !

I have two queries with respect to the ticket #29066 
.

1. Do we need to provide an __neg__ operator for the Sum class, or its 
superclass Aggregate class ? Going by the description in the ticket, the 
operator should probably support all aggregates.
2. Should there be tests for this ? The flag is not set, but I think there 
should be.

Regards
Priyansh

-- 
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/d6cdd454-d0c7-42b9-81a2-fdaccdf2490d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Add slicing notation to F expressions

[askpriyansh]

Hello !

There is a new feature-request in ticket #29049, and some related work has been 
done in PR #9583 (https://github.com/django/django/pull/9583).

Does this require the implementation of the slicing operator using backend 
functions Left, Right and Substring ?

Regards
Priyansh

-- 
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/ce15691c-2baf-42a6-9acc-40da8e331042%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Add slicing notation to F expressions

[askpriyansh]

Hello !

I went through the conversation. Does the ticket #29049 
 looks to add this feature, 
building over the work done in PR #9583 ?

Regards
Priyansh

-- 
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/6e911720-491a-4473-88ce-e43a6e4b646e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Google Summer of Code 2018

[askpriyansh]

Hello !

What is the policy regarding NoSQL datastores being used as backends ? I think 
adding support for something like MongoDB might be good idea.

Regards
Priyansh

-- 
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/7bc40967-81f2-4c2c-9e3d-5231b6ae6889%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Google Summer of Code 2018

[askpriyansh]

Hello !

I thought it would be a good idea as it extends the functionality for 
developers who want to use NoSQL datastores (and possibly, distributed 
datastores like Hive and HBase). 


Would an ODM be a useful feature for Django ? Is there some work in progress 
that aims to develop an ODM ?

Regards
Priyansh

-- 
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/4861087e-3c5e-4fb9-8667-56142ac00f58%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Google Summer of Code 2018

[askpriyansh]

Hello !

That sounds wonderful. I have got some experience with Cassandra and HBase. 
If that seems to be a good candidate for a GSoC project, I'll start 
drafting a proposal. Thanks for the advice !

Regards
Priyansh

On Wednesday, February 14, 2018 at 3:15:56 AM UTC+5:30, Russell Keith-Magee 
wrote:
>
>
> Another approach would be to do what I laid out in this talk at DjangoCon 
> US 2015, following the last Summer of Code student who tackled 
> (tangentially) this problem. 
>
> https://www.youtube.com/watch?v=VgM0qmpHDiE 
>
> That is - finish the modifications needed to Django’s core such that an 
> arbitrary model can register in a way compatible with the Admin and Forms 
> library. This was one of the reasons given for standardising the meta-model 
> framework, but didn’t make it into Daniel’s GSoC project, although he *did* 
> get a proof of concept working that exposed your Gmail inbox in Django’s 
> admin. 
>
> This would allow *any* data backend to expose an interface that is 
> fundamentally compatible with Django - which, really, just means “I want to 
> browse my data in the admin” and “I want to display a form for my model”. 
>
> It won’t allow an arbitrary ORM query to run against an arbitrary “NoSQL” 
> backend - but that’s idea was never going to work anyway. But I don’t think 
> anyone is serious about wanting that, either. All they want is the ability 
> to integrate a non-SQL data source into their basic Django visualisations. 
>
> Yours, 
> Russ Magee %-) 
>
> > On 13 Feb 2018, at 6:48 pm, Curtis Maloney  > wrote: 
> > 
> > On 02/13/2018 09:23 PM, askpr...@gmail.com  wrote: 
> >> Hello ! 
> >> What is the policy regarding NoSQL datastores being used as backends ? 
> I think adding support for something like MongoDB might be good idea. 
> > 
> > Could you elaborate on why you think it would be a good idea? 
> > 
> > I believe every other time the discussion has come up the following 
> points have been made. 
> > 
> > 1. "NoSQL" is not a DB category, it is an anti-category 
> > 2. Because of there there is no common data model, or query languages. 
> > 3. If you limit yourself to just document stores, there is still no 
> common query language [but this can be hidden by code] 
> > 4. Document stores are a really really bad fit for the ORM, as it's 
> designed for the relational model, not document model. 
> > 5. A better approach would be to develop an ODM, which is sufficiently 
> compatible with the ORM you can provide similar tools like ModelForms and 
> ModelAdmin, as well as GCBV. 
> > 
> > If I missed anything, I'm sure someone else will remind me. 
> > 
> > [Also... why is it always MongoDB, instead of something with a solid 
> reputation of reliability and performance?] 
> > 
> > -- 
> > Curtis 
> > 
> > 
> > -- 
> > 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-develop...@googlegroups.com . 
> > To post to this group, send email to django-d...@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/d9e38eeb-eab1-e0db-8d50-54abe6fb1afd%40tinbrain.net.
>  
>
> > 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/47cb28c3-a41c-45ca-9548-5a60e38aae01%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Google Summer of Code 2018

[askpriyansh]

Hello !

I have drafted a project-proposal for the idea that Russell laid out in his 
talk at DjangoCon '15. Here's the link to the draft:

https://gist.github.com/priyanshsaxena/4670cae3d03a7b77a16388601c018460

Looking forward to your suggestions on how best to improve this for a 
concrete GSoC '18 project-proposal.

Regards
Priyansh

On Wednesday, February 14, 2018 at 3:15:56 AM UTC+5:30, Russell Keith-Magee 
wrote:
>
>
> Another approach would be to do what I laid out in this talk at DjangoCon 
> US 2015, following the last Summer of Code student who tackled 
> (tangentially) this problem. 
>
> https://www.youtube.com/watch?v=VgM0qmpHDiE 
>
> That is - finish the modifications needed to Django’s core such that an 
> arbitrary model can register in a way compatible with the Admin and Forms 
> library. This was one of the reasons given for standardising the meta-model 
> framework, but didn’t make it into Daniel’s GSoC project, although he *did* 
> get a proof of concept working that exposed your Gmail inbox in Django’s 
> admin. 
>
> This would allow *any* data backend to expose an interface that is 
> fundamentally compatible with Django - which, really, just means “I want to 
> browse my data in the admin” and “I want to display a form for my model”. 
>
> It won’t allow an arbitrary ORM query to run against an arbitrary “NoSQL” 
> backend - but that’s idea was never going to work anyway. But I don’t think 
> anyone is serious about wanting that, either. All they want is the ability 
> to integrate a non-SQL data source into their basic Django visualisations. 
>
> Yours, 
> Russ Magee %-) 
>
> > On 13 Feb 2018, at 6:48 pm, Curtis Maloney  > wrote: 
> > 
> > On 02/13/2018 09:23 PM, askpr...@gmail.com  wrote: 
> >> Hello ! 
> >> What is the policy regarding NoSQL datastores being used as backends ? 
> I think adding support for something like MongoDB might be good idea. 
> > 
> > Could you elaborate on why you think it would be a good idea? 
> > 
> > I believe every other time the discussion has come up the following 
> points have been made. 
> > 
> > 1. "NoSQL" is not a DB category, it is an anti-category 
> > 2. Because of there there is no common data model, or query languages. 
> > 3. If you limit yourself to just document stores, there is still no 
> common query language [but this can be hidden by code] 
> > 4. Document stores are a really really bad fit for the ORM, as it's 
> designed for the relational model, not document model. 
> > 5. A better approach would be to develop an ODM, which is sufficiently 
> compatible with the ORM you can provide similar tools like ModelForms and 
> ModelAdmin, as well as GCBV. 
> > 
> > If I missed anything, I'm sure someone else will remind me. 
> > 
> > [Also... why is it always MongoDB, instead of something with a solid 
> reputation of reliability and performance?] 
> > 
> > -- 
> > Curtis 
> > 
> > 
> > -- 
> > 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-develop...@googlegroups.com . 
> > To post to this group, send email to django-d...@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/d9e38eeb-eab1-e0db-8d50-54abe6fb1afd%40tinbrain.net.
>  
>
> > 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/63d87409-3a23-4b95-920b-33dfc13bed6b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Update specific keys within nested Django JSONField data

[askpriyansh]

Hello !

I have come up with a solution to #29112 
, using jsonb_set function. 
However, this function is only available from PostgreSQL 9.5, and we need 
to give support for PostgreSQL 9.4 as well.

We can use PL/Python extension to write a custom function. I am planning to 
add the function definition in a class that extends Func, and use it with 
this extension. Is this the correct way of approaching the problem ? Any 
ideas will be welcome. 


Regards
Priyansh


-- 
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/07f23d29-a3fa-4ac8-89df-b7d7a3a66ebf%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Google Summer of Code 2018

[askpriyansh]

Hello !

I am still looking for Track tickets and other references (including 
third-party solutions) to formalise the idea. The work I propose should ideally 
make the process of using any arbitrary backend (like Google App Engine) much 
easier and uniform for every datastore.

The exams will take up no more than ten days (should have clarified this, 
apologies), it's just that they will take place at the start of the period I 
mentioned them in.

I'll do more research and get back to you in this. Meanwhile, ideas from the 
community will be of great help.

Thanks !
Priyansh

-- 
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/475b6c86-d5c8-4bb3-b994-4faae686edbf%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Google Summer of Code 2018

[askpriyansh]

Hello !

Here's the updated version of my proposal: 
https://gist.github.com/priyanshsaxena/4670cae3d03a7b77a16388601c018460. A 
request to the community to spare some time and review this before I put it 
up on the GSoC portal.

I am working on solving some feature-requests, and I've got working 
solutions put as PRs. I have tried to give details of the problem and 
examples of how the project will be useful in the proposal, but I am not 
quite sure on how to demonstrate the understanding of Django. Please do 
give me pointers on this.

Best
Priyansh

On Wednesday, February 21, 2018 at 12:12:44 AM UTC+5:30, Tim Graham wrote:
>
> Hi Priyansh,
>
> Your proposal isn't really detailed enough for me to understand what the 
> outcome of your project would be (I haven't watched Russell's talk that you 
> linked). What are the "big wins"? There are projects like 
> https://github.com/potatolondon/djangae, which allows using Django with 
> Google App Engine. Would your project make something like that much 
> simpler? You'll have to demonstrate a fairly sophisticated level of 
> understanding of Django to convince us that you understand the problems 
> well enough to have a reasonable chance of success.
>
> Regarding your proposed schedule, I'm a bit concerned that you'll have 
> exams for five weeks of the coding period. Students are expected to average 
> 30+ hours/week on their projects. Is that feasible while you're studying 
> for exams?
>
> On Monday, February 19, 2018 at 1:45:22 PM UTC-5, askpr...@gmail.com 
> wrote:
>>
>> Hello !
>>
>> I have drafted a project-proposal for the idea that Russell laid out in 
>> his talk at DjangoCon '15. Here's the link to the draft:
>>
>> https://gist.github.com/priyanshsaxena/4670cae3d03a7b77a16388601c018460
>>
>> Looking forward to your suggestions on how best to improve this for a 
>> concrete GSoC '18 project-proposal.
>>
>> Regards
>> Priyansh
>>
>> On Wednesday, February 14, 2018 at 3:15:56 AM UTC+5:30, Russell 
>> Keith-Magee wrote:
>>>
>>>
>>> Another approach would be to do what I laid out in this talk at 
>>> DjangoCon US 2015, following the last Summer of Code student who tackled 
>>> (tangentially) this problem. 
>>>
>>> https://www.youtube.com/watch?v=VgM0qmpHDiE 
>>>
>>> That is - finish the modifications needed to Django’s core such that an 
>>> arbitrary model can register in a way compatible with the Admin and Forms 
>>> library. This was one of the reasons given for standardising the meta-model 
>>> framework, but didn’t make it into Daniel’s GSoC project, although he *did* 
>>> get a proof of concept working that exposed your Gmail inbox in Django’s 
>>> admin. 
>>>
>>> This would allow *any* data backend to expose an interface that is 
>>> fundamentally compatible with Django - which, really, just means “I want to 
>>> browse my data in the admin” and “I want to display a form for my model”. 
>>>
>>> It won’t allow an arbitrary ORM query to run against an arbitrary 
>>> “NoSQL” backend - but that’s idea was never going to work anyway. But I 
>>> don’t think anyone is serious about wanting that, either. All they want is 
>>> the ability to integrate a non-SQL data source into their basic Django 
>>> visualisations. 
>>>
>>> Yours, 
>>> Russ Magee %-) 
>>>
>>> > On 13 Feb 2018, at 6:48 pm, Curtis Maloney  
>>> wrote: 
>>> > 
>>> > On 02/13/2018 09:23 PM, askpr...@gmail.com wrote: 
>>> >> Hello ! 
>>> >> What is the policy regarding NoSQL datastores being used as backends 
>>> ? I think adding support for something like MongoDB might be good idea. 
>>> > 
>>> > Could you elaborate on why you think it would be a good idea? 
>>> > 
>>> > I believe every other time the discussion has come up the following 
>>> points have been made. 
>>> > 
>>> > 1. "NoSQL" is not a DB category, it is an anti-category 
>>> > 2. Because of there there is no common data model, or query languages. 
>>> > 3. If you limit yourself to just document stores, there is still no 
>>> common query language [but this can be hidden by code] 
>>> > 4. Document stores are a really really bad fit for the ORM, as it's 
>>> designed for the relational model, not document model. 
>>> > 5. A better approach would be to develop an ODM, which is sufficiently 
>>> compatible with the ORM you can provide similar tools like ModelForms and 
>>> ModelAdmin, as well as GCBV. 
>>> > 
>>> > If I missed anything, I'm sure someone else will remind me. 
>>> > 
>>> > [Also... why is it always MongoDB, instead of something with a solid 
>>> reputation of reliability and performance?] 
>>> > 
>>> > -- 
>>> > Curtis 
>>> > 
>>> > 
>>> > -- 
>>> > 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-develop...@googlegroups.com. 
>>> > To post to this group, send email to django-d...@googlegroups.com. 
>>> > Visit this group at h

Re: Google Summer of Code 2018

[askpriyansh]

Hello !

I have submitted a draft proposal on the GSoC Portal. I look forward to the 
community-feedback on this.

Regards
Priyansh

On Saturday, March 24, 2018 at 11:10:43 PM UTC+5:30, askpr...@gmail.com 
wrote:
>
> Hello !
>
> Here's the updated version of my proposal: 
> https://gist.github.com/priyanshsaxena/4670cae3d03a7b77a16388601c018460. 
> A request to the community to spare some time and review this before I put 
> it up on the GSoC portal.
>
> I am working on solving some feature-requests, and I've got working 
> solutions put as PRs. I have tried to give details of the problem and 
> examples of how the project will be useful in the proposal, but I am not 
> quite sure on how to demonstrate the understanding of Django. Please do 
> give me pointers on this.
>
> Best
> Priyansh
>
> On Wednesday, February 21, 2018 at 12:12:44 AM UTC+5:30, Tim Graham wrote:
>>
>> Hi Priyansh,
>>
>> Your proposal isn't really detailed enough for me to understand what the 
>> outcome of your project would be (I haven't watched Russell's talk that you 
>> linked). What are the "big wins"? There are projects like 
>> https://github.com/potatolondon/djangae, which allows using Django with 
>> Google App Engine. Would your project make something like that much 
>> simpler? You'll have to demonstrate a fairly sophisticated level of 
>> understanding of Django to convince us that you understand the problems 
>> well enough to have a reasonable chance of success.
>>
>> Regarding your proposed schedule, I'm a bit concerned that you'll have 
>> exams for five weeks of the coding period. Students are expected to average 
>> 30+ hours/week on their projects. Is that feasible while you're studying 
>> for exams?
>>
>> On Monday, February 19, 2018 at 1:45:22 PM UTC-5, askpr...@gmail.com 
>> wrote:
>>>
>>> Hello !
>>>
>>> I have drafted a project-proposal for the idea that Russell laid out in 
>>> his talk at DjangoCon '15. Here's the link to the draft:
>>>
>>> https://gist.github.com/priyanshsaxena/4670cae3d03a7b77a16388601c018460
>>>
>>> Looking forward to your suggestions on how best to improve this for a 
>>> concrete GSoC '18 project-proposal.
>>>
>>> Regards
>>> Priyansh
>>>
>>> On Wednesday, February 14, 2018 at 3:15:56 AM UTC+5:30, Russell 
>>> Keith-Magee wrote:


 Another approach would be to do what I laid out in this talk at 
 DjangoCon US 2015, following the last Summer of Code student who tackled 
 (tangentially) this problem. 

 https://www.youtube.com/watch?v=VgM0qmpHDiE 

 That is - finish the modifications needed to Django’s core such that an 
 arbitrary model can register in a way compatible with the Admin and Forms 
 library. This was one of the reasons given for standardising the 
 meta-model 
 framework, but didn’t make it into Daniel’s GSoC project, although he 
 *did* 
 get a proof of concept working that exposed your Gmail inbox in Django’s 
 admin. 

 This would allow *any* data backend to expose an interface that is 
 fundamentally compatible with Django - which, really, just means “I want 
 to 
 browse my data in the admin” and “I want to display a form for my model”. 

 It won’t allow an arbitrary ORM query to run against an arbitrary 
 “NoSQL” backend - but that’s idea was never going to work anyway. But I 
 don’t think anyone is serious about wanting that, either. All they want is 
 the ability to integrate a non-SQL data source into their basic Django 
 visualisations. 

 Yours, 
 Russ Magee %-) 

 > On 13 Feb 2018, at 6:48 pm, Curtis Maloney  
 wrote: 
 > 
 > On 02/13/2018 09:23 PM, askpr...@gmail.com wrote: 
 >> Hello ! 
 >> What is the policy regarding NoSQL datastores being used as backends 
 ? I think adding support for something like MongoDB might be good idea. 
 > 
 > Could you elaborate on why you think it would be a good idea? 
 > 
 > I believe every other time the discussion has come up the following 
 points have been made. 
 > 
 > 1. "NoSQL" is not a DB category, it is an anti-category 
 > 2. Because of there there is no common data model, or query 
 languages. 
 > 3. If you limit yourself to just document stores, there is still no 
 common query language [but this can be hidden by code] 
 > 4. Document stores are a really really bad fit for the ORM, as it's 
 designed for the relational model, not document model. 
 > 5. A better approach would be to develop an ODM, which is 
 sufficiently compatible with the ORM you can provide similar tools like 
 ModelForms and ModelAdmin, as well as GCBV. 
 > 
 > If I missed anything, I'm sure someone else will remind me. 
 > 
 > [Also... why is it always MongoDB, instead of something with a solid 
 reputation of reliability and performance?] 
 > 
 > -- 
 > Curtis 
 > 
 > 
 > -- 
 > You rec

Re: Google Summer of Code 2018

[askpriyansh]

Hello !

The deadline for proposal is past, but I agree the plan isn't detailed 
enough as of now. I'll try to add concrete details to the proposal within 
this week to try convincing the community.

Best
Priyansh

On Monday, March 26, 2018 at 10:51:41 PM UTC+5:30, Tim Graham wrote:
>
> Hi, I'm not sure that the plan is fleshed out in enough detail (compare it 
> to https://gist.github.com/chrismedrela/82cbda8d2a78a280a129 and 
> https://github.com/django/deps). That level of detail is needed to give 
> us confidence that you might be able to deliver what you promise.
>
> On Monday, March 26, 2018 at 11:28:30 AM UTC-4, askpr...@gmail.com wrote:
>>
>> Hello !
>>
>> I have submitted a draft proposal on the GSoC Portal. I look forward to 
>> the community-feedback on this.
>>
>> Regards
>> Priyansh
>>
>> On Saturday, March 24, 2018 at 11:10:43 PM UTC+5:30, askpr...@gmail.com 
>> wrote:
>>>
>>> Hello !
>>>
>>> Here's the updated version of my proposal: 
>>> https://gist.github.com/priyanshsaxena/4670cae3d03a7b77a16388601c018460. 
>>> A request to the community to spare some time and review this before I put 
>>> it up on the GSoC portal.
>>>
>>> I am working on solving some feature-requests, and I've got working 
>>> solutions put as PRs. I have tried to give details of the problem and 
>>> examples of how the project will be useful in the proposal, but I am not 
>>> quite sure on how to demonstrate the understanding of Django. Please do 
>>> give me pointers on this.
>>>
>>> Best
>>> Priyansh
>>>
>>> On Wednesday, February 21, 2018 at 12:12:44 AM UTC+5:30, Tim Graham 
>>> wrote:

 Hi Priyansh,

 Your proposal isn't really detailed enough for me to understand what 
 the outcome of your project would be (I haven't watched Russell's talk 
 that 
 you linked). What are the "big wins"? There are projects like 
 https://github.com/potatolondon/djangae, which allows using Django 
 with Google App Engine. Would your project make something like that much 
 simpler? You'll have to demonstrate a fairly sophisticated level of 
 understanding of Django to convince us that you understand the problems 
 well enough to have a reasonable chance of success.

 Regarding your proposed schedule, I'm a bit concerned that you'll have 
 exams for five weeks of the coding period. Students are expected to 
 average 
 30+ hours/week on their projects. Is that feasible while you're studying 
 for exams?

 On Monday, February 19, 2018 at 1:45:22 PM UTC-5, askpr...@gmail.com 
 wrote:
>
> Hello !
>
> I have drafted a project-proposal for the idea that Russell laid out 
> in his talk at DjangoCon '15. Here's the link to the draft:
>
> https://gist.github.com/priyanshsaxena/4670cae3d03a7b77a16388601c018460
>
> Looking forward to your suggestions on how best to improve this for a 
> concrete GSoC '18 project-proposal.
>
> Regards
> Priyansh
>
> On Wednesday, February 14, 2018 at 3:15:56 AM UTC+5:30, Russell 
> Keith-Magee wrote:
>>
>>
>> Another approach would be to do what I laid out in this talk at 
>> DjangoCon US 2015, following the last Summer of Code student who tackled 
>> (tangentially) this problem. 
>>
>> https://www.youtube.com/watch?v=VgM0qmpHDiE 
>>
>> That is - finish the modifications needed to Django’s core such that 
>> an arbitrary model can register in a way compatible with the Admin and 
>> Forms library. This was one of the reasons given for standardising the 
>> meta-model framework, but didn’t make it into Daniel’s GSoC project, 
>> although he *did* get a proof of concept working that exposed your Gmail 
>> inbox in Django’s admin. 
>>
>> This would allow *any* data backend to expose an interface that is 
>> fundamentally compatible with Django - which, really, just means “I want 
>> to 
>> browse my data in the admin” and “I want to display a form for my 
>> model”. 
>>
>> It won’t allow an arbitrary ORM query to run against an arbitrary 
>> “NoSQL” backend - but that’s idea was never going to work anyway. But I 
>> don’t think anyone is serious about wanting that, either. All they want 
>> is 
>> the ability to integrate a non-SQL data source into their basic Django 
>> visualisations. 
>>
>> Yours, 
>> Russ Magee %-) 
>>
>> > On 13 Feb 2018, at 6:48 pm, Curtis Maloney  
>> wrote: 
>> > 
>> > On 02/13/2018 09:23 PM, askpr...@gmail.com wrote: 
>> >> Hello ! 
>> >> What is the policy regarding NoSQL datastores being used as 
>> backends ? I think adding support for something like MongoDB might be 
>> good 
>> idea. 
>> > 
>> > Could you elaborate on why you think it would be a good idea? 
>> > 
>> > I believe every other time the discussion has come up the following 
>> points have been made. 
>>>