[openstack-dev] pep8 barfs on long URL

Julien Danjou julien at danjou.info
Fri Feb 7 14:36:48 UTC 2014


On Fri, Feb 07 2014, Jay Pipes wrote:

> On Fri, 2014-02-07 at 14:25 +0000, Matthew Booth wrote:
>> I have a comment which references a long URL. The URL itself is longer
>> than 80 characters. Jenkins has flagged this as a pep8 failure, because
>> the line is longer than 80 characters.
>> 
>> This is an instance where in the past I have always applied common sense
>> to the line length limit. You either have a long line or a broken URL.
>> As the long line is more usable in this instance, it's the lesser of 2
>> evils.
>> 
>> Is there a mechanism to to coerce Jenkins to allow it? Failing that, is
>> there a mechanism to manually ignore a specific Jenkins failure? Failing
>> that, is there a project convention for broken URLs?
>
> How about using a service like bit.ly to shorten the URL? Would that be
> acceptable?

This would be ridiculous. :-/

Isn't #noqa working on such error?

-- 
Julien Danjou
-- Free Software hacker - independent consultant
-- http://julien.danjou.info
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 832 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20140207/ba5ecd64/attachment.pgp>


More information about the OpenStack-dev mailing list