Server IP : 172.24.0.40 / Your IP : 216.73.216.10 Web Server : Apache System : Linux dbweb26.ust.edu.ph 4.18.0-513.5.1.el8_9.x86_64 #1 SMP Fri Sep 29 05:21:10 EDT 2023 x86_64 User : apache ( 48) PHP Version : 8.2.18 Disable Function : NONE MySQL : OFF | cURL : ON | WGET : ON | Perl : ON | Python : OFF | Sudo : ON | Pkexec : ON Directory : /usr/lib64/python3.6/site-packages/rhsm/__pycache__/ |
Upload File : |
3 a�e�1 � @ s` d dl mZmZmZ d dlZd dlZd dlZd dlmZ d dl m Z dZdZG dd� de �ZdS ) � )�print_function�division�absolute_importN)�GhettoBitStream)�HuffmanNodezPATH ENDZlistingc @ sz e Zd ZdZdd� Zdd� Zdd� Zdd d �Zedd� �Z e d d� �Ze dd� �Zedd� �Z e dd� �Zedd� �ZdS )�PathTreeat This builds and makes available a tree that represents matchable paths. A path must be matched starting from its root and the root of the tree, matching one segment at a time. There are three trees involved in the process, and that can get confusing. 1) Word Tree: This is a Huffman tree made from the word list provided at the beginning of the data stream. 2) Huffman Path Tree: This is a Huffman tree made of nodes whose values will become nodes in the Path Tree. This tree exists so there can be a Huffman code associated with each node in the Path Tree. However, the Path Tree itself will arrange this data much differently. 3) Path Tree: This is the tree used to match paths. Each node is a dict where keys are path segments (the middle part of /.../) and each value is a list of other nodes. c C sn | j |�\}}tj|� tdd� |D ��}t|�}| j|�}tj|� tdd� |D ��}| j||||�| _dS )a� Uncompresses data into a tree that can be traversed for matching paths :param data: binary data as read from a file or pulled directly out of a certificate extension. Data should be compressed with huffman coding as described for v3 entitlement certificates :type data: binary string c s s | ]}|j |jfV qd S )N)�code�value)�.0�node� r � /usr/lib64/python3.6/pathtree.py� <genexpr>>