sycommon-python-lib 0.1.0__tar.gz

sycommon_python_lib-0.1.0/PKG-INFO

@@ -0,0 +1,128 @@
+Metadata-Version: 2.4
+Name: sycommon-python-lib
+Version: 0.1.0
+Summary: Add your description here
+Requires-Python: >=3.10
+Description-Content-Type: text/markdown
+Requires-Dist: aiohttp>=3.12.13
+Requires-Dist: cx-oracle>=8.3.0
+Requires-Dist: decorator>=5.2.1
+Requires-Dist: fastapi>=0.115.14
+Requires-Dist: kafka>=1.3.5
+Requires-Dist: kafka-python>=2.2.14
+Requires-Dist: loguru>=0.7.3
+Requires-Dist: mysql-connector-python>=9.3.0
+Requires-Dist: nacos-sdk-python>=2.0.6
+Requires-Dist: pydantic>=2.11.7
+Requires-Dist: python-dotenv>=1.1.1
+Requires-Dist: pyyaml>=6.0.2
+Requires-Dist: sqlalchemy>=2.0.41
+Requires-Dist: uuid>=1.30
+
+# sycommon-python-lib
+
+常用 python 依赖库
+
+pip install sycommon-python-lib -i http://192.168.2.174:8081/repository/pypy-group/simple/ --trusted-host 192.168.2.174
+
+## 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/ee/user/project/repository/web_editor.html#create-a-file) or [upload](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#upload-a-file) files
+- [ ] [Add files using the command line](https://docs.gitlab.com/ee/gitlab-basics/add-file.html#add-a-file-using-the-command-line) or push an existing Git repository with the following command:
+
+```
+cd existing_repo
+git remote add origin http://git.syf.com/syai/sycommon-python-lib.git
+git branch -M main
+git push -uf origin main
+```
+
+## Integrate with your tools
+
+- [ ] [Set up project integrations](http://git.syf.com/syai/sycommon-python-lib/-/settings/integrations)
+
+## Collaborate with your team
+
+- [ ] [Invite team members and collaborators](https://docs.gitlab.com/ee/user/project/members/)
+- [ ] [Create a new merge request](https://docs.gitlab.com/ee/user/project/merge_requests/creating_merge_requests.html)
+- [ ] [Automatically close issues from merge requests](https://docs.gitlab.com/ee/user/project/issues/managing_issues.html#closing-issues-automatically)
+- [ ] [Enable merge request approvals](https://docs.gitlab.com/ee/user/project/merge_requests/approvals/)
+- [ ] [Automatically merge when pipeline succeeds](https://docs.gitlab.com/ee/user/project/merge_requests/merge_when_pipeline_succeeds.html)
+
+## Test and Deploy
+
+Use the built-in continuous integration in GitLab.
+
+- [ ] [Get started with GitLab CI/CD](https://docs.gitlab.com/ee/ci/quick_start/index.html)
+- [ ] [Analyze your code for known vulnerabilities with Static Application Security Testing(SAST)](https://docs.gitlab.com/ee/user/application_security/sast/)
+- [ ] [Deploy to Kubernetes, Amazon EC2, or Amazon ECS using Auto Deploy](https://docs.gitlab.com/ee/topics/autodevops/requirements.html)
+- [ ] [Use pull-based deployments for improved Kubernetes management](https://docs.gitlab.com/ee/user/clusters/agent/)
+- [ ] [Set up protected environments](https://docs.gitlab.com/ee/ci/environments/protected_environments.html)
+
+---
+
+# 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!). Thank you 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.

sycommon_python_lib-0.1.0/README.md

@@ -0,0 +1,107 @@
+# sycommon-python-lib
+
+常用 python 依赖库
+
+pip install sycommon-python-lib -i http://192.168.2.174:8081/repository/pypy-group/simple/ --trusted-host 192.168.2.174
+
+## 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/ee/user/project/repository/web_editor.html#create-a-file) or [upload](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#upload-a-file) files
+- [ ] [Add files using the command line](https://docs.gitlab.com/ee/gitlab-basics/add-file.html#add-a-file-using-the-command-line) or push an existing Git repository with the following command:
+
+```
+cd existing_repo
+git remote add origin http://git.syf.com/syai/sycommon-python-lib.git
+git branch -M main
+git push -uf origin main
+```
+
+## Integrate with your tools
+
+- [ ] [Set up project integrations](http://git.syf.com/syai/sycommon-python-lib/-/settings/integrations)
+
+## Collaborate with your team
+
+- [ ] [Invite team members and collaborators](https://docs.gitlab.com/ee/user/project/members/)
+- [ ] [Create a new merge request](https://docs.gitlab.com/ee/user/project/merge_requests/creating_merge_requests.html)
+- [ ] [Automatically close issues from merge requests](https://docs.gitlab.com/ee/user/project/issues/managing_issues.html#closing-issues-automatically)
+- [ ] [Enable merge request approvals](https://docs.gitlab.com/ee/user/project/merge_requests/approvals/)
+- [ ] [Automatically merge when pipeline succeeds](https://docs.gitlab.com/ee/user/project/merge_requests/merge_when_pipeline_succeeds.html)
+
+## Test and Deploy
+
+Use the built-in continuous integration in GitLab.
+
+- [ ] [Get started with GitLab CI/CD](https://docs.gitlab.com/ee/ci/quick_start/index.html)
+- [ ] [Analyze your code for known vulnerabilities with Static Application Security Testing(SAST)](https://docs.gitlab.com/ee/user/application_security/sast/)
+- [ ] [Deploy to Kubernetes, Amazon EC2, or Amazon ECS using Auto Deploy](https://docs.gitlab.com/ee/topics/autodevops/requirements.html)
+- [ ] [Use pull-based deployments for improved Kubernetes management](https://docs.gitlab.com/ee/user/clusters/agent/)
+- [ ] [Set up protected environments](https://docs.gitlab.com/ee/ci/environments/protected_environments.html)
+
+---
+
+# 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!). Thank you 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.

sycommon_python_lib-0.1.0/pyproject.toml

@@ -0,0 +1,31 @@
+[project]
+name = "sycommon-python-lib"
+version = "0.1.0"
+description = "Add your description here"
+readme = "README.md"
+requires-python = ">=3.10"
+dependencies = [
+    "aiohttp>=3.12.13",
+    "cx-oracle>=8.3.0",
+    "decorator>=5.2.1",
+    "fastapi>=0.115.14",
+    "kafka>=1.3.5",
+    "kafka-python>=2.2.14",
+    "loguru>=0.7.3",
+    "mysql-connector-python>=9.3.0",
+    "nacos-sdk-python>=2.0.6",
+    "pydantic>=2.11.7",
+    "python-dotenv>=1.1.1",
+    "pyyaml>=6.0.2",
+    "sqlalchemy>=2.0.41",
+    "uuid>=1.30",
+]
+
+[tool.setuptools]
+packages = {find = {where = ["src"]}}
+
+[tool.index]
+name = "testpypi"
+url = "http://192.168.2.174:8081/repository/shengye/"
+publish-url = "http://192.168.2.174:8081/repository/shengye/"
+explicit = true

sycommon_python_lib-0.1.0/setup.cfg

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

sycommon_python_lib-0.1.0/src/sycommon/config/Config.py

@@ -0,0 +1,73 @@
+import yaml
+
+
+class SingletonMeta(type):
+    _instances = {}
+
+    def __call__(cls, *args, **kwargs):
+        if cls not in cls._instances:
+            cls._instances[cls] = super().__call__(*args, **kwargs)
+        return cls._instances[cls]
+
+
+class Config(metaclass=SingletonMeta):
+    def __init__(self, config_file='app.yaml'):
+        with open(config_file, 'r') as f:
+            self.config = yaml.safe_load(f)
+        self.MaxBytes = self.config.get('MaxBytes', 209715200)
+        self.Timeout = self.config.get('Timeout', 300000)
+        self.OCR = self.config.get('OCR', None)
+        self.INVOICE_OCR = self.config.get('INVOICE_OCR', None)
+        self.UnstructuredAPI = self.config.get('UnstructuredAPI', None)
+        self.MaxRetries = self.config.get('MaxRetries', 3)
+        self.llm_configs = []
+        self.embedding_configs = []
+        self.reranker_configs = []
+        self._process_config()
+
+    def get_llm_config(self, model_name):
+        for llm in self.llm_configs:
+            if llm.get('model') == model_name:
+                return llm
+        raise ValueError(f"No configuration found for model: {model_name}")
+
+    def get_embedding_config(self, model_name):
+        for llm in self.embedding_configs:
+            if llm.get('model') == model_name:
+                return llm
+        raise ValueError(f"No configuration found for model: {model_name}")
+
+    def get_reranker_config(self, model_name):
+        for llm in self.reranker_configs:
+            if llm.get('model') == model_name:
+                return llm
+        raise ValueError(f"No configuration found for model: {model_name}")
+
+    def _process_config(self):
+        llm_config_list = self.config.get('LLMConfig', [])
+        for llm_config in llm_config_list:
+            try:
+                # 延迟导入 LLMConfigModel
+                from sycommon.config.LLMConfig import LLMConfig
+                validated_config = LLMConfig(**llm_config)
+                self.llm_configs.append(validated_config.model_dump())
+            except ValueError as e:
+                print(f"Invalid LLM configuration: {e}")
+
+        embedding_config_list = self.config.get('EmbeddingConfig', [])
+        for embedding_config in embedding_config_list:
+            try:
+                from sycommon.config.EmbeddingConfig import EmbeddingConfig
+                validated_config = EmbeddingConfig(**embedding_config)
+                self.embedding_configs.append(validated_config.model_dump())
+            except ValueError as e:
+                print(f"Invalid LLM configuration: {e}")
+
+        reranker_config_list = self.config.get('RerankerConfig', [])
+        for reranker_config in reranker_config_list:
+            try:
+                from sycommon.config.RerankerConfig import RerankerConfig
+                validated_config = RerankerConfig(**reranker_config)
+                self.reranker_configs.append(validated_config.model_dump())
+            except ValueError as e:
+                print(f"Invalid LLM configuration: {e}")

sycommon_python_lib-0.1.0/src/sycommon/config/DatabaseConfig.py

@@ -0,0 +1,34 @@
+from pydantic import BaseModel
+
+
+class HikariConfig(BaseModel):
+    minimum_idle: int
+    maximum_pool_size: int
+    idle_timeout: int
+
+
+class DatabaseConfig(BaseModel):
+    url: str
+    username: str
+    password: str
+    driver_class_name: str
+    time_between_eviction_runs_millis: int
+    min_evictable_idle_time_millis: int
+    validation_query: str
+    test_while_idle: bool
+    test_on_borrow: bool
+    test_on_return: bool
+    hikari: HikariConfig
+
+
+def convert_key_to_snake_case(key):
+    import re
+    # 处理驼峰命名转换为下划线命名
+    key = re.sub(r'(?<!^)(?=[A-Z])', '_', key).lower()
+    return key.replace('-', '_')
+
+
+def convert_dict_keys(d):
+    if isinstance(d, dict):
+        return {convert_key_to_snake_case(k): convert_dict_keys(v) for k, v in d.items()}
+    return d

sycommon_python_lib-0.1.0/src/sycommon/config/EmbeddingConfig.py

@@ -0,0 +1,16 @@
+
+from pydantic import BaseModel
+
+
+class EmbeddingConfig(BaseModel):
+    model: str
+    provider: str
+    baseUrl: str
+    maxTokens: int
+    dimension: int
+
+    @classmethod
+    def from_config(cls, model_name: str):
+        from sycommon.config.Config import Config
+        llm_config = Config().get_embedding_config(model_name)
+        return cls(**llm_config)

sycommon_python_lib-0.1.0/src/sycommon/config/LLMConfig.py

@@ -0,0 +1,16 @@
+from pydantic import BaseModel
+
+
+class LLMConfig(BaseModel):
+    model: str
+    provider: str
+    baseUrl: str
+    maxTokens: int
+    vision: bool
+    callFunction: bool
+
+    @classmethod
+    def from_config(cls, model_name: str):
+        from sycommon.config.Config import Config
+        llm_config = Config().get_llm_config(model_name)
+        return cls(**llm_config)

sycommon_python_lib-0.1.0/src/sycommon/config/RerankerConfig.py

@@ -0,0 +1,13 @@
+from pydantic import BaseModel
+
+
+class RerankerConfig(BaseModel):
+    model: str
+    provider: str
+    baseUrl: str
+
+    @classmethod
+    def from_config(cls, model_name: str):
+        from sycommon.config.Config import Config
+        llm_config = Config().get_reranker_config(model_name)
+        return cls(**llm_config)

sycommon_python_lib-0.1.0/src/sycommon/database/database_service.py

@@ -0,0 +1,79 @@
+from sqlalchemy import create_engine, text
+
+from sycommon.config.Config import SingletonMeta
+from sycommon.config.DatabaseConfig import DatabaseConfig, convert_dict_keys
+from sycommon.logging.kafka_log import SYLogger
+from sycommon.synacos.nacos_service import NacosService
+
+
+class DatabaseService(metaclass=SingletonMeta):
+    _engine = None
+
+    @staticmethod
+    def setup_database(config: dict, shareConfigKey: str):
+        common = NacosService(config).share_configs.get(shareConfigKey, {})
+        if common and common.get('spring', {}).get('datasource', None):
+            databaseConfig = common.get('spring', {}).get('datasource', None)
+            converted_dict = convert_dict_keys(databaseConfig)
+            db_config = DatabaseConfig.model_validate(converted_dict)
+            DatabaseService._engine = DatabaseConnector(db_config).engine
+
+    @staticmethod
+    def engine():
+        return DatabaseService._engine
+
+
+class DatabaseConnector(metaclass=SingletonMeta):
+    def __init__(self, db_config: DatabaseConfig):
+        # 从 DatabaseConfig 中提取数据库连接信息
+        self.db_user = db_config.username
+        self.db_password = db_config.password
+        # 提取 URL 中的主机、端口和数据库名
+        url_parts = db_config.url.split('//')[1].split('/')
+        host_port = url_parts[0].split(':')
+        self.db_host = host_port[0]
+        self.db_port = host_port[1]
+        self.db_name = url_parts[1].split('?')[0]
+
+        # 提取 URL 中的参数
+        params_str = url_parts[1].split('?')[1] if len(
+            url_parts[1].split('?')) > 1 else ''
+        params = {}
+        for param in params_str.split('&'):
+            if param:
+                key, value = param.split('=')
+                params[key] = value
+
+        # 在params中去掉指定的参数
+        for key in ['useUnicode', 'characterEncoding', 'serverTimezone', 'zeroDateTimeBehavior']:
+            if key in params:
+                del params[key]
+
+        # 构建数据库连接 URL
+        self.db_url = f'mysql+mysqlconnector://{self.db_user}:{self.db_password}@{self.db_host}:{self.db_port}/{self.db_name}'
+
+        SYLogger.info(f"Database URL: {self.db_url}")
+
+        # 优化连接池配置
+        self.engine = create_engine(
+            self.db_url,
+            connect_args=params,
+            pool_size=10,  # 连接池大小
+            max_overflow=20,  # 最大溢出连接数
+            pool_timeout=30,  # 连接超时时间（秒）
+            pool_recycle=3600,  # 连接回收时间（秒）
+            pool_pre_ping=True  # 每次获取连接前检查连接是否有效
+        )
+
+        # 测试
+        if not self.test_connection():
+            raise Exception("Database connection test failed")
+
+    def test_connection(self):
+        try:
+            with self.engine.connect() as connection:
+                connection.execute(text("SELECT 1"))
+                return True
+        except Exception as e:
+            SYLogger.error(f"Database connection test failed: {e}")
+            return False

sycommon_python_lib-0.1.0/src/sycommon/health/health_check.py

@@ -0,0 +1,17 @@
+from fastapi import FastAPI, APIRouter
+
+
+def setup_health_handler(app: FastAPI):
+    health_router = APIRouter()
+
+    @health_router.get("/actuator/health")
+    async def health_check():
+        """返回应用的健康状态"""
+        return {
+            "status": "UP",
+            "groups": ["liveness", "readiness"]
+        }
+
+    app.include_router(health_router)
+
+    return app

sycommon_python_lib-0.1.0/src/sycommon/health/ping.py

@@ -0,0 +1,13 @@
+from fastapi import FastAPI, APIRouter
+
+
+def setup_ping_handler(app: FastAPI):
+    ping_router = APIRouter()
+
+    @ping_router.get("/ping")
+    async def ping():
+        return {"status": "alive"}
+
+    app.include_router(ping_router)
+
+    return app