This file is indexed.

/usr/lib/python3/dist-packages/serpent-1.8.egg-info is in python3-serpent 1.8-1.

This file is owned by root:root, with mode 0o644.

The actual contents of the file can be viewed below.

  1
  2
  3
  4
  5
  6
  7
  8
  9
 10
 11
 12
 13
 14
 15
 16
 17
 18
 19
 20
 21
 22
 23
 24
 25
 26
 27
 28
 29
 30
 31
 32
 33
 34
 35
 36
 37
 38
 39
 40
 41
 42
 43
 44
 45
 46
 47
 48
 49
 50
 51
 52
 53
 54
 55
 56
 57
 58
 59
 60
 61
 62
 63
 64
 65
 66
 67
 68
 69
 70
 71
 72
 73
 74
 75
 76
 77
 78
 79
 80
 81
 82
 83
 84
 85
 86
 87
 88
 89
 90
 91
 92
 93
 94
 95
 96
 97
 98
 99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
Metadata-Version: 1.1
Name: serpent
Version: 1.8
Summary: Serialization based on ast.literal_eval
Home-page: UNKNOWN
Author: Irmen de Jong
Author-email: irmen@razorvine.net
License: MIT
Description: 
        Serpent is a simple serialization library based on ast.literal_eval.
        
        Because it only serializes literals and recreates the objects using ast.literal_eval(),
        the serialized data is safe to transport to other machines (over the network for instance)
        and de-serialize it there.
        
        *There is also a Java and a .NET (C#) implementation available. This allows for easy data transfer between the various ecosystems.
        You can get the full source distribution, a Java .jar file, and a .NET assembly dll.*  `Download location here <http://irmen.home.xs4all.nl/serpent/>`_
        
        
        **API**
        
        - ``ser_bytes = serpent.dumps(obj, indent=False, set_literals=True, module_in_classname=False):``      # serialize obj tree to bytes
        - ``obj = serpent.loads(ser_bytes)``     # deserialize bytes back into object tree
        - You can use ``ast.literal_eval`` yourself to deserialize, but ``serpent.deserialize`` works around a few corner cases. See source for details.
        
        Serpent is more sophisticated than a simple repr() + literal_eval():
        
        - it serializes directly to bytes (utf-8 encoded), instead of a string, so it can immediately be saved to a file or sent over a socket
        - it encodes byte-types as base-64 instead of inefficient escaping notation that repr would use (this does mean you have
          to base-64 decode these strings manually on the receiving side to get your bytes back)
        - it contains a few custom serializers for several additional Python types such as uuid, datetime, array and decimal
        - it tries to serialize unrecognised types as a dict (you can control this with __getstate__ on your own types)
        - it can create a pretty-printed (indented) output for readability purposes
        - it outputs the keys of sets and dicts in alphabetical order (when pretty-printing)
        - it works around a few quirks of ast.literal_eval() on the various Python implementations
        
        Serpent allows comments in the serialized data (because it is just Python source code).
        Serpent can't serialize object graphs (when an object refers to itself); it will then crash with a ValueError pointing out the problem.
        
        Works with Python 2.6+ (including 3.x), IronPython 2.7+, Jython 2.7+.
        
        **FAQ**
        
        - Why not use XML? Answer: because XML.
        - Why not use JSON? Answer: because JSON is quite limited in the number of datatypes it supports, and you can't use comments in a JSON file.
        - Why not use pickle? Answer: because pickle has security problems.
        - Why not use ``repr()``/``ast.literal_eval()``? See above; serpent is a superset of this and provides more convenience. Serpent provides automatic serialization mappings for types other than the builtin primitive types. ``repr()`` can't serialize these to literals that ``ast.literal_eval()`` understands.
        - Why not a binary format? Answer: because binary isn't readable by humans.
        - But I don't care about readability. Answer: doesn't matter, ``ast.literal_eval()`` wants a literal string, so that is what we produce.
        - But I want better performance. Answer: ok, maybe you shouldn't use serpent in this case. Find an efficient binary protocol (protobuf?)
        - Why only Python, Java and C#/.NET, but no bindings for insert-favorite-language-here? Answer: I don't speak that language. Maybe you could port serpent yourself?
        - Where is the source?  It's on Github: https://github.com/irmen/Serpent
        - Can I use it everywhere?  Sure, as long as you keep the copyright and disclaimer somewhere. See http://opensource.org/licenses/MIT
        
        **Demo**
        
        .. code:: python
        
         # This demo script is written for Python 3.2+
         # -*- coding: utf-8 -*-
         from __future__ import print_function
         import ast
         import uuid
         import datetime
         import pprint
         import serpent
        
        
         class DemoClass:
             def __init__(self):
                 self.i=42
                 self.b=False
        
         data = {
             "names": ["Harry", "Sally", "Peter"],
             "big": 2**200,
             "colorset": { "red", "green" },
             "id": uuid.uuid4(),
             "timestamp": datetime.datetime.now(),
             "class": DemoClass(),
             "unicode": "€"
         }
        
         # serialize it
         ser = serpent.dumps(data, indent=True)
         open("data.serpent", "wb").write(ser)
        
         print("Serialized form:")
         print(ser.decode("utf-8"))
        
         # read it back
         data = serpent.load(open("data.serpent", "rb"))
         print("Data:")
         pprint.pprint(data)
        
         # you can also use ast.literal_eval if you like
         ser_string = open("data.serpent", "r", encoding="utf-8").read()
         data2 = ast.literal_eval(ser_string)
        
         assert data2==data
        
        
        When you run this (with python 3.2+) it prints:
        
        .. code:: python
        
         Serialized form:
         # serpent utf-8 python3.2
         {
           'big': 1606938044258990275541962092341162602522202993782792835301376,
           'class': {
             '__class__': 'DemoClass',
             'b': False,
             'i': 42
           },
           'colorset': {
             'green',
             'red'
           },
           'id': 'e461378a-201d-4844-8119-7c1570d9d186',
           'names': [
             'Harry',
             'Sally',
             'Peter'
           ],
           'timestamp': '2013-04-02T00:23:00.924000',
           'unicode': '€'
         }
         Data:
         {'big': 1606938044258990275541962092341162602522202993782792835301376,
          'class': {'__class__': 'DemoClass', 'b': False, 'i': 42},
          'colorset': {'green', 'red'},
          'id': 'e461378a-201d-4844-8119-7c1570d9d186',
          'names': ['Harry', 'Sally', 'Peter'],
          'timestamp': '2013-04-02T00:23:00.924000',
          'unicode': '€'}
            
Keywords: serialization
Platform: any
Classifier: Development Status :: 4 - Beta
Classifier: Intended Audience :: Developers
Classifier: License :: OSI Approved :: MIT License
Classifier: Natural Language :: English
Classifier: Operating System :: OS Independent
Classifier: Programming Language :: Python
Classifier: Programming Language :: Python :: 2
Classifier: Programming Language :: Python :: 3
Classifier: Topic :: Software Development