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
signature.asc
Description: PGP signature
_______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
