scCODE 0.1.0__tar.gz
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- sccode-0.1.0/.gitattributes +51 -0
- sccode-0.1.0/.github/workflows/pages.yml +45 -0
- sccode-0.1.0/.github/workflows/publish-pypi.yml +37 -0
- sccode-0.1.0/.gitignore +207 -0
- sccode-0.1.0/CONTRIBUTING.md +149 -0
- sccode-0.1.0/LICENSE +21 -0
- sccode-0.1.0/MANIFEST.in +7 -0
- sccode-0.1.0/PKG-INFO +366 -0
- sccode-0.1.0/README.md +319 -0
- sccode-0.1.0/_config.yml +5 -0
- sccode-0.1.0/examples/README.md +135 -0
- sccode-0.1.0/examples/basic_usage.py +67 -0
- sccode-0.1.0/examples/trajectory_inference.py +97 -0
- sccode-0.1.0/pyproject.toml +70 -0
- sccode-0.1.0/requirements.txt +11 -0
- sccode-0.1.0/setup.cfg +4 -0
- sccode-0.1.0/setup.py +67 -0
- sccode-0.1.0/src/CODE/__init__.py +28 -0
- sccode-0.1.0/src/CODE/agent.py +571 -0
- sccode-0.1.0/src/CODE/environment.py +149 -0
- sccode-0.1.0/src/CODE/mixin.py +317 -0
- sccode-0.1.0/src/CODE/model.py +624 -0
- sccode-0.1.0/src/CODE/module.py +499 -0
- sccode-0.1.0/src/CODE/utils.py +232 -0
- sccode-0.1.0/src/scCODE.egg-info/PKG-INFO +366 -0
- sccode-0.1.0/src/scCODE.egg-info/SOURCES.txt +27 -0
- sccode-0.1.0/src/scCODE.egg-info/dependency_links.txt +1 -0
- sccode-0.1.0/src/scCODE.egg-info/requires.txt +18 -0
- sccode-0.1.0/src/scCODE.egg-info/top_level.txt +1 -0
|
@@ -0,0 +1,51 @@
|
|
|
1
|
+
# Auto detect text files and perform LF normalization
|
|
2
|
+
* text=auto
|
|
3
|
+
|
|
4
|
+
# Python source files
|
|
5
|
+
*.py text eol=lf
|
|
6
|
+
|
|
7
|
+
# Markdown files
|
|
8
|
+
*.md text eol=lf
|
|
9
|
+
|
|
10
|
+
# Configuration files
|
|
11
|
+
*.toml text eol=lf
|
|
12
|
+
*.ini text eol=lf
|
|
13
|
+
*.cfg text eol=lf
|
|
14
|
+
*.json text eol=lf
|
|
15
|
+
*.yml text eol=lf
|
|
16
|
+
*.yaml text eol=lf
|
|
17
|
+
|
|
18
|
+
# Shell scripts
|
|
19
|
+
*.sh text eol=lf
|
|
20
|
+
*.bash text eol=lf
|
|
21
|
+
|
|
22
|
+
# Documentation
|
|
23
|
+
*.rst text eol=lf
|
|
24
|
+
*.txt text eol=lf
|
|
25
|
+
LICENSE text eol=lf
|
|
26
|
+
README text eol=lf
|
|
27
|
+
CONTRIBUTING text eol=lf
|
|
28
|
+
MANIFEST text eol=lf
|
|
29
|
+
|
|
30
|
+
# Binary files
|
|
31
|
+
*.pkl binary
|
|
32
|
+
*.npy binary
|
|
33
|
+
*.npz binary
|
|
34
|
+
*.h5 binary
|
|
35
|
+
*.h5ad binary
|
|
36
|
+
*.zarr binary
|
|
37
|
+
|
|
38
|
+
# Images
|
|
39
|
+
*.png binary
|
|
40
|
+
*.jpg binary
|
|
41
|
+
*.jpeg binary
|
|
42
|
+
*.gif binary
|
|
43
|
+
*.ico binary
|
|
44
|
+
*.svg binary
|
|
45
|
+
|
|
46
|
+
# Archives
|
|
47
|
+
*.zip binary
|
|
48
|
+
*.tar binary
|
|
49
|
+
*.gz binary
|
|
50
|
+
*.bz2 binary
|
|
51
|
+
*.7z binary
|
|
@@ -0,0 +1,45 @@
|
|
|
1
|
+
name: Deploy GitHub Pages
|
|
2
|
+
|
|
3
|
+
on:
|
|
4
|
+
push:
|
|
5
|
+
branches: ["main"]
|
|
6
|
+
workflow_dispatch:
|
|
7
|
+
|
|
8
|
+
permissions:
|
|
9
|
+
contents: read
|
|
10
|
+
pages: write
|
|
11
|
+
id-token: write
|
|
12
|
+
|
|
13
|
+
concurrency:
|
|
14
|
+
group: "pages"
|
|
15
|
+
cancel-in-progress: false
|
|
16
|
+
|
|
17
|
+
jobs:
|
|
18
|
+
build:
|
|
19
|
+
runs-on: ubuntu-latest
|
|
20
|
+
steps:
|
|
21
|
+
- name: Checkout
|
|
22
|
+
uses: actions/checkout@v4
|
|
23
|
+
|
|
24
|
+
- name: Setup Pages
|
|
25
|
+
uses: actions/configure-pages@v5
|
|
26
|
+
|
|
27
|
+
- name: Build with Jekyll
|
|
28
|
+
uses: actions/jekyll-build-pages@v1
|
|
29
|
+
with:
|
|
30
|
+
source: ./
|
|
31
|
+
destination: ./_site
|
|
32
|
+
|
|
33
|
+
- name: Upload artifact
|
|
34
|
+
uses: actions/upload-pages-artifact@v3
|
|
35
|
+
|
|
36
|
+
deploy:
|
|
37
|
+
environment:
|
|
38
|
+
name: github-pages
|
|
39
|
+
url: ${{ steps.deployment.outputs.page_url }}
|
|
40
|
+
runs-on: ubuntu-latest
|
|
41
|
+
needs: build
|
|
42
|
+
steps:
|
|
43
|
+
- name: Deploy to GitHub Pages
|
|
44
|
+
id: deployment
|
|
45
|
+
uses: actions/deploy-pages@v4
|
|
@@ -0,0 +1,37 @@
|
|
|
1
|
+
name: Publish to PyPI
|
|
2
|
+
|
|
3
|
+
on:
|
|
4
|
+
release:
|
|
5
|
+
types: [published]
|
|
6
|
+
|
|
7
|
+
jobs:
|
|
8
|
+
deploy:
|
|
9
|
+
runs-on: ubuntu-latest
|
|
10
|
+
permissions:
|
|
11
|
+
id-token: write
|
|
12
|
+
contents: read
|
|
13
|
+
|
|
14
|
+
steps:
|
|
15
|
+
- uses: actions/checkout@v4
|
|
16
|
+
|
|
17
|
+
- name: Set up Python
|
|
18
|
+
uses: actions/setup-python@v5
|
|
19
|
+
with:
|
|
20
|
+
python-version: '3.10'
|
|
21
|
+
|
|
22
|
+
- name: Install build dependencies
|
|
23
|
+
run: |
|
|
24
|
+
python -m pip install --upgrade pip
|
|
25
|
+
pip install build twine
|
|
26
|
+
|
|
27
|
+
- name: Build distributions
|
|
28
|
+
run: python -m build
|
|
29
|
+
|
|
30
|
+
- name: Check distributions
|
|
31
|
+
run: python -m twine check dist/*
|
|
32
|
+
|
|
33
|
+
- name: Publish to PyPI
|
|
34
|
+
env:
|
|
35
|
+
TWINE_USERNAME: __token__
|
|
36
|
+
TWINE_PASSWORD: ${{ secrets.PYPI_API_TOKEN }}
|
|
37
|
+
run: python -m twine upload dist/* --non-interactive --verbose
|
sccode-0.1.0/.gitignore
ADDED
|
@@ -0,0 +1,207 @@
|
|
|
1
|
+
# Byte-compiled / optimized / DLL files
|
|
2
|
+
__pycache__/
|
|
3
|
+
*.py[codz]
|
|
4
|
+
*$py.class
|
|
5
|
+
|
|
6
|
+
# C extensions
|
|
7
|
+
*.so
|
|
8
|
+
|
|
9
|
+
# Distribution / packaging
|
|
10
|
+
.Python
|
|
11
|
+
build/
|
|
12
|
+
develop-eggs/
|
|
13
|
+
dist/
|
|
14
|
+
downloads/
|
|
15
|
+
eggs/
|
|
16
|
+
.eggs/
|
|
17
|
+
lib/
|
|
18
|
+
lib64/
|
|
19
|
+
parts/
|
|
20
|
+
sdist/
|
|
21
|
+
var/
|
|
22
|
+
wheels/
|
|
23
|
+
share/python-wheels/
|
|
24
|
+
*.egg-info/
|
|
25
|
+
.installed.cfg
|
|
26
|
+
*.egg
|
|
27
|
+
MANIFEST
|
|
28
|
+
|
|
29
|
+
# PyInstaller
|
|
30
|
+
# Usually these files are written by a python script from a template
|
|
31
|
+
# before PyInstaller builds the exe, so as to inject date/other infos into it.
|
|
32
|
+
*.manifest
|
|
33
|
+
*.spec
|
|
34
|
+
|
|
35
|
+
# Installer logs
|
|
36
|
+
pip-log.txt
|
|
37
|
+
pip-delete-this-directory.txt
|
|
38
|
+
|
|
39
|
+
# Unit test / coverage reports
|
|
40
|
+
htmlcov/
|
|
41
|
+
.tox/
|
|
42
|
+
.nox/
|
|
43
|
+
.coverage
|
|
44
|
+
.coverage.*
|
|
45
|
+
.cache
|
|
46
|
+
nosetests.xml
|
|
47
|
+
coverage.xml
|
|
48
|
+
*.cover
|
|
49
|
+
*.py.cover
|
|
50
|
+
.hypothesis/
|
|
51
|
+
.pytest_cache/
|
|
52
|
+
cover/
|
|
53
|
+
|
|
54
|
+
# Translations
|
|
55
|
+
*.mo
|
|
56
|
+
*.pot
|
|
57
|
+
|
|
58
|
+
# Django stuff:
|
|
59
|
+
*.log
|
|
60
|
+
local_settings.py
|
|
61
|
+
db.sqlite3
|
|
62
|
+
db.sqlite3-journal
|
|
63
|
+
|
|
64
|
+
# Flask stuff:
|
|
65
|
+
instance/
|
|
66
|
+
.webassets-cache
|
|
67
|
+
|
|
68
|
+
# Scrapy stuff:
|
|
69
|
+
.scrapy
|
|
70
|
+
|
|
71
|
+
# Sphinx documentation
|
|
72
|
+
docs/_build/
|
|
73
|
+
|
|
74
|
+
# PyBuilder
|
|
75
|
+
.pybuilder/
|
|
76
|
+
target/
|
|
77
|
+
|
|
78
|
+
# Jupyter Notebook
|
|
79
|
+
.ipynb_checkpoints
|
|
80
|
+
|
|
81
|
+
# IPython
|
|
82
|
+
profile_default/
|
|
83
|
+
ipython_config.py
|
|
84
|
+
|
|
85
|
+
# pyenv
|
|
86
|
+
# For a library or package, you might want to ignore these files since the code is
|
|
87
|
+
# intended to run in multiple environments; otherwise, check them in:
|
|
88
|
+
# .python-version
|
|
89
|
+
|
|
90
|
+
# pipenv
|
|
91
|
+
# According to pypa/pipenv#598, it is recommended to include Pipfile.lock in version control.
|
|
92
|
+
# However, in case of collaboration, if having platform-specific dependencies or dependencies
|
|
93
|
+
# having no cross-platform support, pipenv may install dependencies that don't work, or not
|
|
94
|
+
# install all needed dependencies.
|
|
95
|
+
#Pipfile.lock
|
|
96
|
+
|
|
97
|
+
# UV
|
|
98
|
+
# Similar to Pipfile.lock, it is generally recommended to include uv.lock in version control.
|
|
99
|
+
# This is especially recommended for binary packages to ensure reproducibility, and is more
|
|
100
|
+
# commonly ignored for libraries.
|
|
101
|
+
#uv.lock
|
|
102
|
+
|
|
103
|
+
# poetry
|
|
104
|
+
# Similar to Pipfile.lock, it is generally recommended to include poetry.lock in version control.
|
|
105
|
+
# This is especially recommended for binary packages to ensure reproducibility, and is more
|
|
106
|
+
# commonly ignored for libraries.
|
|
107
|
+
# https://python-poetry.org/docs/basic-usage/#commit-your-poetrylock-file-to-version-control
|
|
108
|
+
#poetry.lock
|
|
109
|
+
#poetry.toml
|
|
110
|
+
|
|
111
|
+
# pdm
|
|
112
|
+
# Similar to Pipfile.lock, it is generally recommended to include pdm.lock in version control.
|
|
113
|
+
# pdm recommends including project-wide configuration in pdm.toml, but excluding .pdm-python.
|
|
114
|
+
# https://pdm-project.org/en/latest/usage/project/#working-with-version-control
|
|
115
|
+
#pdm.lock
|
|
116
|
+
#pdm.toml
|
|
117
|
+
.pdm-python
|
|
118
|
+
.pdm-build/
|
|
119
|
+
|
|
120
|
+
# pixi
|
|
121
|
+
# Similar to Pipfile.lock, it is generally recommended to include pixi.lock in version control.
|
|
122
|
+
#pixi.lock
|
|
123
|
+
# Pixi creates a virtual environment in the .pixi directory, just like venv module creates one
|
|
124
|
+
# in the .venv directory. It is recommended not to include this directory in version control.
|
|
125
|
+
.pixi
|
|
126
|
+
|
|
127
|
+
# PEP 582; used by e.g. github.com/David-OConnor/pyflow and github.com/pdm-project/pdm
|
|
128
|
+
__pypackages__/
|
|
129
|
+
|
|
130
|
+
# Celery stuff
|
|
131
|
+
celerybeat-schedule
|
|
132
|
+
celerybeat.pid
|
|
133
|
+
|
|
134
|
+
# SageMath parsed files
|
|
135
|
+
*.sage.py
|
|
136
|
+
|
|
137
|
+
# Environments
|
|
138
|
+
.env
|
|
139
|
+
.envrc
|
|
140
|
+
.venv
|
|
141
|
+
env/
|
|
142
|
+
venv/
|
|
143
|
+
ENV/
|
|
144
|
+
env.bak/
|
|
145
|
+
venv.bak/
|
|
146
|
+
|
|
147
|
+
# Spyder project settings
|
|
148
|
+
.spyderproject
|
|
149
|
+
.spyproject
|
|
150
|
+
|
|
151
|
+
# Rope project settings
|
|
152
|
+
.ropeproject
|
|
153
|
+
|
|
154
|
+
# mkdocs documentation
|
|
155
|
+
/site
|
|
156
|
+
|
|
157
|
+
# mypy
|
|
158
|
+
.mypy_cache/
|
|
159
|
+
.dmypy.json
|
|
160
|
+
dmypy.json
|
|
161
|
+
|
|
162
|
+
# Pyre type checker
|
|
163
|
+
.pyre/
|
|
164
|
+
|
|
165
|
+
# pytype static type analyzer
|
|
166
|
+
.pytype/
|
|
167
|
+
|
|
168
|
+
# Cython debug symbols
|
|
169
|
+
cython_debug/
|
|
170
|
+
|
|
171
|
+
# PyCharm
|
|
172
|
+
# JetBrains specific template is maintained in a separate JetBrains.gitignore that can
|
|
173
|
+
# be found at https://github.com/github/gitignore/blob/main/Global/JetBrains.gitignore
|
|
174
|
+
# and can be added to the global gitignore or merged into this file. For a more nuclear
|
|
175
|
+
# option (not recommended) you can uncomment the following to ignore the entire idea folder.
|
|
176
|
+
#.idea/
|
|
177
|
+
|
|
178
|
+
# Abstra
|
|
179
|
+
# Abstra is an AI-powered process automation framework.
|
|
180
|
+
# Ignore directories containing user credentials, local state, and settings.
|
|
181
|
+
# Learn more at https://abstra.io/docs
|
|
182
|
+
.abstra/
|
|
183
|
+
|
|
184
|
+
# Visual Studio Code
|
|
185
|
+
# Visual Studio Code specific template is maintained in a separate VisualStudioCode.gitignore
|
|
186
|
+
# that can be found at https://github.com/github/gitignore/blob/main/Global/VisualStudioCode.gitignore
|
|
187
|
+
# and can be added to the global gitignore or merged into this file. However, if you prefer,
|
|
188
|
+
# you could uncomment the following to ignore the entire vscode folder
|
|
189
|
+
# .vscode/
|
|
190
|
+
|
|
191
|
+
# Ruff stuff:
|
|
192
|
+
.ruff_cache/
|
|
193
|
+
|
|
194
|
+
# PyPI configuration file
|
|
195
|
+
.pypirc
|
|
196
|
+
|
|
197
|
+
# Cursor
|
|
198
|
+
# Cursor is an AI-powered code editor. `.cursorignore` specifies files/directories to
|
|
199
|
+
# exclude from AI features like autocomplete and code analysis. Recommended for sensitive data
|
|
200
|
+
# refer to https://docs.cursor.com/context/ignore-files
|
|
201
|
+
.cursorignore
|
|
202
|
+
.cursorindexingignore
|
|
203
|
+
|
|
204
|
+
# Marimo
|
|
205
|
+
marimo/_static/
|
|
206
|
+
marimo/_lsp/
|
|
207
|
+
__marimo__/
|
|
@@ -0,0 +1,149 @@
|
|
|
1
|
+
# Contributing to CODE
|
|
2
|
+
|
|
3
|
+
Thank you for your interest in contributing to CODE! This document provides guidelines for contributing to the project.
|
|
4
|
+
|
|
5
|
+
## Getting Started
|
|
6
|
+
|
|
7
|
+
1. Fork the repository on GitHub
|
|
8
|
+
2. Clone your fork locally:
|
|
9
|
+
```bash
|
|
10
|
+
git clone https://github.com/YOUR-USERNAME/CODE.git
|
|
11
|
+
cd CODE
|
|
12
|
+
```
|
|
13
|
+
|
|
14
|
+
3. Create a virtual environment and install dependencies:
|
|
15
|
+
```bash
|
|
16
|
+
python -m venv venv
|
|
17
|
+
source venv/bin/activate # On Windows: venv\Scripts\activate
|
|
18
|
+
pip install -e ".[dev]"
|
|
19
|
+
```
|
|
20
|
+
|
|
21
|
+
## Development Process
|
|
22
|
+
|
|
23
|
+
### Setting Up Your Development Environment
|
|
24
|
+
|
|
25
|
+
1. Install the package in editable mode with development dependencies:
|
|
26
|
+
```bash
|
|
27
|
+
pip install -e ".[dev]"
|
|
28
|
+
```
|
|
29
|
+
|
|
30
|
+
2. Install pre-commit hooks (optional but recommended):
|
|
31
|
+
```bash
|
|
32
|
+
pip install pre-commit
|
|
33
|
+
pre-commit install
|
|
34
|
+
```
|
|
35
|
+
|
|
36
|
+
### Making Changes
|
|
37
|
+
|
|
38
|
+
1. Create a new branch for your feature or bugfix:
|
|
39
|
+
```bash
|
|
40
|
+
git checkout -b feature/your-feature-name
|
|
41
|
+
```
|
|
42
|
+
|
|
43
|
+
2. Make your changes, following the code style guidelines
|
|
44
|
+
|
|
45
|
+
3. Write or update tests for your changes
|
|
46
|
+
|
|
47
|
+
4. Run tests to ensure everything works:
|
|
48
|
+
```bash
|
|
49
|
+
pytest tests/
|
|
50
|
+
```
|
|
51
|
+
|
|
52
|
+
5. Format your code:
|
|
53
|
+
```bash
|
|
54
|
+
black src/CODE/
|
|
55
|
+
```
|
|
56
|
+
|
|
57
|
+
6. Check for common issues:
|
|
58
|
+
```bash
|
|
59
|
+
flake8 src/CODE/
|
|
60
|
+
```
|
|
61
|
+
|
|
62
|
+
### Submitting Changes
|
|
63
|
+
|
|
64
|
+
1. Commit your changes with a clear commit message:
|
|
65
|
+
```bash
|
|
66
|
+
git add .
|
|
67
|
+
git commit -m "Add feature: brief description"
|
|
68
|
+
```
|
|
69
|
+
|
|
70
|
+
2. Push to your fork:
|
|
71
|
+
```bash
|
|
72
|
+
git push origin feature/your-feature-name
|
|
73
|
+
```
|
|
74
|
+
|
|
75
|
+
3. Open a Pull Request on GitHub
|
|
76
|
+
|
|
77
|
+
## Code Style Guidelines
|
|
78
|
+
|
|
79
|
+
- Follow PEP 8 style guide for Python code
|
|
80
|
+
- Use meaningful variable and function names
|
|
81
|
+
- Write docstrings for all public functions, classes, and modules
|
|
82
|
+
- Keep functions focused and relatively small
|
|
83
|
+
- Add type hints where appropriate
|
|
84
|
+
|
|
85
|
+
### Docstring Format
|
|
86
|
+
|
|
87
|
+
Use Google-style docstrings:
|
|
88
|
+
|
|
89
|
+
```python
|
|
90
|
+
def example_function(arg1: int, arg2: str) -> bool:
|
|
91
|
+
"""
|
|
92
|
+
Brief description of the function.
|
|
93
|
+
|
|
94
|
+
More detailed description if needed.
|
|
95
|
+
|
|
96
|
+
Args:
|
|
97
|
+
arg1: Description of arg1
|
|
98
|
+
arg2: Description of arg2
|
|
99
|
+
|
|
100
|
+
Returns:
|
|
101
|
+
Description of return value
|
|
102
|
+
|
|
103
|
+
Raises:
|
|
104
|
+
ValueError: When something goes wrong
|
|
105
|
+
"""
|
|
106
|
+
pass
|
|
107
|
+
```
|
|
108
|
+
|
|
109
|
+
## Testing
|
|
110
|
+
|
|
111
|
+
- Write unit tests for new functionality
|
|
112
|
+
- Ensure existing tests pass
|
|
113
|
+
- Aim for good test coverage
|
|
114
|
+
- Test edge cases and error conditions
|
|
115
|
+
|
|
116
|
+
## Reporting Issues
|
|
117
|
+
|
|
118
|
+
When reporting issues, please include:
|
|
119
|
+
|
|
120
|
+
- A clear, descriptive title
|
|
121
|
+
- Detailed description of the issue
|
|
122
|
+
- Steps to reproduce the problem
|
|
123
|
+
- Expected behavior
|
|
124
|
+
- Actual behavior
|
|
125
|
+
- System information (OS, Python version, etc.)
|
|
126
|
+
- Relevant code snippets or error messages
|
|
127
|
+
|
|
128
|
+
## Feature Requests
|
|
129
|
+
|
|
130
|
+
We welcome feature requests! Please:
|
|
131
|
+
|
|
132
|
+
- Check if the feature has already been requested
|
|
133
|
+
- Clearly describe the feature and its use case
|
|
134
|
+
- Explain why it would be useful to the community
|
|
135
|
+
|
|
136
|
+
## Questions?
|
|
137
|
+
|
|
138
|
+
If you have questions, feel free to:
|
|
139
|
+
|
|
140
|
+
- Open an issue on GitHub
|
|
141
|
+
- Start a discussion in the GitHub Discussions tab
|
|
142
|
+
|
|
143
|
+
## License
|
|
144
|
+
|
|
145
|
+
By contributing to CODE, you agree that your contributions will be licensed under the MIT License.
|
|
146
|
+
|
|
147
|
+
## Acknowledgments
|
|
148
|
+
|
|
149
|
+
Thank you for helping improve CODE! Your contributions make this project better for everyone.
|
sccode-0.1.0/LICENSE
ADDED
|
@@ -0,0 +1,21 @@
|
|
|
1
|
+
MIT License
|
|
2
|
+
|
|
3
|
+
Copyright (c) 2025 Zeyu Fu
|
|
4
|
+
|
|
5
|
+
Permission is hereby granted, free of charge, to any person obtaining a copy
|
|
6
|
+
of this software and associated documentation files (the "Software"), to deal
|
|
7
|
+
in the Software without restriction, including without limitation the rights
|
|
8
|
+
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
|
|
9
|
+
copies of the Software, and to permit persons to whom the Software is
|
|
10
|
+
furnished to do so, subject to the following conditions:
|
|
11
|
+
|
|
12
|
+
The above copyright notice and this permission notice shall be included in all
|
|
13
|
+
copies or substantial portions of the Software.
|
|
14
|
+
|
|
15
|
+
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
|
|
16
|
+
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
|
|
17
|
+
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
|
|
18
|
+
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
|
|
19
|
+
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
|
|
20
|
+
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
|
|
21
|
+
SOFTWARE.
|