Re: [Django] #30555: Migration files generated do not follow PEP8 E501 rule

[Django]

#30555: Migration files generated do not follow PEP8 E501 rule
-+--
 Reporter:  Aman Sharma  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Migrations   |  Version:  2.2
 Severity:  Normal   |   Resolution:  wontfix
 Keywords:   | Triage Stage:  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+--

Comment (by felixxm):

 No, if a ticket is `wontfix` then we will close PR.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/070.7badcf71fc539e105b3aeb691625c84f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #30555: Migration files generated do not follow PEP8 E501 rule

[Django]

#30555: Migration files generated do not follow PEP8 E501 rule
-+--
 Reporter:  Aman Sharma  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Migrations   |  Version:  2.2
 Severity:  Normal   |   Resolution:  wontfix
 Keywords:   | Triage Stage:  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+--

Comment (by Jarek Glowacki):

 Ooh really?

 It's a little inconsistent currently, with how the `dependencies` list
 (from makemigrations) gets nicely newlined, whereas the `replaces` list
 (from squashmigrations) doesn't.

 This has been a little pet peeve of mine for yonks, where `replaces` lists
 are difficult to interact with when doing manual migration tinkering, but
 I never got round to raising a ticket for it..

 Despite this being closed as a wontfix, would a PR still be accepted if
 one were submitted? :D

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/070.c1e1a9aa1228311a91b226ed06ec5f0f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #30555: Migration files generated do not follow PEP8 E501 rule

[Django]

#30555: Migration files generated do not follow PEP8 E501 rule
-+--
 Reporter:  Aman Sharma  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Migrations   |  Version:  2.2
 Severity:  Normal   |   Resolution:  wontfix
 Keywords:   | Triage Stage:  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+--

Comment (by Adam (Chainz) Johnson):

 ...or run Black on your codebase, like Django will :)

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/070.2da453fe32e3123eb52f9d3b76c1b0b8%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #30555: Migration files generated do not follow PEP8 E501 rule

[Django]

#30555: Migration files generated do not follow PEP8 E501 rule
--+--
 Reporter:  algomaster99  |Owner:  nobody
 Type:  Bug   |   Status:  closed
Component:  Migrations|  Version:  2.2
 Severity:  Normal|   Resolution:  wontfix
 Keywords:| Triage Stage:  Unreviewed
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+--
Changes (by Carlton Gibson):

 * status:  new => closed
 * resolution:   => wontfix


Comment:

 This isn’t something worth addressing. I suggest you add `migrations`
 folders to the [https://flake8.pycqa.org/en/latest/user/options.html
 #cmdoption-flake8-exclude flake8 exclude] list.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/070.8d83ba79ca70f7f151a319c19331498b%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #30555: Migration files generated do not follow PEP8 E501 rule

[Django]

#30555: Migration files generated do not follow PEP8 E501 rule
--+--
 Reporter:  algomaster99  |Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  Migrations|  Version:  2.2
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Unreviewed
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+--
Changes (by algomaster99):

 * Attachment "Screenshot from 2019-06-08 11-40-35.png" added.

 PEP8 throwing warnings when ran on `migrations` directory

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/070.161f63f0926ffd7f435dd302d12c36c3%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.