Re: About contributing to django...

[Adam Johnson]

Hi Xero,

There have been a few email threads about this previously, with links to
the relevant locations:

https://groups.google.com/d/msgid/django-developers/af075d59-ece3-4044-9204-b690c746b9e0%40googlegroups.com

https://groups.google.com/d/msgid/django-developers/3d87d5a8-ab76-45a7-ab28-b8a6501fce7d%40googlegroups.com

Hope these help as a starting point,

Adam

On Sun, 2 Feb 2020 at 18:09, XERO  wrote:

> hello everybody!
> I am computer science student, studying in second year.I am novice in this
> sector.I have been going through the documentation,readme etc. from last
> few days (done some basic projects like to-do web-app,calculator etc.) but
> not actually understanding the flow properly.I am participating gsoc
> competition this year and would like to contribute here(very
> desperate..).Can someone help me with the same :|
>
> --
> 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 view this discussion on the web visit
> https://groups.google.com/d/msgid/django-developers/90574ec0-6b59-4fdd-ad8f-1f80e3a50233%40googlegroups.com
> 
> .
>


-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/CAMyDDM1wMthTHyVWiQRqBvD7_bAsQcNQ2drPckgLTNWT1pgCVw%40mail.gmail.com.

Django security releases issued: 3.0.3, 2.2.10 and 1.11.28

[Carlton Gibson]

Today the Django team issued 3.0.3, 2.2.10 and 1.11.28 as part of our security 
process. These releases address a security issue, and we encourage all users to 
upgrade as soon as possible:

https://www.djangoproject.com/weblog/2020/feb/03/security-releases/ 




-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/A2A70666-CA0C-49C2-965A-173464D4DAE3%40gmail.com.

Re: Fellow Reports -- January 2020

[Carlton Gibson]

Hi all. 



Calendar Week 5 -- ending 02 February.


Triaged:

https://code.djangoproject.com/ticket/31216 -- Support terminal color 
output on Windows via colorama (Accepted)
https://code.djangoproject.com/ticket/31201 -- Atomic Transaction Roll Back 
File Upload (wontfix)



Reviewed:

https://github.com/django/django/pull/12321 -- #31169 Ensure the parallel 
test worker has initialised django and uses the test db names.
https://github.com/django/django/pull/12387 -- Fixed #31216 -- Added 
support for colorama terminal colors on Windows.
https://github.com/django/django/pull/11650 -- Implement async views
https://github.com/django/django/pull/12388 -- Fixed #31217 -- Made 
QuerySet.values()/values_list() group by not selected annotations used in 
order_by().
https://github.com/django/django/pull/11452 -- Fixed #12990 -- Added 
JSONField model field.
https://github.com/django/django/pull/12251 -- Fixed #28290 -- Enabled 
Sphinx auto-label generation for title and section headers.
https://github.com/django/django/pull/12367 -- Used model's 
Options.label/label_lower where applicable.
https://github.com/django/django/pull/12261 -- Fixed #31126 -- Doc'd 
STATICFILES_DIRS namespacing in static files how-to.
https://github.com/django/django/pull/9126 -- Fixed #28198 -- Prevented 
model attributes from overriding deferred fields. #9126
https://github.com/django/django/pull/12036 -- Removed "Pocket 
PC" from terminal color support function.
https://github.com/django/django/pull/12382 -- Updated the GeoJSON format 
specification link to RFC 7946.
https://github.com/django/django/pull/12381 -- Refs #25778 -- Updated some 
links to HTTPS and new locations.



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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/304a03b6-6fd2-4cb5-bd2e-7def2d62b767%40googlegroups.com.

Re: Fellow Reports - January 2020

[Mariusz Felisiak]

Week ending February 2, 2020.

