line-protocol-parser 1.1.4__tar.gz → 2.0.1__tar.gz

{line_protocol_parser-1.1.4/line_protocol_parser.egg-info → line_protocol_parser-2.0.1}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: line-protocol-parser
-Version: 1.1.4
+Version: 2.0.1
 Summary: Parse InfluxDB line protocol string into Python dictionary
 Home-page: https://github.com/Penlect/line-protocol-parser
 Author: Daniel Andersson
@@ -18,17 +18,14 @@ Classifier: Operating System :: POSIX :: Linux
 Classifier: Operating System :: MacOS
 Classifier: Operating System :: Microsoft :: Windows :: Windows 10
 Classifier: Programming Language :: C
-Classifier: Programming Language :: Python :: 3.5
-Classifier: Programming Language :: Python :: 3.6
-Classifier: Programming Language :: Python :: 3.7
-Classifier: Programming Language :: Python :: 3.8
-Classifier: Programming Language :: Python :: 3.9
 Classifier: Programming Language :: Python :: 3.10
 Classifier: Programming Language :: Python :: 3.11
 Classifier: Programming Language :: Python :: 3.12
 Classifier: Programming Language :: Python :: 3.13
 Classifier: Programming Language :: Python :: 3.14
+Classifier: Programming Language :: Python :: 3.15
 Classifier: Programming Language :: Python :: Implementation :: CPython
+Requires-Python: >=3.10
 License-File: LICENSE.md
 Dynamic: author
 Dynamic: author-email
@@ -38,6 +35,7 @@ Dynamic: home-page
 Dynamic: keywords
 Dynamic: license
 Dynamic: license-file
+Dynamic: requires-python
 Dynamic: summary
 
 Welcome to InfluxDB line-protocol-parser
@@ -68,10 +66,25 @@ The line protocol has the following format:
 
 and is documented here: `InfluxDB line protocol`_.
 
+This parser is aligned with archived InfluxDB v1.2 single-line parser
+semantics for standard text inputs. When an input point omits the timestamp,
+``parse_line()`` returns ``None`` for ``time`` so omission remains distinct
+from an explicit ``0`` timestamp. Leading ``#`` comment lines, including
+lines with leading whitespace before ``#``, are treated as valid input and
+``parse_line()`` returns ``None`` for those lines as well. The parser also
+accepts the same top-level whitespace skipping before measurements, fields,
+and timestamps that the archived v1.2 parser tolerated, along with trailing
+spaces after the optional timestamp. The combined measurement/tag key is
+limited to 65535 bytes, matching the archived parser limit.
+Unsigned ``123u`` field values are retained as a package extension even though
+they are not documented in the archived v1.2 reference.
+
 The ``line_protocol_parser`` module only contains the ``parse_line`` function and the ``LineFormatError`` exception which is raised on failure.
 
 Installation
 ^^^^^^^^^^^^
+Python 3.10 or newer is required.
+
 From PyPI:
 
 .. code-block:: bash
@@ -102,6 +115,7 @@ Use Case 1: Read points from a file
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 Suppose you have a text file with influxDB measurement points, "my_influxDB_points.txt"::
 
+    # generated by sensor gateway
     myMeasurement,someTag=A temperature=37.0 1570977942581909918
     myMeasurement,someTag=A temperature=37.3 1570977942581910000
     myMeasurement,someTag=A temperature=36.9 1570977942581912345
@@ -115,7 +129,9 @@ Then you can load each line into a dicitonary to be printed like this:
     >>> from line_protocol_parser import parse_line
     >>> with open('my_influxDB_points.txt', 'r') as f_obj:
     ...     for line in f_obj:
-    ...         print(parse_line(line))
+    ...         point = parse_line(line)
+    ...         if point is not None:
+    ...             print(point)
 
 
 Use Case 2: InfluxDB subscriptions
@@ -165,7 +181,9 @@ Create a python file *server.py* with the following content:
         def do_POST(self):
             content_length = int(self.headers['Content-Length'])
             post_data = self.rfile.read(content_length)
-            pprint(parse_line(post_data))
+            point = parse_line(post_data)
+            if point is not None:
+                pprint(point)
             self.send_response(200)
             self.end_headers()
 
@@ -209,6 +227,12 @@ If you are not interested in the Python wrapper you may find the pure-c files us
 * ``include/line_protocol_parser.h``
 * ``src/line_protocol_parser.c``
 
