Re: Introduction

[Ruchit Vithani]

I have following queries regarding tickets on Trac. In many of the tickets, 
some people comment `Regression in` and `Reproduced at`, and both of them 
link to some commit on GitHub. I could not understand what these links 
specify. I read this 

 documentation 
on Triage workflow, there is not anything mentioned about this yet on this 
page. It would be great if someone could tell me what those links specify, 
and if there is any link to documentation, which could be helpful, please 
mention. 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/28af2017-ad64-4348-911b-31280f1afe91%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

RANDOM SELECTION

[Edward Victorhez]

HELLO
PLEASE I WANT A CODE THAT CAN SELECT AN ITEM FROM A DATABASE ASSIGNING A
WORK FROM GROUP OF WORKS RANDOMLY.

-- 
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/CACzrH1Cvzccoys%3D3426wFvSY3p2RGH6nSzxXXOEs8V9SGtO1EQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Help wanted reviewing applications for the DSF internship

[Jacob Kaplan-Moss]

Hi folks -

I'm looking for some folks to help me review applications for the
internship to build a new DSF membership app. If you have experience hiring
junior developers and can devote around 10+ hours over the next few weeks.

Background: the DSF put out a CFP

for
a new membership app. I won this contract and am fulfilling it in a novel
way: instead of doing the work myself, I'm hiring an intern to do the work
with my support. I put out a call for interns

a
couple weeks ago. The response was overwhelming: just over a thousand
people applied!

So, I need some help reviewing applications. I'm looking for people who
already have experience hiring junior devs (normally I'd love to offer to
train some folks to help, but I don't have time). If this is you, LMK!

Jacob

-- 
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/CAK8PqJFjSX2_uZNKqoAUwe96eASb9XqWfn1zM%2BpKqAb1wUKhQg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Introduction

[Tobias Kunze]

Hi Ruchit,

On 19-05-10 23:19:16, Ruchit Vithani wrote:
>I have following queries regarding tickets on Trac. In many of the tickets, 
>some people comment `Regression in` and `Reproduced at`, and both of them 
>link to some commit on GitHub. I could not understand what these links 
>specify.

The "regression in" comments point to commits that have either
introduced or re-introduced the issue in the ticket. Regressions are
explained in the contributing documentation, including a guide on how to
figure out which commit caused the regression:


This is helpful because it gives you a start when trying to fix the
issue. You can look at the causing commit, and figure out if this
behaviour was intentional, if it was discussed in the ticket referenced
in the commit, if it was accidental, etc. It also helps you to develop a
fix that doesn't break anything else unintentionally. So even if you
don't have the time or experience to find a fix, finding and noting
which commit caused a regression can be very helpful.

The 'reproduced at' comments are indeed not mentioned in the triage
documentation – maybe you could add them?  Sometimes people add comments
like that when they accept a ticket, for better documentation of why
they decided to accept a ticket. There is a note about this workflow
here: 
https://docs.djangoproject.com/en/2.2/internals/contributing/new-contributors/

They can also be useful with old tickets: With more than a thousand
open tickets, and most of them older than the last one or two releases,
it's not always obvious that an issue still persists. (For instance, I
recently came across a ticket that called for the introduction of
template-based form rendering, which has been part of Django for some
time now.) Adding a comment that the issue still persists currently (and
linking to the tested commit for reference) can be helpful to show that
an 8 year old bug is still relevant.

I hope this helps,
Tobias

-- 
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/20190511132755.gmpmcetv33npqlji%40cordelia.localdomain.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: PGP signature

RANDOM PICKING OF TWO DIFFERENT LISTS, ASSIGNING ONE ITEM FROM ONE LIST TO THE OTHER ITEM IN ANOTHER LIST

[Edward Victorhez]

HELLO


PLEASE I WANT A CODE THAT CAN SELECT AN ITEM FROM A DATABASE ASSIGNING A 
WORK FROM GROUP OF WORKS RANDOMLY. 

-- 
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/0b981149-8b3a-4796-be17-9087dee2a52b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: RANDOM PICKING OF TWO DIFFERENT LISTS, ASSIGNING ONE ITEM FROM ONE LIST TO THE OTHER ITEM IN ANOTHER LIST

[Karen Tracey]