*Triaged:*
https://code.djangoproject.com/ticket/31206 - Migration crashes when 
altering a field to use the db_returning flag and default value returned 
from database. (duplicate)
https://code.djangoproject.com/ticket/26251 - SimpleArrayField missing 
clean method which leads to unexpected validation error. (duplicate)
https://code.djangoproject.com/ticket/31209 - Logic flaw in the tutorial 4. 
(invalid)
https://code.djangoproject.com/ticket/31211 - Add SearchConfig expression. 
(accepted)
https://code.djangoproject.com/ticket/31212 - Update http://initd.org/ URLs 
to https://www.psycopg.org/. (accepted)
https://code.djangoproject.com/ticket/31214 - ORM query with 
Count(Subquery(...)) produces invalid SQL with Django 3.0. (duplicate)
https://code.djangoproject.com/ticket/31213 - Add flag to 
remove_stale_contenttypes to remove entries for nonexistent apps. 
(duplicate)
https://code.djangoproject.com/ticket/31123 - Add option to 
remove_stale_contenttypes to remove entries for nonexistent apps. (accepted)
https://code.djangoproject.com/ticket/31210 - Document backwards-compatible 
replacement for is_ajax(). (accepted)
https://code.djangoproject.com/ticket/31215 - Typo in tutorial 6. (invalid)
https://code.djangoproject.com/ticket/31217 - 
QuerySet.values()/values_list() with ordering by annotations with related 
fields and aggregations crashes. (accepted)
https://code.djangoproject.com/ticket/31218 - response.set_cookie() method 
not accepting "samesite" key set to "None" in release versions (invalid)
https://code.djangoproject.com/ticket/31220 - Widgets ignores "cols" 
attribute. (invalid)

*Reviewed/committed:*
https://github.com/django/django/pull/12091 - Fixed #30997 -- Deprecated 
HttpRequest.is_ajax().
https://github.com/django/django/pull/12372 - Refs #27852 -- Fixed object 
deletion to show all protected related objects rather than just the first 
one.
https://github.com/django/django/pull/12334 - Refs #27468 -- Added 
algorithm parameter to django.utils.crypto.salted_hmac().
https://github.com/django/django/pull/12148 - Fixed #22261 -- Fixed 
resolving namespaced URLs for flatpages.
https://github.com/django/django/pull/12379 - Refs #25778 -- Updated 
sphinx-doc.org URLs to use HTTPS.
https://github.com/django/django/pull/12378 - Fixed #31212 -- Updated 
psycopg links to HTTPS and new location.
https://github.com/django/django/pull/12377 - Fixed #31211 -- Added 
SearchConfig expression.
https://github.com/django/django/pull/12376 - Refs #27852 -- Fixed object 
deletion to show all restricted related objects rather than just the first 
one.
https://github.com/django/django/pull/12390 - Added tests for signing 
non-string values and updated docs.
https://github.com/django/django/pull/12394 - Fixed #31219 -- Fixed object 
deletion crash for nested protected related objects.
https://github.com/django/django/pull/12383 - Fixed #31207 -- Prevented 
references to non-local remote fields in ForeignKey.to_field.

*Reviewed:*
https://github.com/django/django/pull/12384 - Fixed #31206 -- Migration 
crashes for changed database default values.

*Authored:*
https://github.com/django/django/pull/12388 - Fixed #31217 -- Made 
QuerySet.values()/values_list() group by not selected annotations with 
aggregations used in order_by().

Best regards,
Mariusz

>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/1c3dcbd6-fa0d-4a6c-8aef-44b2eac84422%40googlegroups.com.

Re: Model inheritance in different modules

[Steven Mapes]

It sounds to me like your data modelling is wrong. You can either have a 
one-to-one table2 acts as an extension of table1, a view that combines 
multiple tables into one "virtual table" or have one table and two models 
that use the table. One, the superset, would be managed, the other would 
only show a subset of the columns

Otherwise you risk adding fields into the subset model and assuming that 
they will be in the superset model which they won't unless you are 
inheriting from it and then overloading the meta.

On Thursday, 30 January 2020 16:30:36 UTC, LBris wrote:
>
> I've never said it isn't saved in database. It is saved but in the table 
> of the employee since hrfleetemployee inherits from employee. It simply 
> adds this field to the table of Employee
>
> Le jeu. 30 janv. 2020 à 5:24 PM, Abhijeet Viswa  > a écrit :
>
>> How would the fields in HRFleetEmployee be persistent and linked to a 
>> particular Employee or Vehicle without being saved in the database? Or did 
>> I understand your code and request wrong? 
>>
>> -- 
>> 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-d...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/django-developers/CAP1-YrrSo06-gxD1ZdzN0CCPQCm-shdah24H_ZVyLh_rGkU4%3DA%40mail.gmail.com
>>  
>> 
>> .
>>
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/eed19926-f9e8-4eb8-b521-ce89b0745aca%40googlegroups.com.

