table-stream 0.1.0__tar.gz

table_stream-0.1.0/PKG-INFO

@@ -0,0 +1,104 @@
+Metadata-Version: 2.4
+Name: table_stream
+Version: 0.1.0
+Summary: Tipos de dados e implementações para o uso em tabelas.
+Requires-Python: >=3.14
+Description-Content-Type: text/markdown
+Requires-Dist: odfpy>=1.4.1
+Requires-Dist: openpyxl>=3.1.5
+Requires-Dist: pandas>=3.0.0
+Requires-Dist: soup-files>=1.4.2
+
+# table
+
+
+
+## Getting started
+
+To make it easy for you to get started with GitLab, here's a list of recommended next steps.
+
+Already a pro? Just edit this README.md and make it your own. Want to make it easy? [Use the template at the bottom](#editing-this-readme)!
+
+## Add your files
+
+* [Create](https://docs.gitlab.com/user/project/repository/web_editor/#create-a-file) or [upload](https://docs.gitlab.com/user/project/repository/web_editor/#upload-a-file) files
+* [Add files using the command line](https://docs.gitlab.com/topics/git/add_files/#add-files-to-a-git-repository) or push an existing Git repository with the following command:
+
+```
+cd existing_repo
+git remote add origin https://gitlab.com/bschaves/table.git
+git branch -M main
+git push -uf origin main
+```
+
+## Integrate with your tools
+
+* [Set up project integrations](https://gitlab.com/bschaves/table/-/settings/integrations)
+
+## Collaborate with your team
+
+* [Invite team members and collaborators](https://docs.gitlab.com/user/project/members/)
+* [Create a new merge request](https://docs.gitlab.com/user/project/merge_requests/creating_merge_requests/)
+* [Automatically close issues from merge requests](https://docs.gitlab.com/user/project/issues/managing_issues/#closing-issues-automatically)
+* [Enable merge request approvals](https://docs.gitlab.com/user/project/merge_requests/approvals/)
+* [Set auto-merge](https://docs.gitlab.com/user/project/merge_requests/auto_merge/)
+
+## Test and Deploy
+
+Use the built-in continuous integration in GitLab.
+
+* [Get started with GitLab CI/CD](https://docs.gitlab.com/ci/quick_start/)
+* [Analyze your code for known vulnerabilities with Static Application Security Testing (SAST)](https://docs.gitlab.com/user/application_security/sast/)
+* [Deploy to Kubernetes, Amazon EC2, or Amazon ECS using Auto Deploy](https://docs.gitlab.com/topics/autodevops/requirements/)
+* [Use pull-based deployments for improved Kubernetes management](https://docs.gitlab.com/user/clusters/agent/)
+* [Set up protected environments](https://docs.gitlab.com/ci/environments/protected_environments/)
+
+***
+
+# Editing this README
+
+When you're ready to make this README your own, just edit this file and use the handy template below (or feel free to structure it however you want - this is just a starting point!). Thanks to [makeareadme.com](https://www.makeareadme.com/) for this template.
+
+## Suggestions for a good README
+
+Every project is different, so consider which of these sections apply to yours. The sections used in the template are suggestions for most open source projects. Also keep in mind that while a README can be too long and detailed, too long is better than too short. If you think your README is too long, consider utilizing another form of documentation rather than cutting out information.
+
+## Name
+Choose a self-explaining name for your project.
+
+## Description
+Let people know what your project can do specifically. Provide context and add a link to any reference visitors might be unfamiliar with. A list of Features or a Background subsection can also be added here. If there are alternatives to your project, this is a good place to list differentiating factors.
+
+## Badges
+On some READMEs, you may see small images that convey metadata, such as whether or not all the tests are passing for the project. You can use Shields to add some to your README. Many services also have instructions for adding a badge.
+
+## Visuals
+Depending on what you are making, it can be a good idea to include screenshots or even a video (you'll frequently see GIFs rather than actual videos). Tools like ttygif can help, but check out Asciinema for a more sophisticated method.
+
+## Installation
+Within a particular ecosystem, there may be a common way of installing things, such as using Yarn, NuGet, or Homebrew. However, consider the possibility that whoever is reading your README is a novice and would like more guidance. Listing specific steps helps remove ambiguity and gets people to using your project as quickly as possible. If it only runs in a specific context like a particular programming language version or operating system or has dependencies that have to be installed manually, also add a Requirements subsection.
+
+## Usage
+Use examples liberally, and show the expected output if you can. It's helpful to have inline the smallest example of usage that you can demonstrate, while providing links to more sophisticated examples if they are too long to reasonably include in the README.
+
+## Support
+Tell people where they can go to for help. It can be any combination of an issue tracker, a chat room, an email address, etc.
+
+## Roadmap
+If you have ideas for releases in the future, it is a good idea to list them in the README.
+
+## Contributing
+State if you are open to contributions and what your requirements are for accepting them.
+
+For people who want to make changes to your project, it's helpful to have some documentation on how to get started. Perhaps there is a script that they should run or some environment variables that they need to set. Make these steps explicit. These instructions could also be useful to your future self.
+
+You can also document commands to lint the code or run tests. These steps help to ensure high code quality and reduce the likelihood that the changes inadvertently break something. Having instructions for running tests is especially helpful if it requires external setup, such as starting a Selenium server for testing in a browser.
+
+## Authors and acknowledgment
+Show your appreciation to those who have contributed to the project.
+
+## License
+For open source projects, say how it is licensed.
+
+## Project status
+If you have run out of energy or time for your project, put a note at the top of the README saying that development has slowed down or stopped completely. Someone may choose to fork your project or volunteer to step in as a maintainer or owner, allowing your project to keep going. You can also make an explicit request for maintainers.

table_stream-0.1.0/README.md

@@ -0,0 +1,93 @@
+# table
+
+
+
+## Getting started
+
+To make it easy for you to get started with GitLab, here's a list of recommended next steps.
+
+Already a pro? Just edit this README.md and make it your own. Want to make it easy? [Use the template at the bottom](#editing-this-readme)!
+
+## Add your files
+
+* [Create](https://docs.gitlab.com/user/project/repository/web_editor/#create-a-file) or [upload](https://docs.gitlab.com/user/project/repository/web_editor/#upload-a-file) files
+* [Add files using the command line](https://docs.gitlab.com/topics/git/add_files/#add-files-to-a-git-repository) or push an existing Git repository with the following command:
+
+```
+cd existing_repo
+git remote add origin https://gitlab.com/bschaves/table.git
+git branch -M main
+git push -uf origin main
+```
+
+## Integrate with your tools
+
+* [Set up project integrations](https://gitlab.com/bschaves/table/-/settings/integrations)
+
+## Collaborate with your team
+
+* [Invite team members and collaborators](https://docs.gitlab.com/user/project/members/)
+* [Create a new merge request](https://docs.gitlab.com/user/project/merge_requests/creating_merge_requests/)
+* [Automatically close issues from merge requests](https://docs.gitlab.com/user/project/issues/managing_issues/#closing-issues-automatically)
+* [Enable merge request approvals](https://docs.gitlab.com/user/project/merge_requests/approvals/)
+* [Set auto-merge](https://docs.gitlab.com/user/project/merge_requests/auto_merge/)
+
+## Test and Deploy
+
+Use the built-in continuous integration in GitLab.
+
+* [Get started with GitLab CI/CD](https://docs.gitlab.com/ci/quick_start/)
+* [Analyze your code for known vulnerabilities with Static Application Security Testing (SAST)](https://docs.gitlab.com/user/application_security/sast/)
+* [Deploy to Kubernetes, Amazon EC2, or Amazon ECS using Auto Deploy](https://docs.gitlab.com/topics/autodevops/requirements/)
+* [Use pull-based deployments for improved Kubernetes management](https://docs.gitlab.com/user/clusters/agent/)
+* [Set up protected environments](https://docs.gitlab.com/ci/environments/protected_environments/)
+
+***
+
+# Editing this README
+
+When you're ready to make this README your own, just edit this file and use the handy template below (or feel free to structure it however you want - this is just a starting point!). Thanks to [makeareadme.com](https://www.makeareadme.com/) for this template.
+
+## Suggestions for a good README
+
+Every project is different, so consider which of these sections apply to yours. The sections used in the template are suggestions for most open source projects. Also keep in mind that while a README can be too long and detailed, too long is better than too short. If you think your README is too long, consider utilizing another form of documentation rather than cutting out information.
+
+## Name
+Choose a self-explaining name for your project.
+
+## Description
+Let people know what your project can do specifically. Provide context and add a link to any reference visitors might be unfamiliar with. A list of Features or a Background subsection can also be added here. If there are alternatives to your project, this is a good place to list differentiating factors.
+
+## Badges
+On some READMEs, you may see small images that convey metadata, such as whether or not all the tests are passing for the project. You can use Shields to add some to your README. Many services also have instructions for adding a badge.
+
+## Visuals
+Depending on what you are making, it can be a good idea to include screenshots or even a video (you'll frequently see GIFs rather than actual videos). Tools like ttygif can help, but check out Asciinema for a more sophisticated method.
+
+## Installation
+Within a particular ecosystem, there may be a common way of installing things, such as using Yarn, NuGet, or Homebrew. However, consider the possibility that whoever is reading your README is a novice and would like more guidance. Listing specific steps helps remove ambiguity and gets people to using your project as quickly as possible. If it only runs in a specific context like a particular programming language version or operating system or has dependencies that have to be installed manually, also add a Requirements subsection.
+
+## Usage
+Use examples liberally, and show the expected output if you can. It's helpful to have inline the smallest example of usage that you can demonstrate, while providing links to more sophisticated examples if they are too long to reasonably include in the README.
+
+## Support
+Tell people where they can go to for help. It can be any combination of an issue tracker, a chat room, an email address, etc.
+
+## Roadmap
+If you have ideas for releases in the future, it is a good idea to list them in the README.
+
+## Contributing
+State if you are open to contributions and what your requirements are for accepting them.
+
+For people who want to make changes to your project, it's helpful to have some documentation on how to get started. Perhaps there is a script that they should run or some environment variables that they need to set. Make these steps explicit. These instructions could also be useful to your future self.
+
+You can also document commands to lint the code or run tests. These steps help to ensure high code quality and reduce the likelihood that the changes inadvertently break something. Having instructions for running tests is especially helpful if it requires external setup, such as starting a Selenium server for testing in a browser.
+
+## Authors and acknowledgment
+Show your appreciation to those who have contributed to the project.
+
+## License
+For open source projects, say how it is licensed.
+
+## Project status
+If you have run out of energy or time for your project, put a note at the top of the README saying that development has slowed down or stopped completely. Someone may choose to fork your project or volunteer to step in as a maintainer or owner, allowing your project to keep going. You can also make an explicit request for maintainers.

table_stream-0.1.0/pyproject.toml

@@ -0,0 +1,41 @@
+[project]
+name = "table_stream"
+version = "0.1.0"
+description = "Tipos de dados e implementações para o uso em tabelas."
+readme = "README.md"
+requires-python = ">=3.14"
+dependencies = [
+    "odfpy>=1.4.1",
+    "openpyxl>=3.1.5",
+    "pandas>=3.0.0",
+    "soup-files>=1.4.2",
+]
+
+[dependency-groups]
+dev = [
+    "build>=1.4.0",
+    "twine>=6.2.0",
+]
+
+[tool.setuptools]
+packages = [
+    "table_stream",
+    "table_stream.base",
+    "table_stream.erros",
+    "table_stream.thread",
+    "table_stream.sheet",
+    "table_stream.sheet.csv",
+    "table_stream.sheet.excel",
+    "table_stream.sheet.ods",
+    "table_stream.sheet.parse",
+    "table_stream.sheet.interface",
+    "table_stream.sheet.load_adapter",
+    "table_stream.types",
+    "table_stream.types.workbook",
+    "table_stream.types.pattner",
+    "table_stream.types.pattner.adapter",
+    "table_stream.types.pattner.mediator",
+    "table_stream.types.pattner.observer",
+]
+
+

table_stream-0.1.0/setup.cfg

@@ -0,0 +1,4 @@
+[egg_info]
+tag_build = 
+tag_date = 0
+

table_stream-0.1.0/table_stream/__init__.py

@@ -0,0 +1,8 @@
+from .base import HashMap, hashMapName, HashMapDataFrame, HashMapDict, ArrayList, K, T
+from .types import (
+    WorkbookData, MessageNotification, Provider, Listener, EVENT_TYPE, VALUE, 
+    Mediator, ComponentMediator
+)
+from .thread import ControlledThread, ThreadConsumer
+from .sheet import SheetLoader, InterfaceSheetLoad, ParserData
+

table_stream-0.1.0/table_stream/base/__init__.py

@@ -0,0 +1,2 @@
+from .mapping import HashMap, K, T, hashMapName, ArrayList
+from .hash_map import HashMapDict, HashMapDataFrame

table_stream-0.1.0/table_stream/base/hash_map.py

@@ -0,0 +1,160 @@
+from typing import Any, Literal
+from pandas.core.api import DataFrame
+from table_stream.base.mapping import ArrayList, HashMap, T
+import json
+
+
+class HashMapDict[K, T](HashMap):
+    
+    def __init__(self, _mapping: dict[K, T] | None = None) -> None:
+        super().__init__()
+        if _mapping is None:
+            _mapping = dict()
+        self._mapping: dict[K, T] = _mapping
+    
+    def size_values(self) -> int:
+        return len(self._mapping.values())
+
+    def size_header(self) -> int:
+        return self.header().size()
+
+    def __getitem__(self, key: K) -> T:
+        return self._mapping[key]
+
+    def __setitem__(self, key: K, value: T) -> None:
+        self._mapping[key] = value
+
+    def get_hash_map_name(self) -> Literal['DICT']:
+        return "DICT"
+
+    def get_real_hash_map(self) -> dict[K, T]:
+        return self._mapping
+
+    def set_real_hash_map(self, hash_map: dict[K, T]) -> None:
+        self._mapping = hash_map
+
+    def clear(self) -> None:
+        self._mapping.clear()
+
+    def get_first(self) -> T:
+        return self._mapping[self.header().get_first()]
+
+    def set_first(self, value: T) -> None:
+        self._mapping[self.header().get_first()] = value
+
+    def get_last(self) -> T:
+        return self._mapping[self.header().get_last()]
+
+    def set_last(self, value: T) -> None:
+        self._mapping[self.header().get_last()] = value
+
+    def set_value(self, key: K, value: T) -> None:
+        self._mapping[key] = value
+
+    def get_value(self, key: K) -> T:
+        return self._mapping[key]
+
+    def header(self) -> ArrayList[K]:
+        return ArrayList(list(self._mapping.keys()))
+
+    def values(self) -> ArrayList[T]:
+        return ArrayList(list(self._mapping.values()))
+
+    def delete_items(self, keys: list[K]) -> None:
+        for k in keys:
+            self._mapping.pop(k)
+
+    def to_json(self) -> str:
+        """
+        Converte o mapa real para uma string JSON.
+        Nota: As chaves e valores devem ser serializáveis pelo módulo json.
+        """
+        return json.dumps(self.to_map_str(), ensure_ascii=False, indent=4)
+
+    def to_map_str(self) -> dict[str, Any]:
+        final = dict()
+        for i in self.header():
+            final[str(i)] = str(self.get_value(i))
+        return final
+
+    
+class HashMapDataFrame[K, Series](HashMap):
+    
+    def __init__(self, data: DataFrame | None) -> None:
+        super().__init__()
+        if data is None:
+            data = DataFrame()
+        self._data: DataFrame = data
+    
+    def size_values(self) -> int:
+        return len(self.values())
+
+    def size_header(self) -> int:
+        return len(self.header())
+
+    def __getitem__(self, key: K) -> Series:
+        return self._data[key]
+
+    def __setitem__(self, key: K, value: Series) -> None:
+        self._data[key] = value
+
+    def get_hash_map_name(self) -> Literal['DATAFRAME']:
+        return "DATAFRAME"
+
+    def get_real_hash_map(self) -> DataFrame:
+        return self._data
+
+    def set_real_hash_map(self, hash_map: DataFrame) -> None:
+        self._data = hash_map
+
+    def clear(self) -> None:
+        self._data = DataFrame()
+
+    def get_first(self) -> Series:
+        return self._data[self.header().get_first()]
+
+    def set_first(self, value: Series) -> None:
+        self._data[self.header().get_first()] = value
+
+    def get_last(self) -> Series:
+        return self._data[self.header().get_last()]
+
+    def set_last(self, value: T) -> None:
+        raise NotImplementedError
+
+    def set_value(self, key: K, value: Series) -> None:
+        self._data[key] = value
+
+    def get_value(self, key: K) -> Series:
+        return self._data[key]
+
+    def header(self) -> ArrayList[K]:
+        return ArrayList(self._data.columns.tolist())
+
+    def values(self) -> ArrayList[Any]:
+        return ArrayList(self._data.values.tolist())
+
+    def delete_items(self, keys: list[K]) -> None:
+        """
+        Remove as colunas informadas.
+        """
+        # axis=1 indica que queremos remover colunas (as chaves do seu mapa)
+        # errors='ignore' evita que o código quebre caso uma chave não exista
+        #self._data.drop(columns=keys, axis=1, inplace=True, errors='ignore'
+        self._data.drop(columns=keys, inplace=True, errors="ignore",)
+
+    def to_json(self) -> str:
+        """
+        Serializa o DataFrame para JSON.
+        Mantém estrutura por colunas.
+        """
+        return self._data.astype(str).to_json(orient="columns", force_ascii=False, indent=4)
+
+    def to_map_str(self) -> dict[str, Any]:
+        return self._data.astype('str').to_dict()
+
+    
+     
+   
+
+    

table_stream-0.1.0/table_stream/base/mapping.py

@@ -0,0 +1,153 @@
+
+from __future__ import annotations
+from abc import abstractmethod, ABC, ABCMeta
+from collections.abc import Iterator
+from typing import Any, Callable, TypeVar, Generic, Union, Literal
+#import pandas as pd
+#from pandas import Series
+
+
+T = TypeVar('T')
+K = TypeVar('K')
+hashMapName = Literal['DATAFRAME', 'DICT']
+
+
+class ArrayList[T](list):
+    
+    def __init__(self, items: list[T] | None = None):
+        if items is None:
+            items = list()
+        super().__init__(items)
+        
+    def set_items(self, items: list[T]):
+        self.clear()
+        super().__init__(items)
+        
+    def for_each(self, func: Callable[[T], Any | None]) -> None:
+        for x in self: func(x)
+    
+    def apply_command(self, func: Callable[[T], Any]) -> ArrayList[Any]:
+        return ArrayList([func(x) for x in self])
+    
+    def size(self) -> int:
+        return len(self)
+        
+    def empty(self) -> bool:
+        return self.size() == 0
+        
+    def get_first(self) -> T:
+        return self[0]
+
+    def get_last(self) -> T:
+        return self[-1]
+    
+    def hash(self) -> int:
+        return hash(tuple(self))
+    
+    def contains(self, _o: T) -> bool:
+        for i in self:
+            if i == _o:
+                return True
+        return False
+    
+
+class HashMap[K, T](metaclass=ABCMeta):
+    
+    def __repr__(self) -> str:
+        return f"<HashMap()> {self.header()}"
+    
+    @abstractmethod
+    def size_values(self) -> int:
+        pass
+    
+    @abstractmethod
+    def size_header(self) -> int:
+        pass
+    
+    @abstractmethod
+    def __getitem__(self, key: K) -> T:
+        pass
+    
+    @abstractmethod
+    def __setitem__(self, key: K, value: T) -> None:
+        pass
+    
+    @abstractmethod
+    def get_hash_map_name(self) -> hashMapName:
+        pass
+    
+    @abstractmethod
+    def get_real_hash_map(self) -> Union[dict[K, T], pd.DataFrame]:
+        pass
+    
+    @abstractmethod
+    def set_real_hash_map(self, hash_map: dict[K, T] | pd.DataFrame) -> None:
+        pass
+
+    @abstractmethod
+    def clear(self) -> None:
+        pass
+
+    @abstractmethod
+    def get_first(self) -> T:
+        pass
+
+    @abstractmethod
+    def set_first(self, value: T) -> None:
+        pass
+
+    @abstractmethod
+    def get_last(self) -> T:
+        pass
+
+    @abstractmethod
+    def set_last(self, value: T) -> None:
+        pass
+
+    @abstractmethod
+    def set_value(self, key: K, value: T) -> None:
+        pass
+
+    @abstractmethod
+    def get_value(self, key: K) -> T:
+        pass
+
+    @abstractmethod
+    def header(self) -> ArrayList[K]:
+        """
+            Retornar as chaves de um dicionário ou columns de um DataFrame()
+        """
+        pass
+
+    @abstractmethod
+    def values(self) -> ArrayList[T]:
+        pass
+
+    @abstractmethod
+    def delete_items(self, keys: list[K]) -> None:
+        """
+            Apaga chaves e valores, semelhante ao método pop().
+        """
+        pass
+
+    @abstractmethod
+    def to_json(self) -> str:
+        """
+            Converte o HashMap() para uma representação no formato json.
+        """
+        pass
+
+    @abstractmethod
+    def to_map_str(self) -> dict[str, Any]:
+        """
+            Converte o HashMap() para uma representação no formato dict() python.
+        """
+        pass
+
+    @classmethod
+    def from_json(cls, data: str) -> HashMap:
+        pass
+
+    @classmethod
+    def from_map(cls, data: Any) -> HashMap:
+        pass

table_stream-0.1.0/table_stream/erros/__init__.py

@@ -0,0 +1,90 @@
+class CoreException(Exception):
+
+    def __init__(self, message: str = f'Erro') -> None:
+        super().__init__(message)
+        self._message = message
+
+    def get_message(self) -> str:
+        return self._message
+
+    def set_message(self, message: str) -> None:
+        self._message = message
+        super().__init__(f"{__class__.__name__}: {message}")
+
+    def launch_exception_handler(self) -> None:
+        raise self
+
+
+#============================================================#
+# Erros relacionados a HashMap
+#============================================================#
+class InvalidHashMapTableError(CoreException):
+
+    def __init__(self, message: str = 'HashMap inválido') -> None:
+        super().__init__(message)
+
+
+class InvalidBodyTableError(InvalidHashMapTableError):
+
+    def __init__(self, message: str = 'Erro corpo de tabela inválido') -> None:
+        super().__init__(message)
+
+
+class SizeTableError(InvalidHashMapTableError):
+
+    def __init__(self, message: str = 'Tamanho de tabela inválido') -> None:
+        super().__init__(message)
+
+
+#============================================================#
+# Erros relacionados a planilhas
+#============================================================#
+class UndefinedSheetIndex(CoreException):
+
+    def __init__(self, message: str = 'SheetIndexNames não foi definido') -> None:
+        super().__init__(message)
+
+
+class LoadWorkbookError(CoreException):
+
+    def __init__(self, message: str = 'Erro ao tentar ler Workbook') -> None:
+        super().__init__(message)
+
+#============================================================#
+# Erros relacionados a arquivos/bytes de imagem (.png, .jpg, ...)
+#============================================================#
+class InvalidSourceImageError(CoreException):
+
+    def __init__(self, message: str = 'Erro, use bytes de imagem') -> None:
+        super().__init__(message)
+
+
+#============================================================#
+# Erros relacionados a módulos
+#============================================================#
+class NotImplementedModuleError(CoreException):
+
+    def __init__(self, message: str = 'Erro, módulo não implementado') -> None:
+        super().__init__(message)
+
+
+class NotImplementedModuleImageError(NotImplementedModuleError):
+
+    def __init__(self, message: str = 'Erro, módulo IMAGEM não implementado') -> None:
+        super().__init__(message)
+
+
+class NotImplementedModulePdfError(NotImplementedModuleError):
+
+    def __init__(self, message: str = 'Erro, módulo PDF não implementado') -> None:
+        super().__init__(message)
+
+
+class NotImplementedInvertColor(NotImplementedError):
+
+    def __init__(self, message: str = 'Adaptador InvertColor não implementado...') -> None:
+        super().__init__(message)
+
+
+
+

table_stream-0.1.0/table_stream/sheet/__init__.py

@@ -0,0 +1,10 @@
+from .excel import ExcelLoadPandasInterface
+from .ods import ODSLoadPandasInterface
+from .csv import (
+    CsvLoadPandasInterface, csvEncoding, CsvMapping, csvSeparator, create_csv_mapping,
+    CsvSeparatorList, CsvEncodingList,
+)
+from .parse import FilterData, ParserData
+from .interface import InterfaceSheetLoad
+from .load_adapter import SheetLoader
+