Please ask questions about using Django on Django-users. The topic of this
list is the development of Django itself.

-- 
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/CACS9rafeajAtmP_-uYM2%2BC10-_DoWJSAKfO3tNX1dbHETQF8SA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: RANDOM SELECTION

[Adam Johnson]

This mailing list is for the development of Django itself, not for support
using Django. Please use the django-users mailing list for that, or IRC
#django on freenode, or a site like Stack Overflow.

Also I searched the web, your query shows up several times on Stack
Overflow: https://duckduckgo.com/?q=django+random+database&ia=web

On Sat, 11 May 2019 at 13:42, Edward Victorhez 
wrote:

> HELLO
> PLEASE I WANT A CODE THAT CAN SELECT AN ITEM FROM A DATABASE ASSIGNING A
> WORK FROM GROUP OF WORKS RANDOMLY.
>
> --
> 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/CACzrH1Cvzccoys%3D3426wFvSY3p2RGH6nSzxXXOEs8V9SGtO1EQ%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/CAMyDDM2JsUF68BfUN286qwx7EurLoYyKZ%2BV47jb6D4Gr%2BFb0-Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Introduction

[Carlton Gibson]

Thank you Tobias. Good explanation.

An additional point I picked up from Tim is that if you have a Reproduced
at... but the bug is fixed on master then you have a starting point to git
bisect where the issue was fixed.

On Sat, 11 May 2019 at 15:28, Tobias Kunze  wrote:

> Hi Ruchit,
>
> On 19-05-10 23:19:16, Ruchit Vithani wrote:
> >I have following queries regarding tickets on Trac. In many of the
> tickets,
> >some people comment `Regression in` and `Reproduced at`, and both of them
> >link to some commit on GitHub. I could not understand what these links
> >specify.
>
> The "regression in" comments point to commits that have either
> introduced or re-introduced the issue in the ticket. Regressions are
> explained in the contributing documentation, including a guide on how to
> figure out which commit caused the regression:
> <
> https://docs.djangoproject.com/en/2.2/internals/contributing/triaging-tickets/#bisecting-a-regression
> >
>
> This is helpful because it gives you a start when trying to fix the
> issue. You can look at the causing commit, and figure out if this
> behaviour was intentional, if it was discussed in the ticket referenced
> in the commit, if it was accidental, etc. It also helps you to develop a
> fix that doesn't break anything else unintentionally. So even if you
> don't have the time or experience to find a fix, finding and noting
> which commit caused a regression can be very helpful.
>
> The 'reproduced at' comments are indeed not mentioned in the triage
> documentation – maybe you could add them?  Sometimes people add comments
> like that when they accept a ticket, for better documentation of why
> they decided to accept a ticket. There is a note about this workflow
> here:
> https://docs.djangoproject.com/en/2.2/internals/contributing/new-contributors/
>
> They can also be useful with old tickets: With more than a thousand
> open tickets, and most of them older than the last one or two releases,
> it's not always obvious that an issue still persists. (For instance, I
> recently came across a ticket that called for the introduction of
> template-based form rendering, which has been part of Django for some
> time now.) Adding a comment that the issue still persists currently (and
> linking to the tested commit for reference) can be helpful to show that
> an 8 year old bug is still relevant.
>
> I hope this helps,
> Tobias
>
> --
> 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/20190511132755.gmpmcetv33npqlji%40cordelia.localdomain
> .
> 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/CAJwKpyRmus1j7xwz2NEjbzUYN1ncft0vu0uCqh6x8_xsebnCxA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Introduction

[Ruchit Vithani]

Thanks, Tobias, for a wonderful explanation. I sure will try to add 
documentation about 'Reproduced at:' in triaging workflow. But currently, 
I've claimed one easy picking ticket, so once I finish work on that, I'll 
come on to this documentation :)

-- 
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/a3c3d5f3-8b52-466b-aa5d-583127586f19%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: DEP 0008 (Formatting using Black) is accepted

[Michael Martinez]

I'm disappointed to learn that this was merged without a healthy debate on 
the deps repo. 