Re: Model inheritance in different modules

[LBris]

The thing is in my app, everything would be done on runtime. The idea is to 
have a minimal app "base" and once you're on in, you'd have a list of 
applications that you can install. So If I have "base" and "Employee", and 
then I want to install "Fleet", only migrations from Fleet would have to be 
done. The thing is it would be possible to install more apps only 1 by 1 ..

Le jeudi 30 janvier 2020 19:29:05 UTC+1, Abhijeet Viswa a écrit :
>
> Each model represents one table on the DB. Modifying it in two different 
> apps (hence creating two different sets of migrations) might result in 
> breaking changes. What if one migration affects something that is directly 
> referenced by the other app, but wasn't updated?
>
> Also, what would the potential benefits be (other than reduction of number 
> of tables) to such a type of inheritance? Couldn't the same be done with 
> another table and a select related? The only difference would be a in 
> prefetch_related call (your inheritance wouldn't require one). However, 
> doing something that like that means the Employee app knows about (and 
> relies upon) this backward relation to the Vehicle model (and hence the 2nd 
> app itself).
>
> On Thu, 30 Jan 2020 at 23:07, LBris > 
> wrote:
>
>> I do not understand. Could you explain to me what it would break the 
>> database and how ?
>>
>> Le jeudi 30 janvier 2020 17:37:22 UTC+1, Abhijeet Viswa a écrit :
>>>
>>> I think this would needlessly complicate the entire migration process. 
>>> Two different app migrations (and possibly even more) would have be 
>>> considered and executed in sequence to prevent anything breaking on the 
>>> database. 
>>>
>>> On Thu, 30 Jan 2020 at 22:00, LBris  wrote:
>>>
 I've never said it isn't saved in database. It is saved but in the 
 table of the employee since hrfleetemployee inherits from employee. It 
 simply adds this field to the table of Employee

 Le jeu. 30 janv. 2020 à 5:24 PM, Abhijeet Viswa  
 a écrit :

> How would the fields in HRFleetEmployee be persistent and linked to a 
> particular Employee or Vehicle without being saved in the database? Or 
> did 
> I understand your code and request wrong? 
>
> -- 
> 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-d...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/django-developers/CAP1-YrrSo06-gxD1ZdzN0CCPQCm-shdah24H_ZVyLh_rGkU4%3DA%40mail.gmail.com
>  
> 
> .
>
 -- 
 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-d...@googlegroups.com.
 To view this discussion on the web visit 
 https://groups.google.com/d/msgid/django-developers/CAJi3W9g2qa%2Bd1cXJNO2NJWfDpFTUHrqX2e%2B%2BS71KH2Wv9BeUuw%40mail.gmail.com
  
 
 .

>>>
>>>
>>> -- 
>>> Abhijeet
>>>
>> -- 
>> 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-d...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/django-developers/f58e79a0-6494-4a0a-ace8-e2cc31c799da%40googlegroups.com
>>  
>> 
>> .
>>
>
>
> -- 
> Abhijeet
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/1d0fa4ea-6e0a-4dd7-992a-f5a1431ead89%40googlegroups.com.

Where to post to ask questions about solving a Django ticket

[Ahmad A. Hussein]

I'm currently stuck on solving a Django ticket I assigned to myself, and I 
don't know where to post to ask for help/feedback.
Should I post here or ask someone on the #django IRC channel or should I 
make a post on the django project forums?

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/9d3b5148-4303-4453-bbd0-eb574432968a%40googlegroups.com.

Re: Where to post to ask questions about solving a Django ticket

[Carlton Gibson]

Hi Ahmed.

There’s a mentoring topic on forum.djangoproject.com. You can post there.

Please try to provide as much detail as possible. 🙂

Kind regards,
Carlton

On Mon, 3 Feb 2020 at 18:23, Ahmad A. Hussein 
wrote:

> I'm currently stuck on solving a Django ticket I assigned to myself, and I
> don't know where to post to ask for help/feedback.
> Should I post here or ask someone on the #django IRC channel or should I
> make a post on the django project forums?
>
> --
> 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 view this discussion on the web visit
> https://groups.google.com/d/msgid/django-developers/9d3b5148-4303-4453-bbd0-eb574432968a%40googlegroups.com
> 
> .
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/CAJwKpySjQ7XiTPZmmyy60bBeBxWUPYnstAW8-1iB9HK0mExaGA%40mail.gmail.com.

Re: Where to post to ask questions about solving a Django ticket

[Adam Johnson]

Post here

On Mon, 3 Feb 2020 at 16:58, Ahmad A. Hussein 
wrote:

> I'm currently stuck on solving a Django ticket I assigned to myself, and I
> don't know where to post to ask for help/feedback.
> Should I post here or ask someone on the #django IRC channel or should I
> make a post on the django project forums?
>
> --
> 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 view this discussion on the web visit
> https://groups.google.com/d/msgid/django-developers/9d3b5148-4303-4453-bbd0-eb574432968a%40googlegroups.com
> 
> .
>
-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/CAMyDDM2wq3xpchwMq9GB6c07vWQgcOVXhXjJ2Ncr4yfBQ8pNOg%40mail.gmail.com.

Re: Where to post to ask questions about solving a Django ticket

[Carlton Gibson]

Grrr. Auto-correct. Sorry about that Ahmad.

On Mon, 3 Feb 2020 at 18:42, Carlton Gibson 
wrote:

> Hi Ahmed.
>
> There’s a mentoring topic on forum.djangoproject.com. You can post there.
>
> Please try to provide as much detail as possible. 🙂
>
> Kind regards,
> Carlton
>
> On Mon, 3 Feb 2020 at 18:23, Ahmad A. Hussein 
> wrote:
>
>> I'm currently stuck on solving a Django ticket I assigned to myself, and
>> I don't know where to post to ask for help/feedback.
>> Should I post here or ask someone on the #django IRC channel or should I
>> make a post on the django project forums?
>>
>> --
>> 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 view this discussion on the web visit
>> https://groups.google.com/d/msgid/django-developers/9d3b5148-4303-4453-bbd0-eb574432968a%40googlegroups.com
>> 
>> .
>>
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/CAJwKpyS5kEwdM5_MLmM%3DTL5zhzeWSBRb%3D4b9QYF58Ef-6oCYvw%40mail.gmail.com.

recurring slot booking/reservation code

[Siddhartha Satyakama]

I'm looking for a code to see models,forms,views for creating recurring
slot booking app without any external module everything from scratch.
Please help how should I start??
Suppose if i want to block calender dates if booked how should I do it?

P.S. I'm new to Django so please help!

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/CADK5jRMuMBJiXsUohAHJJ298AcvL1_WuvvzAUz6WoYOkds%3Dmhg%40mail.gmail.com.

Re: recurring slot booking/reservation code

[Adam Johnson]

Hi!

I think you've found the wrong mailing list for this post. This mailing
list is for the development of Django itself, not for support using Django.
This means the discussions of bugs and features in Django itself, rather
than in your code using it. People on this list are unlikely to answer your
support query with their limited time and energy. Read more on the mailing
lists at https://www.djangoproject.com/community/

For support, please use the NEW Django forum at
https://forum.djangoproject.com , django-users mailing list, or IRC #django
on Freenode, or a site like Stack Overflow. There are people out there
willing to help on those channels, but they might not respond if you don't
ask your question well. Stack Overflow's question guide can help you frame
it well: https://stackoverflow.com/help/how-to-ask .

Also if you haven't read it, please take a look at Django's Code of
Conduct: https://www.djangoproject.com/conduct/ . These are our "ground
rules" for working well as a community, and will help you get the most out
of Django and our fantastic community.

Thanks for your understanding,

Adam

On Mon, 3 Feb 2020 at 18:31, Siddhartha Satyakama 
wrote:

> I'm looking for a code to see models,forms,views for creating recurring
> slot booking app without any external module everything from scratch.
> Please help how should I start??
> Suppose if i want to block calender dates if booked how should I do it?
>
> P.S. I'm new to Django so please help!
>
> --
> 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 view this discussion on the web visit
> https://groups.google.com/d/msgid/django-developers/CADK5jRMuMBJiXsUohAHJJ298AcvL1_WuvvzAUz6WoYOkds%3Dmhg%40mail.gmail.com
> 
> .
>


-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/CAMyDDM197aq5G5mAx7HfVx%2B9RuQRJfrUi_V6E9KeauHyM4ZeOw%40mail.gmail.com.