From 785c823fa269a173f5b526e0fd856b0edb5aa61e Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Jan=20Kundr=C3=A1t?= Date: Sat, 23 May 2020 15:17:41 +0200 Subject: [PATCH] coding style: separate property definitions from each other While not strictly needed in Python, it's much clearer this way. Change-Id: I5f8caccde6440cb4032aae5deae577d328834a75 --- gnpy/tools/service_sheet.py | 1 + gnpy/topology/request.py | 2 ++ 2 files changed, 3 insertions(+) diff --git a/gnpy/tools/service_sheet.py b/gnpy/tools/service_sheet.py index 1a9c07b0..20254a0c 100644 --- a/gnpy/tools/service_sheet.py +++ b/gnpy/tools/service_sheet.py @@ -121,6 +121,7 @@ class Request_element(Element): self.path_bandwidth = 0 uid = property(lambda self: repr(self)) + @property def pathrequest(self): # Default assumption for bidir is False diff --git a/gnpy/topology/request.py b/gnpy/topology/request.py index cfa5a814..fe8a7614 100644 --- a/gnpy/topology/request.py +++ b/gnpy/topology/request.py @@ -140,7 +140,9 @@ class ResultElement(Element): # starting implementing reversed properties in case of bidir demand if reversed_computed_path is not None: self.reversed_computed_path = reversed_computed_path + uid = property(lambda self: repr(self)) + @property def detailed_path_json(self): """ a function that builds path object for normal and blocking cases