On Friday, May 10, 2019 at 8:53:44 PM UTC-5, Andrew Godwin wrote:
>
> One quick clarification - when I said "stable (1.0)" release, I in fact 
> meant the first release that the Black project officially marks as stable.
>
> Black doesn't use versioning that would result in a stable release being 
> called 1.0, as far as I know, given they are on 19.3b0 right now!
>
> Andrew
>
> On Friday, May 10, 2019 at 6:46:37 PM UTC-7, Andrew Godwin wrote:
>>
>> Hi everyone,
>>
>> The Technical Board has voted on DEP 0008 (
>> https://github.com/django/deps/blob/master/accepted/0008-black.rst), 
>> after the extensive discussion here and the updates done as a result.
>>
>> The board voted in favour, and so I've moved the DEP into the accepted 
>> directory.
>>
>> One of the key changes to the proposal was to wait until Black got to a 
>> stable (1.0) release, so it will sit in "accepted" until that happens, at 
>> which point we will do the implementation (including the big reformat 
>> itself) and then move the DEP to "final".
>>
>> There's no hard timeline on when Black will hit a stable release, but 
>> it's very close; there are a few changes we'd like to make sure are 
>> included when we reformat Django, such as keeping lists with trailing 
>> commas on multiple lines (https://github.com/python/black/pull/826). 
>> That's why we're waiting for the stable release rather than reformatting 
>> now.
>>
>> Thanks to everyone who chimed in on the discussion - this was not an easy 
>> decision, and the feedback helped a lot to work out what was best for us.
>>
>> I also want to personally thank Herman Schistad, for prompting this 
>> discussion, and Aymeric Augustin, for his work on writing and updating the 
>> DEP!
>>
>> Yours in auto-formatting,
>> Andrew
>>
>

-- 
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/8f6f5de0-f489-4271-9c2e-af3b0a97f365%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: DEP 0008 (Formatting using Black) is accepted

[Tom Forbes]

There has been a particularly healthy debate on the mailing list, I think it 
was clear that a consensus was not going to be reached. Are there any points 
you wanted to bring up there that where not already made on the mailing list 
thread?

Tom

> On 11 May 2019, at 17:30, Michael Martinez  
> wrote:
> 
> I'm disappointed to learn that this was merged without a healthy debate on 
> the deps repo. 
> 
>> On Friday, May 10, 2019 at 8:53:44 PM UTC-5, Andrew Godwin wrote:
>> One quick clarification - when I said "stable (1.0)" release, I in fact 
>> meant the first release that the Black project officially marks as stable.
>> 
>> Black doesn't use versioning that would result in a stable release being 
>> called 1.0, as far as I know, given they are on 19.3b0 right now!
>> 
>> Andrew
>> 
>>> On Friday, May 10, 2019 at 6:46:37 PM UTC-7, Andrew Godwin wrote:
>>> Hi everyone,
>>> 
>>> The Technical Board has voted on DEP 0008 
>>> (https://github.com/django/deps/blob/master/accepted/0008-black.rst), after 
>>> the extensive discussion here and the updates done as a result.
>>> 
>>> The board voted in favour, and so I've moved the DEP into the accepted 
>>> directory.
>>> 
>>> One of the key changes to the proposal was to wait until Black got to a 
>>> stable (1.0) release, so it will sit in "accepted" until that happens, at 
>>> which point we will do the implementation (including the big reformat 
>>> itself) and then move the DEP to "final".
>>> 
>>> There's no hard timeline on when Black will hit a stable release, but it's 
>>> very close; there are a few changes we'd like to make sure are included 
>>> when we reformat Django, such as keeping lists with trailing commas on 
>>> multiple lines (https://github.com/python/black/pull/826). That's why we're 
>>> waiting for the stable release rather than reformatting now.
>>> 
>>> Thanks to everyone who chimed in on the discussion - this was not an easy 
>>> decision, and the feedback helped a lot to work out what was best for us.
>>> 
>>> I also want to personally thank Herman Schistad, for prompting this 
>>> discussion, and Aymeric Augustin, for his work on writing and updating the 
>>> DEP!
>>> 
>>> Yours in auto-formatting,
>>> Andrew
> 
> -- 
> 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/8f6f5de0-f489-4271-9c2e-af3b0a97f365%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/B3F49C9A-FAE8-41BA-A9EE-06222826B54F%40tomforb.es.
For more options, visit https://groups.google.com/d/optout.