From c99ac4a2109a1602c0d39276a3eb189e6b6f1cd7 Mon Sep 17 00:00:00 2001
From: Dashie <dashie@sigpipe.me>
Date: Tue, 9 Aug 2022 11:56:21 +0200
Subject: [PATCH] py3: xrange is now range
---
.../parser/policies/PacketRelatedMapSectorsPolicy.py | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/server/trackdirect/parser/policies/PacketRelatedMapSectorsPolicy.py b/server/trackdirect/parser/policies/PacketRelatedMapSectorsPolicy.py
index 08767d9..a0595ef 100644
--- a/server/trackdirect/parser/policies/PacketRelatedMapSectorsPolicy.py
+++ b/server/trackdirect/parser/policies/PacketRelatedMapSectorsPolicy.py
@@ -125,8 +125,8 @@ class PacketRelatedMapSectorsPolicy():
# lat interval: 0 - 18000000
# lng interval: 0 - 00003600
# Maybe we can do this smarter? Currently we are adding many map-sectors that is not relevant
- for lat in xrange(minLat, maxLat, 20000):
- for lng in xrange(minLng, maxLng, 5):
+ for lat in range(minLat, maxLat, 20000):
+ for lng in range(minLng, maxLng, 5):
mapSectorAreaCode = lat+lng
if (mapSectorAreaCode != prevPacketAreaCode and mapSectorAreaCode != newPacketAreaCode):
relatedMapSectors.append(mapSectorAreaCode)
--
GitLab