+The C API keeps the original point-or-error contract. If you want to skip
+leading ``#`` comment lines in C code, filter those lines before calling
+``LP_parse_line()``. The C API accepts NUL-terminated strings only, while the
+Python wrapper rejects embedded NUL bytes instead of silently truncating
+input.
+
 Example:
 
 .. code-block:: c
@@ -237,7 +261,7 @@ Changelog
 ^^^^^^^^^
 The changelog is maintained in the debian directory, please check there: `changelog <debian/changelog>`_.
 
-.. _line protocol: https://docs.influxdata.com/influxdb/latest/write_protocols/line_protocol_reference/
-.. _InfluxDB line protocol: https://docs.influxdata.com/influxdb/latest/write_protocols/line_protocol_reference/
+.. _line protocol: https://archive.docs.influxdata.com/influxdb/v1.2/write_protocols/line_protocol_reference/
+.. _InfluxDB line protocol: https://archive.docs.influxdata.com/influxdb/v1.2/write_protocols/line_protocol_reference/
 .. _InfluxDB Subscriptions: https://docs.influxdata.com/influxdb/latest/administration/subscription-management/
 .. _InfluxDB container: https://hub.docker.com/_/influxdb

{line_protocol_parser-1.1.4 → line_protocol_parser-2.0.1}/README.rst

@@ -26,10 +26,25 @@ The line protocol has the following format:
 
 and is documented here: `InfluxDB line protocol`_.
 
+This parser is aligned with archived InfluxDB v1.2 single-line parser
+semantics for standard text inputs. When an input point omits the timestamp,
+``parse_line()`` returns ``None`` for ``time`` so omission remains distinct
+from an explicit ``0`` timestamp. Leading ``#`` comment lines, including
+lines with leading whitespace before ``#``, are treated as valid input and
+``parse_line()`` returns ``None`` for those lines as well. The parser also
+accepts the same top-level whitespace skipping before measurements, fields,
+and timestamps that the archived v1.2 parser tolerated, along with trailing
+spaces after the optional timestamp. The combined measurement/tag key is
+limited to 65535 bytes, matching the archived parser limit.
+Unsigned ``123u`` field values are retained as a package extension even though
+they are not documented in the archived v1.2 reference.
+
 The ``line_protocol_parser`` module only contains the ``parse_line`` function and the ``LineFormatError`` exception which is raised on failure.
 
 Installation
 ^^^^^^^^^^^^
+Python 3.10 or newer is required.
+
 From PyPI:
 
 .. code-block:: bash
@@ -60,6 +75,7 @@ Use Case 1: Read points from a file
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 Suppose you have a text file with influxDB measurement points, "my_influxDB_points.txt"::
 
+    # generated by sensor gateway
     myMeasurement,someTag=A temperature=37.0 1570977942581909918
     myMeasurement,someTag=A temperature=37.3 1570977942581910000
     myMeasurement,someTag=A temperature=36.9 1570977942581912345
@@ -73,7 +89,9 @@ Then you can load each line into a dicitonary to be printed like this:
     >>> from line_protocol_parser import parse_line
     >>> with open('my_influxDB_points.txt', 'r') as f_obj:
     ...     for line in f_obj:
-    ...         print(parse_line(line))
+    ...         point = parse_line(line)
+    ...         if point is not None:
+    ...             print(point)
 
 
 Use Case 2: InfluxDB subscriptions
@@ -123,7 +141,9 @@ Create a python file *server.py* with the following content:
         def do_POST(self):
             content_length = int(self.headers['Content-Length'])
             post_data = self.rfile.read(content_length)
-            pprint(parse_line(post_data))
+            point = parse_line(post_data)
+            if point is not None:
+                pprint(point)
             self.send_response(200)
             self.end_headers()
 
@@ -167,6 +187,12 @@ If you are not interested in the Python wrapper you may find the pure-c files us
 * ``include/line_protocol_parser.h``
 * ``src/line_protocol_parser.c``
 
+The C API keeps the original point-or-error contract. If you want to skip
+leading ``#`` comment lines in C code, filter those lines before calling
+``LP_parse_line()``. The C API accepts NUL-terminated strings only, while the
+Python wrapper rejects embedded NUL bytes instead of silently truncating
+input.
+
 Example:
 
 .. code-block:: c
@@ -195,7 +221,7 @@ Changelog
 ^^^^^^^^^
 The changelog is maintained in the debian directory, please check there: `changelog <debian/changelog>`_.
 
