Closed vangheem closed 8 years ago
Totally unrelated but thanks anyway: you uncovered a bug on the package QA jenkins job :-)
@vangheem and as it is fixed now, would you mind reformatting that line to be shorter than 80 characters? Thanks in advance!
ok, an aside, can we increase that limit to more than 80? I thought it wasn't really recommended anymore and that we've moved on to longer line lengths.
After discussing the styleguide about documentation here and there, I also started using the ReST styleguide for changelog files ( https://github.com/plone/documentation/blob/5.0/about/rst-styleguide.rst#id4 ). It says to have one sentence per line and line length doesn't matter. It's better for translators to translate text. But wrapping any kind of text within the 80 columns limit is cumbersome.
+1 for giving up the 80 chars restriction for any kind of docs, except for docstrings or the like in Python files.
@vangheem @thet can we just stick to what has been endlessly discussed? And sorry if it feels a bit rude, but as a community we already decided on sticking to full pep8.
This re-formatted string (as already done, thanks @vangheem ) is still perfectly readable.
@gforcada I don't think PEP 8 is meant to be applied to non-python files. Even our Python styleguide is explicit about this here: https://github.com/plone/documentation/blob/5.0/develop/styleguide/python.rst#line-length
[the 79 column line length rule] explicitly does not aply to documentation .rst files. For rst files, use semantic linebreaks.
But that's not related and I move this discussion to here: https://github.com/plone/documentation/issues/548
@thet sure, i was only talking about python code here (as it was what jenkins reported to this pull request).
oh! sorry for the confusion. I only saw the changelog exceeding 80 cols.
Yah, okay, just a huge pet peeve of mine and I think it's rather insane.
tests: http://jenkins.plone.org/job/pull-request-5.0/1066/