fix: logItem nano time now become fourth pos in the ctor, which may cause a breaking change. (#347)

Author: crimson-gao

HISTORY.md

@@ -1,5 +1,14 @@
 # Release History
 
+## 0.9.36 (2025-11-13)
+
+**Breaking Changes**
+
+Fix: Adapt to [LogItem](aliyun/log/logitem.py) breaking change from v0.8.10
+
+Updates code to reflect the new LogItem signature, where the
+`nano_time_part` argument moved from the 3rd to the 4th position.
+
 ## 0.9.35 (2025-11-05)
 
 **Feature**

aliyun/log/logitem.py

@@ -17,9 +17,12 @@ class LogItem(object):
 
     :type contents: tuple(key-value) list
     :param contents: the data of the log item, including many (key,value) pairs.
+
+    :type time_nano_part: int
+    :param time_nano_part: time nano part of the log item, ranges from 0 to 999999999.
     """
 
-    def __init__(self, timestamp=None, time_nano_part=None, contents=None):
+    def __init__(self, timestamp=None, contents=None, time_nano_part=None):
         nano_time = int(time.time() * 10**9)
         self.timestamp = int(timestamp) if timestamp else int(nano_time / 1000000000)
         # milliseconds

aliyun/log/version.py

@@ -1,4 +1,4 @@
-__version__ = '0.9.35'
+__version__ = '0.9.36'
 
 import sys
 OS_VERSION = str(sys.platform)