-.. _line protocol: https://docs.influxdata.com/influxdb/latest/write_protocols/line_protocol_reference/
-.. _InfluxDB line protocol: https://docs.influxdata.com/influxdb/latest/write_protocols/line_protocol_reference/
+.. _line protocol: https://archive.docs.influxdata.com/influxdb/v1.2/write_protocols/line_protocol_reference/
+.. _InfluxDB line protocol: https://archive.docs.influxdata.com/influxdb/v1.2/write_protocols/line_protocol_reference/
 .. _InfluxDB Subscriptions: https://docs.influxdata.com/influxdb/latest/administration/subscription-management/
 .. _InfluxDB container: https://hub.docker.com/_/influxdb

{line_protocol_parser-1.1.4 → line_protocol_parser-2.0.1}/include/line_protocol_parser.h

@@ -1,6 +1,9 @@
 #ifndef LINEPROTOCOLPARSER_H
 #define LINEPROTOCOLPARSER_H
 
+#include <stdbool.h>
+#include <stdint.h>
+
 /* Error return codes of `LP_parse_line` */
 #define LP_MEMORY_ERROR 1
 #define LP_LINE_EMPTY 2
@@ -13,6 +16,7 @@
 #define LP_FIELD_VALUE_ERROR 9
 #define LP_FIELD_VALUE_TYPE_ERROR 10
 #define LP_TIME_ERROR 11
