PEP8: W293 blank line contains whitespace

Author: ddemidov

ev3dev.py

@@ -249,7 +249,7 @@ def commands(self):
         Returns a list of commands that are supported by the motor
         controller. Possible values are `run-forever`, `run-to-abs-pos`, `run-to-rel-pos`,
         `run-timed`, `run-direct`, `stop` and `reset`. Not all commands may be supported.
-        
+
         - `run-forever` will cause the motor to run until another command is sent.
         - `run-to-abs-pos` will run to an absolute position specified by `position_sp`
           and then stop using the command specified in `stop_command`.
@@ -1148,11 +1148,11 @@ class Sensor(Device):
     The sensor class provides a uniform interface for using most of the
     sensors available for the EV3. The various underlying device drivers will
     create a `lego-sensor` device for interacting with the sensors.
-    
+
     Sensors are primarily controlled by setting the `mode` and monitored by
     reading the `value<N>` attributes. Values can be converted to floating point
     if needed by `value<N>` / 10.0 ^ `decimals`.
-    
+
     Since the name of the `sensor<N>` device node does not correspond to the port
     that a sensor is plugged in to, you must look at the `port_name` attribute if
     you need to know which port a sensor is plugged in to. However, if you don't
@@ -1644,7 +1644,7 @@ def trigger(self):
         complex. A simple trigger isn't configurable and is designed to slot into
         existing subsystems with minimal additional code. Examples are the `ide-disk` and
         `nand-disk` triggers.
-        
+
         Complex triggers whilst available to all LEDs have LED specific
         parameters and work on a per LED basis. The `timer` trigger is an example.
         The `timer` trigger will periodically change the LED brightness between
@@ -2112,12 +2112,12 @@ class LegoPort(Device):
     WeDo and LEGO Power Functions sensors and motors. Supported devices include
     the LEGO MINDSTORMS EV3 Intelligent Brick, the LEGO WeDo USB hub and
     various sensor multiplexers from 3rd party manufacturers.
-    
+
     Some types of ports may have multiple modes of operation. For example, the
     input ports on the EV3 brick can communicate with sensors using UART, I2C
     or analog validate signals - but not all at the same time. Therefore there
     are multiple modes available to connect to the different types of sensors.
-    
+
     In most cases, ports are able to automatically detect what type of sensor
     or motor is connected. In some cases though, this must be manually specified
     using the `mode` and `set_device` attributes. The `mode` attribute affects
@@ -2127,7 +2127,7 @@ class LegoPort(Device):
     appropriate for the connected sensor. The `set_device` attribute is used to
     specify the exact type of sensor that is connected. Note: the mode must be
     correctly set before setting the sensor type.
-    
+
     Ports can be found at `/sys/class/lego-port/port<N>` where `<N>` is
     incremented each time a new port is registered. Note: The number is not
     related to the actual port at all - use the `port_name` attribute to find

templates/generic-class.liquid

@@ -19,8 +19,13 @@ if currentClass.driverName %}{%
 endif %}
 class {{ class_name }}({{ base_class }}):
 
-    """{% for line in currentClass.description %}
-    {{ line }}{% endfor %}
+    """{%
+for line in currentClass.description %}{%
+    if line %}
+    {{ line }}{%
+    else %}
+{%  endif %}{%
+endfor %}
     """
 {% if currentClass.inheritance %}
     SYSTEM_CLASS_NAME = {{ base_class }}.SYSTEM_CLASS_NAME

templates/generic-get-set.liquid

@@ -12,8 +12,11 @@ for prop in currentClass.systemProperties %}{%
     @property
     def {{prop_name}}(self):
         """{%
-  for line in prop.description %}
+  for line in prop.description %}{%
+      if line %}
         {{ line }}{%
+      else %}
+{%    endif %}{%
   endfor %}
         """{%
   if prop.readAccess %}