trpc-fastapi-python 1.0.0__tar.gz

trpc_fastapi_python-1.0.0/.flake8

@@ -0,0 +1,3 @@
+[flake8]
+max-line-length = 120
+ignore = E402

trpc_fastapi_python-1.0.0/.gitignore

@@ -0,0 +1,32 @@
+.idea
+.vscode
+.DS_Store
+*.lock
+*.log
+examples/*.log
+
+trpc_fastapi.egg-info
+
+build
+dist
+.venv
+venv
+venv*
+__pycache__
+
+.coverage
+htmlcov
+cov.tmp
+coverage.xml
+test-ngtest-ut-trpc_mcp.xml
+.pytest_cache
+
+node_modules
+package-lock.json
+pyrightconfig.json
+
+# local notes and captured responses
+baseline/
+docs/run.md
+docs/source_code_guide.md
+docs/trpc_fastapi_源码理解.md

trpc_fastapi_python-1.0.0/.style.yapf

@@ -0,0 +1,6 @@
+[style]
+based_on_style = pep8
+column_limit = 120 
+indent_width = 4 
+split_before_logical_operator = true
+

trpc_fastapi_python-1.0.0/.yapfignore

@@ -0,0 +1,25 @@
+# 构建和分发目录
+build/
+dist/
+*.egg-info/
+
+# 虚拟环境
+venv/
+env/
+.venv/
+.env/
+
+# Python 缓存
+__pycache__/
+*.pyc
+*.pyo
+
+# 文档
+docs/
+
+# 临时文件
+*.tmp
+*.temp
+
+# examples
+examples/

trpc_fastapi_python-1.0.0/CHANGELOG.md

@@ -0,0 +1,6 @@
+# Change Log
+
+## 1.0.0
+
+- 导入 `trpc_fastapi` 即注册 `http_fastapi` 协议，需在 `create_server` 之前导入。
+- 把 tRPC 服务暴露为 FastAPI HTTP 路由，并支持中间件和 WebSocket。

trpc_fastapi_python-1.0.0/CODE-OF-CONDUCT.md

@@ -0,0 +1,55 @@
+English | [中文](CODE-OF-CONDUCT.zh_CN.md)
+
+# Community Code of Conduct
+
+Welcome to our open source project!
+
+We are committed to creating a friendly, respectful, and inclusive community. 
+
+To ensure a positive experience in our project, we have established the following code of conduct, which we require all participants to abide by, and provide a safe and inclusive environment for all community members.
+
+## Our Pledge
+
+As participants, contributors, and maintainers of our community, we pledge to:
+- Treat everyone with openness, inclusivity, and collaboration;
+- Respect individuals with different backgrounds and viewpoints, regardless of gender, sexual orientation, disability, race, ethnicity, religion, age, or any other factor;
+- Focus on contributing and improving the project, rather than attacking or criticizing individuals;
+- Build trust with community members and promote our project through constructive feedback;
+- Provide a safe, supportive, and encouraging environment for community members to promote learning and personal growth.
+
+## Our standards
+
+Our community members should adhere to the following standards:
+- Respect the opinions, viewpoints, and experiences of others;
+- Avoid using insulting, discriminatory, or harmful language;
+- Do not harass, intimidate, or threaten others;
+- Do not publicly or privately disclose others' private information, such as contact information or addresses;
+- Respect the privacy of others;
+- Establish a safe, inclusive, and respectful environment for community members.
+
+## Our responsibility
+
+Project maintainers have a responsibility to create a friendly, respectful, and inclusive environment for our community members. 
+
+They should:
+- Clearly and publicly explain the community guidelines;
+- Handle reports of guideline violations and resolve disputes appropriately;
+- Protect the privacy and security of all community members;
+- Maintain a fair, transparent, and responsible attitude.
+
+## Scope
+
+This code of conduct applies to all project spaces, including GitHub, mailing lists, forums, social media, gatherings, and conferences. 
+
+Violations of the code of conduct will be dealt with, including but not limited to warnings, temporary or permanent bans, revocation of contribution rights, and revocation of project access rights.
+
+## Implementation guidelines
+
+If you encounter behavior that violates this code of conduct, you can:
+- Communicate privately with the relevant person to try to resolve the issue;
+- Report the violation to the project maintainers(maintainer mailing list), who will take necessary action based on the situation;
+- If you are not satisfied with the way the maintainers handle the situation, you can seek help from higher-level organizations or institutions.
+
+Our community is a diverse, open, and inclusive community, and we welcome everyone's participation and contribution. 
+
+We believe that only in a safe, respectful, and inclusive environment can we create the best project together.

trpc_fastapi_python-1.0.0/CODE-OF-CONDUCT.zh_CN.md

@@ -0,0 +1,53 @@
+[English](CODE-OF-CONDUCT.md) | 中文
+
+# 社区行为准则
+
+欢迎来到我们的开源项目！我们致力于创建一个友好、尊重和包容的社区，我们希望所有人都能为此做出贡献。
+
+为了确保在我们的项目中有一个积极的体验，我们制定了以下行为准则，我们要求所有参与者遵守这些准则，并向所有社区成员提供一个安全和包容的环境。
+
+## 我们的承诺
+
+作为我们社区的参与者、贡献者和维护者，我们承诺：
+- 以开放、包容和合作的态度对待所有人；
+- 尊重不同背景和观点的人，不论是性别、性取向、残疾、种族、民族、宗教、年龄或任何其他因素；
+- 专注于对项目的贡献和改进，而不是对个人的攻击或抨击；
+- 与社区成员建立互信关系，通过积极的反馈来推动我们的项目发展；
+- 为社区成员提供一个安全、支持和鼓励的环境，以促进学习和个人成长。
+
+## 我们的标准
+
+我们的社区成员应该遵守以下标准：
+- 尊重他人的意见、观点和经验；
+- 避免使用侮辱性、歧视性或有损的语言；
+- 不要骚扰、恐吓或威胁他人；
+- 不要公开或私下发布他人的私人信息，例如联系方式或地址；
+- 尊重他人的隐私权；
+- 为社区成员建立安全、包容和尊重的环境。
+
+## 我们的责任
+
+项目维护者有责任为我们的社区成员创造一个友好、尊重和包容的环境。
+
+他们应该：
+- 明确和公开地说明社区准则；
+- 处理准则违规行为的举报，通过适当的方式解决纠纷；
+- 保护所有社区成员的隐私和安全；
+- 保持公正、透明和负责任的态度。
+
+## 管理范围
+
+本行为准则适用于所有的项目空间，包括 GitHub、邮件列表、论坛、社交媒体、聚会和会议等。
+
+违反准则的行为将受到处理，包括但不限于警告、暂时或永久禁言、撤销贡献权、撤销项目访问权等。
+
+## 实施指南
+
+如果你遇到了违反本准则的行为，你可以：
+- 私下与相关人员沟通，以尝试解决问题；
+- 向项目维护者报告违规行为，维护者会根据情况采取必要的行动；
+- 如果你不满意维护者的处理方式，你可以向更高级别的机构或组织寻求帮助。
+
+我们的社区是一个多样化、开放和包容的社区，我们欢迎所有人的参与和贡献。
+
+我们相信，只有在一个安全、尊重和包容的环境中，我们才能共同创造出最优秀的项目。

trpc_fastapi_python-1.0.0/CONTRIBUTING.md

@@ -0,0 +1,65 @@
+English | [中文](CONTRIBUTING.zh_CN.md)
+
+# How to Contribute
+
+Thank you for your interest and support in tRPC!
+
+We welcome and appreciate any form of contribution, including but not limited to submitting issues, providing improvement suggestions, improving documentation, fixing bugs, and adding features. 
+
+This document aims to provide you with a detailed contribution guide to help you better participate in the project.
+
+Please read this guide carefully before contributing and make sure to follow the rules here.
+
+We look forward to working with you to make this project better together!
+
+## Before submitting an issue
+
+Please make sure that you have reviewed the project's documentation, FAQ, and existing issues.
+
+This can avoid submitting known issues repeatedly and save your and the project maintainer's time. 
+
+When you decide to submit an issue, please follow these rules:
+- Select appropriate labels for the issue. This helps us to quickly locate the problem and solve it as soon as possible.
+- Ensure that the issue title is concise and accurately summarizes the problem. Avoid using vague words such as "problem" or "error".
+
+In the issue description, please provide a detailed description of the problem you encountered.
+
+This includes but is not limited to the following:
+- Problem description: briefly describe the symptoms and impact of the problem.
+- Reproduction steps: describe in detail how to reproduce the problem, so that we can locate and solve the problem more quickly.
+- Environment information: relevant information including operating system, browser, project version, etc.
+- Error log: if there are relevant error logs, please provide them.
+- Expected results: describe what the correct result should be.
+- Screenshots or screen recordings: if possible, provide screenshots or screen recordings of the problem.
+
+Please be polite and friendly. 
+
+We attach great importance to the environment of the project and hope that everyone can grow together in a friendly and inclusive environment.
+
+## Rules for submitting PRs
+
+We welcome you to submit code for the project. 
+
+Before submitting a PR, please make sure that you have read this contribution guide. 
+
+Here are some suggestions and rules regarding submitting PRs.
+
+Please read them carefully before submitting:
+- Ensure that your code conforms to the project's code specifications. This includes but is not limited to code style, comment specifications, etc. This helps us to maintain the cleanliness and consistency of the project.
+- Before submitting a PR, please make sure that you have tested your code locally. Ensure that the code has no obvious errors and can run normally.
+- Please select appropriate labels for your PR. This helps us to process your PR more quickly.
+- Ensure that your PR title is concise and accurately summarizes your changes. Avoid using vague words such as "update" or "modify".
+- In the PR description, please provide a detailed description of your changes. This includes but is not limited to the following:
+  - Reason for modification: briefly explain why this modification is necessary.
+  - Modification content: describe in detail what you have modified and how you have implemented it.
+  - Scope of impact: describe the functions or modules that may be affected by the modification.
+  - Testing: describe the testing you have done locally and the results.
+- If your PR resolves a certain issue, please associate the corresponding issue in the PR description. For example: Fixes #123.
+
+## Communication and Consultation
+
+We welcome you to participate in the project's communication and consultation.
+
+You can interact with us through the following channels:
+- Submit your questions or suggestions in the project's discussions.
+- Join our technical communication group.

trpc_fastapi_python-1.0.0/CONTRIBUTING.zh_CN.md

@@ -0,0 +1,62 @@
+[English](CONTRIBUTING.md) | 中文
+
+# 如何作出贡献
+
+首先，感谢您对本开源项目的关注和支持！
+
+我们非常欢迎和感谢任何形式的贡献，包括但不限于提交问题、提出改进意见、完善文档、修复缺陷以及新增功能。
+
+本文档旨在为您提供一份详尽的贡献指南，以便您更好地参与到项目中。
+
+请在参与贡献之前仔细阅读本指南，并确保遵循其中的规则和建议。
+
+我们期待与您一起打造一个更加完善的开源项目！
+
+## 提交 issue 的规则
+
+在提交 issue 之前，请先确保您已经查看了项目的文档、常见问题解答以及已有的 issue。
+
+这样可以避免重复提交已知问题，节省您和项目维护者的时间。
+
+当您确定需要提交一个 issue 时，请遵循以下规则：
+- 为 issue 选择合适的标签。这有助于我们更快地找到问题所在，以便尽快解决。
+- 请确保您的 issue 标题简洁明了，能够准确概括问题所在。避免使用模糊的词语，如“问题”、“错误”等。
+
+在 issue 描述中，请详细说明您遇到的问题。
+
+包括但不限于以下内容：
+- 问题描述：简要说明问题的现象和影响。
+- 复现步骤：详细描述如何复现问题，让我们能够更快地定位和解决问题。
+- 环境信息：包括操作系统、浏览器、项目版本等相关信息。
+- 错误日志：如果有相关错误日志，请一并提供。
+- 期望结果：描述您期望的正确结果是什么。
+- 截图或录屏：如果可能，请提供问题现象的截图或录屏。
+
+请保持礼貌和友好。我们非常重视项目的氛围，希望每个人都能够在友好、包容的环境中共同成长。
+
+## 提交 PR 的规则
+
+我们非常欢迎您为项目提交代码。
+
+在提交 PR 之前，请确保您已经阅读了项目的文档以及本贡献指南。
+
+以下是关于提交 PR 的一些建议和规则，请在提交前仔细阅读：
+
+- 请确保您的代码符合项目的代码规范。这包括但不限于代码风格、注释规范等。这有助于我们保持项目的整洁和一致性。
+- 在提交 PR 之前，请确保您已经在本地测试过您的代码。确保代码没有明显的错误，并能够正常运行。
+- 请为您的 PR 选择合适的标签。这有助于我们更快地处理您的 PR。
+- 请确保您的 PR 标题简洁明了，能够准确概括您的修改。避免使用模糊的词语，如“更新”、“修改”等。
+- 在 PR 描述中，请详细说明您的修改内容。包括但不限于以下内容：
+  - 修改原因：简要说明为什么要进行这次修改。
+  - 修改内容：详细描述您修改了哪些内容，以及修改的具体实现。
+  - 影响范围：说明修改可能影响到的功能或模块。
+  - 测试情况：描述您在本地测试的情况，以及测试结果。
+- 如果您的 PR 解决了某个 issue，请在 PR 描述中关联对应的 issue。例如：Fixes #123。
+
+## 技术交流与问题咨询
+
+我们非常欢迎您参与到项目的技术交流和问题咨询中来。
+
+您可以通过以下途径与我们互动：
+- 在项目的 discussions 中提交您的问题或建议
+- 加入我们的技术交流群

trpc_fastapi_python-1.0.0/CONTRIBUTORS.md

@@ -0,0 +1,39 @@
+English | [中文](CONTRIBUTORS.zh_CN.md)
+
+# Contributor Guidelines
+
+Thank you for your interest and support for tRPC! 
+
+This document outlines the roles and responsibilities of contributors in the project, as well as the process for becoming a Contributor and losing Maintainer status. We hope that this document will help every contributor understand the growth path and make a greater contribution to the project's development.
+
+## Contributor Roles and Responsibilities
+
+we have two main contributor roles: Contributor and Maintainer. 
+
+Here is a brief introduction to these two roles:
+1. Contributor: A contributor to the project who can contribute code, documentation, testing, and other resources. Contributors provide valuable resources to the project, helping it to continuously improve and develop.
+2. Maintainer: A maintainer of the project who is responsible for the day-to-day maintenance of the project, including reviewing and merging PRs, handling issues, and releasing versions. Maintainers are key members of the project and have a significant impact on the project's development direction and decision-making.
+
+## How to become a  Maintainer
+
+We welcome every contributor to contribute to the project's development and encourage contributors to upgrade to the role of Maintainer. 
+
+The following are the conditions for upgrading from Contributor to Maintainer:
+1. Continuous contribution: Contributors need to contribute to the project continuously for a period of time (e.g., 3 months). This demonstrates the contributor's attention and enthusiasm for the project.
+2. Quality assurance: The code or documentation submitted by contributors needs to maintain a high level of quality, meet the project's specifications, and have a positive impact on the project.
+3. Active participation: Contributors need to actively participate in project discussions and decision-making, providing constructive opinions and suggestions for the project's development.
+4. Team collaboration: Contributors need to have good teamwork skills, communicate friendly with other contributors and maintainers, and work together to solve problems.
+5. Responsibility: Contributors need to have a certain sense of responsibility and be willing to undertake some of the project maintenance work, including reviewing PRs and handling issues. When a contributor meets the above conditions, existing maintainers will evaluate them. 
+
+If they meet the requirements of Maintainer, they will be invited to become a new Maintainer.
+
+## Losing Maintainers status
+
+Maintainer have important responsibilities in the project, and we hope that every Maintainer can maintain their attention and enthusiasm for the project. 
+
+However, we also understand that everyone's time and energy are limited, so when Maintainers cannot continue to fulfill their responsibilities, they will be downgraded to the role of Contributor:
+1. Long-term inactivity: If a Maintainer has not participated in project maintenance work, including reviewing PRs and handling issues, for a period of time (e.g., 3 months), they will be considered inactive.
+2. Quality issues: If a Maintainer's work in the project has serious quality issues that affect the project's development, they will be considered not meeting the requirements of Maintainer.
+3. Team collaboration issues: If a Maintainer has serious communication or teamwork issues with other contributors and maintainers, such as disrespecting others' opinions, frequent conflicts, or refusing to collaborate, which affects the project's normal operation and atmosphere, they will be considered not meeting the requirements of Maintainer.
+4. Violation of rules: If a Maintainer violates the project's rules or code of conduct, including but not limited to leaking sensitive information or abusing privileges, they will be considered not meeting the requirements of Maintainer.
+5. Voluntary application: If a Maintainer cannot continue to fulfill their responsibilities due to personal reasons, they can voluntarily apply to be downgraded to the role of Contributor.

trpc_fastapi_python-1.0.0/CONTRIBUTORS.zh_CN.md

@@ -0,0 +1,37 @@
+[English](CONTRIBUTORS.md) | 中文
+
+# 贡献者管理说明文档
+
+感谢您对本开源项目的关注和支持！本文档将阐述贡献者在项目中的角色、职责以及如何从 Contributor 升级为 Maintainer，以及 Maintainer 降级为 Contributor 的规则。我们希望通过这份文档，让每位贡献者都能清楚地了解自己的成长路径，并为项目的发展做出更大的贡献。
+
+## 贡献者角色及职责
+
+在本开源项目中，我们主要设有两个贡献者角色：Contributor 和 Maintainer。
+
+以下是对这两个角色的简要介绍：
+1. Contributor：项目的贡献者，可以是代码贡献者、文档贡献者、测试贡献者等。Contributor 为项目提供了宝贵的资源，帮助项目不断完善和发展。
+2. Maintainer：项目的维护者，负责项目的日常维护工作，包括审查和合并 PR、处理 Issue、发布版本等。Maintainer 是项目的核心成员，对项目的发展方向和决策具有重要的影响力。
+
+## Contributor 升级为 Maintainer
+
+我们非常欢迎每位 Contributor 为项目的发展做出贡献，并鼓励 Contributor 向 Maintainer 的角色发展。
+
+以下是从 Contributor 升级为 Maintainer 的条件：
+1. 持续贡献：Contributor 需要在一段时间内（例如 3 个月）持续为项目贡献代码、文档或其他资源。这表明 Contributor 对项目的关注度和热情。
+2. 质量保证：Contributor 提交的代码或文档等资源需要保持较高的质量，符合项目的规范要求，并对项目产生积极的影响。
+3. 积极参与：Contributor 需要积极参与到项目的讨论和决策中来，为项目的发展提供建设性的意见和建议。
+4. 团队协作：Contributor 需要具备良好的团队协作精神，能够与其他贡献者和 Maintainer 友好沟通，共同解决问题。
+5. 责任担当：Contributor 需要具备一定的责任心，愿意承担项目维护的部分工作，包括审查 PR、处理 Issue 等。
+
+当 Contributor 满足以上条件时，现有的 Maintainer 将会对其进行评估，如果达到 Maintainer 的要求，将会邀请其成为新的 Maintainer。
+
+## Maintainer 降级为 Contributor
+
+Maintainer 在项目中承担了重要的职责，我们希望每位 Maintainer 都能够保持对项目的关注和热情。
+
+然而，我们也理解每个人的时间和精力是有限的，因此，当 Maintainer 无法继续履行职责时，将会降级为 Contributor：
+1. 长时间不活跃：如果 Maintainer 在一段时间内（例如 3 个月）没有参与项目的维护工作，包括审查 PR、处理 Issue 等，将被视为不活跃。
+2. 质量问题：如果 Maintainer 在项目中的工作出现严重的质量问题，导致项目的发展受到影响，将被视为不符合 Maintainer 的要求。
+3. 团队协作问题：如果 Maintainer 在与其他贡献者和 Maintainer 的协作过程中出现严重的沟通问题或团队协作问题，如不尊重他人意见、频繁产生冲突、拒绝协作等，影响到项目的正常运作和氛围，将被视为不符合 Maintainer 的要求。
+4. 违反规定：如果 Maintainer 违反了项目的规定或行为准则，包括但不限于泄露敏感信息、滥用权限等，将被视为不符合 Maintainer 的要求。
+5. 主动申请：如果 Maintainer 由于个人原因无法继续履行职责，可以主动申请降级为 Contributor。

trpc_fastapi_python-1.0.0/LICENSE

@@ -0,0 +1,210 @@
+Tencent is pleased to support the open source community by making tRPC-FastAPI-Python available. 
+
+Copyright (C) 2026 Tencent.  All rights reserved. 
+
+tRPC-FastAPI-Python is licensed under the Apache-2.0.
+
+
+Terms of the Apache-2.0:
+--------------------------------------------------------------------
+Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.