+#define LP_KEY_TOO_LONG_ERROR 12
 
 /* Indicates which type a field has */
 enum LP_ValueType {
@@ -49,7 +53,9 @@ struct LP_Point {
     char *measurement;
     struct LP_Item *fields;
     struct LP_Item *tags;
-    unsigned long long time;
+    /* `time` is only valid when `has_time` is true. */
+    bool has_time;
+    int64_t time;
     struct LP_Point *next_point;
 };
 

{line_protocol_parser-1.1.4 → line_protocol_parser-2.0.1}/line_protocol_parser/__init__.py

@@ -1,4 +1,4 @@
-"""Module for parsing InfluxDB line protocol strings"""
+"""Parse InfluxDB line protocol strings into dictionaries or ``None``."""
 from ._line_protocol_parser import parse_line, LineFormatError
 
 # Module metadata
@@ -9,4 +9,4 @@ __contact__ = __email__
 __copyright__ = 'Copyright (c) 2019 Daniel Andersson'
 __license__ = 'MIT'
 __url__ = "https://github.com/Penlect/line-protocol-parser"
-__version__ = '1.1.4'
+__version__ = '2.0.1'

{line_protocol_parser-1.1.4 → line_protocol_parser-2.0.1/line_protocol_parser.egg-info}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: line-protocol-parser
-Version: 1.1.4
+Version: 2.0.1
 Summary: Parse InfluxDB line protocol string into Python dictionary
 Home-page: https://github.com/Penlect/line-protocol-parser
 Author: Daniel Andersson
@@ -18,17 +18,14 @@ Classifier: Operating System :: POSIX :: Linux
 Classifier: Operating System :: MacOS
 Classifier: Operating System :: Microsoft :: Windows :: Windows 10
 Classifier: Programming Language :: C
-Classifier: Programming Language :: Python :: 3.5
-Classifier: Programming Language :: Python :: 3.6
-Classifier: Programming Language :: Python :: 3.7
-Classifier: Programming Language :: Python :: 3.8
-Classifier: Programming Language :: Python :: 3.9
 Classifier: Programming Language :: Python :: 3.10
 Classifier: Programming Language :: Python :: 3.11
 Classifier: Programming Language :: Python :: 3.12
 Classifier: Programming Language :: Python :: 3.13
 Classifier: Programming Language :: Python :: 3.14
+Classifier: Programming Language :: Python :: 3.15
 Classifier: Programming Language :: Python :: Implementation :: CPython
+Requires-Python: >=3.10
 License-File: LICENSE.md
 Dynamic: author
 Dynamic: author-email
@@ -38,6 +35,7 @@ Dynamic: home-page
 Dynamic: keywords
 Dynamic: license
 Dynamic: license-file
+Dynamic: requires-python
 Dynamic: summary
 
 Welcome to InfluxDB line-protocol-parser
@@ -68,10 +66,25 @@ The line protocol has the following format:
 
 and is documented here: `InfluxDB line protocol`_.
 
+This parser is aligned with archived InfluxDB v1.2 single-line parser
+semantics for standard text inputs. When an input point omits the timestamp,
+``parse_line()`` returns ``None`` for ``time`` so omission remains distinct
+from an explicit ``0`` timestamp. Leading ``#`` comment lines, including
+lines with leading whitespace before ``#``, are treated as valid input and
+``parse_line()`` returns ``None`` for those lines as well. The parser also
+accepts the same top-level whitespace skipping before measurements, fields,
+and timestamps that the archived v1.2 parser tolerated, along with trailing
+spaces after the optional timestamp. The combined measurement/tag key is
+limited to 65535 bytes, matching the archived parser limit.
+Unsigned ``123u`` field values are retained as a package extension even though
+they are not documented in the archived v1.2 reference.
+
 The ``line_protocol_parser`` module only contains the ``parse_line`` function and the ``LineFormatError`` exception which is raised on failure.
 
 Installation
 ^^^^^^^^^^^^
+Python 3.10 or newer is required.
+
 From PyPI:
 
 .. code-block:: bash
@@ -102,6 +115,7 @@ Use Case 1: Read points from a file
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 Suppose you have a text file with influxDB measurement points, "my_influxDB_points.txt"::
 
+    # generated by sensor gateway
     myMeasurement,someTag=A temperature=37.0 1570977942581909918
     myMeasurement,someTag=A temperature=37.3 1570977942581910000
     myMeasurement,someTag=A temperature=36.9 1570977942581912345
@@ -115,7 +129,9 @@ Then you can load each line into a dicitonary to be printed like this:
     >>> from line_protocol_parser import parse_line
     >>> with open('my_influxDB_points.txt', 'r') as f_obj:
     ...     for line in f_obj:
-    ...         print(parse_line(line))
+    ...         point = parse_line(line)
+    ...         if point is not None:
+    ...             print(point)
 
 
 Use Case 2: InfluxDB subscriptions
@@ -165,7 +181,9 @@ Create a python file *server.py* with the following content:
         def do_POST(self):
             content_length = int(self.headers['Content-Length'])
             post_data = self.rfile.read(content_length)
-            pprint(parse_line(post_data))
+            point = parse_line(post_data)
+            if point is not None:
+                pprint(point)
             self.send_response(200)
             self.end_headers()
 
@@ -209,6 +227,12 @@ If you are not interested in the Python wrapper you may find the pure-c files us
 * ``include/line_protocol_parser.h``
 * ``src/line_protocol_parser.c``
 
+The C API keeps the original point-or-error contract. If you want to skip
+leading ``#`` comment lines in C code, filter those lines before calling
+``LP_parse_line()``. The C API accepts NUL-terminated strings only, while the
+Python wrapper rejects embedded NUL bytes instead of silently truncating
+input.
+
 Example:
 
 .. code-block:: c
@@ -237,7 +261,7 @@ Changelog
 ^^^^^^^^^
 The changelog is maintained in the debian directory, please check there: `changelog <debian/changelog>`_.
 
-.. _line protocol: https://docs.influxdata.com/influxdb/latest/write_protocols/line_protocol_reference/
-.. _InfluxDB line protocol: https://docs.influxdata.com/influxdb/latest/write_protocols/line_protocol_reference/
+.. _line protocol: https://archive.docs.influxdata.com/influxdb/v1.2/write_protocols/line_protocol_reference/
+.. _InfluxDB line protocol: https://archive.docs.influxdata.com/influxdb/v1.2/write_protocols/line_protocol_reference/
 .. _InfluxDB Subscriptions: https://docs.influxdata.com/influxdb/latest/administration/subscription-management/
 .. _InfluxDB container: https://hub.docker.com/_/influxdb

{line_protocol_parser-1.1.4 → line_protocol_parser-2.0.1}/setup.py

@@ -30,6 +30,7 @@ setup(
     license=__license__,
     keywords='InfluxDB influx line protocol parser reader',
     url=__url__,
+    python_requires='>=3.10',
     ext_modules=[
         Extension(
             'line_protocol_parser._line_protocol_parser',
@@ -56,16 +57,12 @@ setup(
         'Operating System :: MacOS',
         'Operating System :: Microsoft :: Windows :: Windows 10',
         'Programming Language :: C',
-        'Programming Language :: Python :: 3.5',
-        'Programming Language :: Python :: 3.6',
-        'Programming Language :: Python :: 3.7',
-        'Programming Language :: Python :: 3.8',
-        'Programming Language :: Python :: 3.9',
         'Programming Language :: Python :: 3.10',
         'Programming Language :: Python :: 3.11',
         'Programming Language :: Python :: 3.12',
         'Programming Language :: Python :: 3.13',
         'Programming Language :: Python :: 3.14',
+        'Programming Language :: Python :: 3.15',
         'Programming Language :: Python :: Implementation :: CPython'
     ]
 )