sampleproject-rs 0.0.2__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.
@@ -0,0 +1,25 @@
1
+ name: Publish Python Package
2
+
3
+ on:
4
+ release:
5
+ types:
6
+ - published
7
+
8
+ permissions:
9
+ contents: read
10
+
11
+ jobs:
12
+ publish:
13
+ runs-on: ubuntu-latest
14
+ environment: pypi
15
+ permissions:
16
+ id-token: write
17
+
18
+ steps:
19
+ - uses: actions/checkout@v5
20
+ - name: Build package
21
+ run: |
22
+ pipx run maturin build --release --out dist --sdist
23
+ pipx run twine check dist/*
24
+ - name: Publish package
25
+ uses: pypa/gh-action-pypi-publish@release/v1
@@ -0,0 +1,220 @@
1
+ /target
2
+
3
+ ### https://github.com/github/gitignore/blob/main/Python.gitignore ###
4
+ # Byte-compiled / optimized / DLL files
5
+ __pycache__/
6
+ *.py[codz]
7
+ *$py.class
8
+
9
+ # C extensions
10
+ *.so
11
+
12
+ # Distribution / packaging
13
+ .Python
14
+ build/
15
+ develop-eggs/
16
+ dist/
17
+ downloads/
18
+ eggs/
19
+ .eggs/
20
+ lib/
21
+ lib64/
22
+ parts/
23
+ sdist/
24
+ var/
25
+ wheels/
26
+ share/python-wheels/
27
+ *.egg-info/
28
+ .installed.cfg
29
+ *.egg
30
+ MANIFEST
31
+
32
+ # PyInstaller
33
+ # Usually these files are written by a python script from a template
34
+ # before PyInstaller builds the exe, so as to inject date/other infos into it.
35
+ *.manifest
36
+ *.spec
37
+
38
+ # Installer logs
39
+ pip-log.txt
40
+ pip-delete-this-directory.txt
41
+
42
+ # Unit test / coverage reports
43
+ htmlcov/
44
+ .tox/
45
+ .nox/
46
+ .coverage
47
+ .coverage.*
48
+ .cache
49
+ nosetests.xml
50
+ coverage.xml
51
+ *.cover
52
+ *.py.cover
53
+ .hypothesis/
54
+ .pytest_cache/
55
+ cover/
56
+
57
+ # Translations
58
+ *.mo
59
+ *.pot
60
+
61
+ # Django stuff:
62
+ *.log
63
+ local_settings.py
64
+ db.sqlite3
65
+ db.sqlite3-journal
66
+
67
+ # Flask stuff:
68
+ instance/
69
+ .webassets-cache
70
+
71
+ # Scrapy stuff:
72
+ .scrapy
73
+
74
+ # Sphinx documentation
75
+ docs/_build/
76
+
77
+ # PyBuilder
78
+ .pybuilder/
79
+ target/
80
+
81
+ # Jupyter Notebook
82
+ .ipynb_checkpoints
83
+
84
+ # IPython
85
+ profile_default/
86
+ ipython_config.py
87
+
88
+ # pyenv
89
+ # For a library or package, you might want to ignore these files since the code is
90
+ # intended to run in multiple environments; otherwise, check them in:
91
+ # .python-version
92
+
93
+ # pipenv
94
+ # According to pypa/pipenv#598, it is recommended to include Pipfile.lock in version control.
95
+ # However, in case of collaboration, if having platform-specific dependencies or dependencies
96
+ # having no cross-platform support, pipenv may install dependencies that don't work, or not
97
+ # install all needed dependencies.
98
+ #Pipfile.lock
99
+
100
+ # UV
101
+ # Similar to Pipfile.lock, it is generally recommended to include uv.lock in version control.
102
+ # This is especially recommended for binary packages to ensure reproducibility, and is more
103
+ # commonly ignored for libraries.
104
+ #uv.lock
105
+
106
+ # poetry
107
+ # Similar to Pipfile.lock, it is generally recommended to include poetry.lock in version control.
108
+ # This is especially recommended for binary packages to ensure reproducibility, and is more
109
+ # commonly ignored for libraries.
110
+ # https://python-poetry.org/docs/basic-usage/#commit-your-poetrylock-file-to-version-control
111
+ #poetry.lock
112
+ #poetry.toml
113
+
114
+ # pdm
115
+ # Similar to Pipfile.lock, it is generally recommended to include pdm.lock in version control.
116
+ # pdm recommends including project-wide configuration in pdm.toml, but excluding .pdm-python.
117
+ # https://pdm-project.org/en/latest/usage/project/#working-with-version-control
118
+ #pdm.lock
119
+ #pdm.toml
120
+ .pdm-python
121
+ .pdm-build/
122
+
123
+ # pixi
124
+ # Similar to Pipfile.lock, it is generally recommended to include pixi.lock in version control.
125
+ #pixi.lock
126
+ # Pixi creates a virtual environment in the .pixi directory, just like venv module creates one
127
+ # in the .venv directory. It is recommended not to include this directory in version control.
128
+ .pixi
129
+
130
+ # PEP 582; used by e.g. github.com/David-OConnor/pyflow and github.com/pdm-project/pdm
131
+ __pypackages__/
132
+
133
+ # Celery stuff
134
+ celerybeat-schedule
135
+ celerybeat.pid
136
+
137
+ # Redis
138
+ *.rdb
139
+ *.aof
140
+ *.pid
141
+
142
+ # RabbitMQ
143
+ mnesia/
144
+ rabbitmq/
145
+ rabbitmq-data/
146
+
147
+ # ActiveMQ
148
+ activemq-data/
149
+
150
+ # SageMath parsed files
151
+ *.sage.py
152
+
153
+ # Environments
154
+ .env
155
+ .envrc
156
+ .venv
157
+ env/
158
+ venv/
159
+ ENV/
160
+ env.bak/
161
+ venv.bak/
162
+
163
+ # Spyder project settings
164
+ .spyderproject
165
+ .spyproject
166
+
167
+ # Rope project settings
168
+ .ropeproject
169
+
170
+ # mkdocs documentation
171
+ /site
172
+
173
+ # mypy
174
+ .mypy_cache/
175
+ .dmypy.json
176
+ dmypy.json
177
+
178
+ # Pyre type checker
179
+ .pyre/
180
+
181
+ # pytype static type analyzer
182
+ .pytype/
183
+
184
+ # Cython debug symbols
185
+ cython_debug/
186
+
187
+ # PyCharm
188
+ # JetBrains specific template is maintained in a separate JetBrains.gitignore that can
189
+ # be found at https://github.com/github/gitignore/blob/main/Global/JetBrains.gitignore
190
+ # and can be added to the global gitignore or merged into this file. For a more nuclear
191
+ # option (not recommended) you can uncomment the following to ignore the entire idea folder.
192
+ #.idea/
193
+
194
+ # Abstra
195
+ # Abstra is an AI-powered process automation framework.
196
+ # Ignore directories containing user credentials, local state, and settings.
197
+ # Learn more at https://abstra.io/docs
198
+ .abstra/
199
+
200
+ # Visual Studio Code
201
+ # Visual Studio Code specific template is maintained in a separate VisualStudioCode.gitignore
202
+ # that can be found at https://github.com/github/gitignore/blob/main/Global/VisualStudioCode.gitignore
203
+ # and can be added to the global gitignore or merged into this file. However, if you prefer,
204
+ # you could uncomment the following to ignore the entire vscode folder
205
+ # .vscode/
206
+
207
+ # Ruff stuff:
208
+ .ruff_cache/
209
+
210
+ # PyPI configuration file
211
+ .pypirc
212
+
213
+ # Marimo
214
+ marimo/_static/
215
+ marimo/_lsp/
216
+ __marimo__/
217
+
218
+ # Streamlit
219
+ .streamlit/secrets.toml
220
+ ### End of Python.gitignore ###
@@ -0,0 +1,170 @@
1
+ # This file is automatically @generated by Cargo.
2
+ # It is not intended for manual editing.
3
+ version = 4
4
+
5
+ [[package]]
6
+ name = "anstyle"
7
+ version = "1.0.11"
8
+ source = "registry+https://github.com/rust-lang/crates.io-index"
9
+ checksum = "862ed96ca487e809f1c8e5a8447f6ee2cf102f846893800b20cebdf541fc6bbd"
10
+
11
+ [[package]]
12
+ name = "assert_cmd"
13
+ version = "2.0.17"
14
+ source = "registry+https://github.com/rust-lang/crates.io-index"
15
+ checksum = "2bd389a4b2970a01282ee455294913c0a43724daedcd1a24c3eb0ec1c1320b66"
16
+ dependencies = [
17
+ "anstyle",
18
+ "bstr",
19
+ "doc-comment",
20
+ "libc",
21
+ "predicates",
22
+ "predicates-core",
23
+ "predicates-tree",
24
+ "wait-timeout",
25
+ ]
26
+
27
+ [[package]]
28
+ name = "bstr"
29
+ version = "1.12.0"
30
+ source = "registry+https://github.com/rust-lang/crates.io-index"
31
+ checksum = "234113d19d0d7d613b40e86fb654acf958910802bcceab913a4f9e7cda03b1a4"
32
+ dependencies = [
33
+ "memchr",
34
+ "regex-automata",
35
+ "serde",
36
+ ]
37
+
38
+ [[package]]
39
+ name = "difflib"
40
+ version = "0.4.0"
41
+ source = "registry+https://github.com/rust-lang/crates.io-index"
42
+ checksum = "6184e33543162437515c2e2b48714794e37845ec9851711914eec9d308f6ebe8"
43
+
44
+ [[package]]
45
+ name = "doc-comment"
46
+ version = "0.3.3"
47
+ source = "registry+https://github.com/rust-lang/crates.io-index"
48
+ checksum = "fea41bba32d969b513997752735605054bc0dfa92b4c56bf1189f2e174be7a10"
49
+
50
+ [[package]]
51
+ name = "libc"
52
+ version = "0.2.175"
53
+ source = "registry+https://github.com/rust-lang/crates.io-index"
54
+ checksum = "6a82ae493e598baaea5209805c49bbf2ea7de956d50d7da0da1164f9c6d28543"
55
+
56
+ [[package]]
57
+ name = "memchr"
58
+ version = "2.7.5"
59
+ source = "registry+https://github.com/rust-lang/crates.io-index"
60
+ checksum = "32a282da65faaf38286cf3be983213fcf1d2e2a58700e808f83f4ea9a4804bc0"
61
+
62
+ [[package]]
63
+ name = "predicates"
64
+ version = "3.1.3"
65
+ source = "registry+https://github.com/rust-lang/crates.io-index"
66
+ checksum = "a5d19ee57562043d37e82899fade9a22ebab7be9cef5026b07fda9cdd4293573"
67
+ dependencies = [
68
+ "anstyle",
69
+ "difflib",
70
+ "predicates-core",
71
+ ]
72
+
73
+ [[package]]
74
+ name = "predicates-core"
75
+ version = "1.0.9"
76
+ source = "registry+https://github.com/rust-lang/crates.io-index"
77
+ checksum = "727e462b119fe9c93fd0eb1429a5f7647394014cf3c04ab2c0350eeb09095ffa"
78
+
79
+ [[package]]
80
+ name = "predicates-tree"
81
+ version = "1.0.12"
82
+ source = "registry+https://github.com/rust-lang/crates.io-index"
83
+ checksum = "72dd2d6d381dfb73a193c7fca536518d7caee39fc8503f74e7dc0be0531b425c"
84
+ dependencies = [
85
+ "predicates-core",
86
+ "termtree",
87
+ ]
88
+
89
+ [[package]]
90
+ name = "proc-macro2"
91
+ version = "1.0.101"
92
+ source = "registry+https://github.com/rust-lang/crates.io-index"
93
+ checksum = "89ae43fd86e4158d6db51ad8e2b80f313af9cc74f5c0e03ccb87de09998732de"
94
+ dependencies = [
95
+ "unicode-ident",
96
+ ]
97
+
98
+ [[package]]
99
+ name = "quote"
100
+ version = "1.0.40"
101
+ source = "registry+https://github.com/rust-lang/crates.io-index"
102
+ checksum = "1885c039570dc00dcb4ff087a89e185fd56bae234ddc7f056a945bf36467248d"
103
+ dependencies = [
104
+ "proc-macro2",
105
+ ]
106
+
107
+ [[package]]
108
+ name = "regex-automata"
109
+ version = "0.4.10"
110
+ source = "registry+https://github.com/rust-lang/crates.io-index"
111
+ checksum = "6b9458fa0bfeeac22b5ca447c63aaf45f28439a709ccd244698632f9aa6394d6"
112
+
113
+ [[package]]
114
+ name = "sample"
115
+ version = "0.0.1"
116
+ dependencies = [
117
+ "assert_cmd",
118
+ ]
119
+
120
+ [[package]]
121
+ name = "serde"
122
+ version = "1.0.219"
123
+ source = "registry+https://github.com/rust-lang/crates.io-index"
124
+ checksum = "5f0e2c6ed6606019b4e29e69dbaba95b11854410e5347d525002456dbbb786b6"
125
+ dependencies = [
126
+ "serde_derive",
127
+ ]
128
+
129
+ [[package]]
130
+ name = "serde_derive"
131
+ version = "1.0.219"
132
+ source = "registry+https://github.com/rust-lang/crates.io-index"
133
+ checksum = "5b0276cf7f2c73365f7157c8123c21cd9a50fbbd844757af28ca1f5925fc2a00"
134
+ dependencies = [
135
+ "proc-macro2",
136
+ "quote",
137
+ "syn",
138
+ ]
139
+
140
+ [[package]]
141
+ name = "syn"
142
+ version = "2.0.106"
143
+ source = "registry+https://github.com/rust-lang/crates.io-index"
144
+ checksum = "ede7c438028d4436d71104916910f5bb611972c5cfd7f89b8300a8186e6fada6"
145
+ dependencies = [
146
+ "proc-macro2",
147
+ "quote",
148
+ "unicode-ident",
149
+ ]
150
+
151
+ [[package]]
152
+ name = "termtree"
153
+ version = "0.5.1"
154
+ source = "registry+https://github.com/rust-lang/crates.io-index"
155
+ checksum = "8f50febec83f5ee1df3015341d8bd429f2d1cc62bcba7ea2076759d315084683"
156
+
157
+ [[package]]
158
+ name = "unicode-ident"
159
+ version = "1.0.19"
160
+ source = "registry+https://github.com/rust-lang/crates.io-index"
161
+ checksum = "f63a545481291138910575129486daeaf8ac54aee4387fe7906919f7830c7d9d"
162
+
163
+ [[package]]
164
+ name = "wait-timeout"
165
+ version = "0.2.1"
166
+ source = "registry+https://github.com/rust-lang/crates.io-index"
167
+ checksum = "09ac3b126d3914f9849036f826e054cbabdc8519970b8998ddaf3b5bd3c65f11"
168
+ dependencies = [
169
+ "libc",
170
+ ]
@@ -0,0 +1,10 @@
1
+ [package]
2
+ name = "sample"
3
+ version = "0.0.1"
4
+ edition = "2024"
5
+ readme = "README.md"
6
+
7
+ [dependencies]
8
+
9
+ [dev-dependencies]
10
+ assert_cmd = "2"
@@ -0,0 +1,21 @@
1
+ MIT License
2
+
3
+ Copyright (c) 2025 nikkie
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.
@@ -0,0 +1,50 @@
1
+ Metadata-Version: 2.4
2
+ Name: sampleproject-rs
3
+ Version: 0.0.2
4
+ Classifier: Development Status :: 1 - Planning
5
+ Classifier: Intended Audience :: Developers
6
+ Classifier: Topic :: Software Development :: Build Tools
7
+ Classifier: License :: OSI Approved :: MIT License
8
+ Classifier: Programming Language :: Python :: 3
9
+ Classifier: Programming Language :: Python :: 3.10
10
+ Classifier: Programming Language :: Python :: 3.11
11
+ Classifier: Programming Language :: Python :: 3.12
12
+ Classifier: Programming Language :: Python :: 3.13
13
+ Classifier: Programming Language :: Python :: 3 :: Only
14
+ Provides-Extra: dev
15
+ Provides-Extra: test
16
+ License-File: LICENSE
17
+ Summary: A sample Python project from Rust binary
18
+ Keywords: sample,maturin,development
19
+ Author-email: ftnext <takuyafjp+develop@gmail.com>
20
+ Requires-Python: >=3.10
21
+ Description-Content-Type: text/markdown; charset=UTF-8; variant=GFM
22
+ Project-URL: Homepage, https://github.com/ftnext/sampleproject-rs
23
+ Project-URL: Bug Reports, https://github.com/ftnext/sampleproject-rs/issues
24
+ Project-URL: Source, https://github.com/ftnext/sampleproject-rs/
25
+
26
+ # A sample Python project from Rust binary
27
+
28
+ Inspired [sampleproject](https://github.com/pypa/sampleproject/).
29
+
30
+ *Currently distributed to GitHub Codespace (Ubuntu) only.*
31
+
32
+ ----
33
+
34
+ This is the README file for the project.
35
+
36
+ The file should use UTF-8 encoding and can be written using
37
+ [reStructuredText][rst] or [markdown][md use] with the appropriate [key set][md
38
+ use]. It will be used to generate the project webpage on PyPI and will be
39
+ displayed as the project homepage on common code-hosting services, and should be
40
+ written for that purpose.
41
+
42
+ Typical contents for this file would include an overview of the project, basic
43
+ usage examples, etc. Generally, including the project changelog in here is not a
44
+ good idea, although a simple “What's New” section for the most recent version
45
+ may be appropriate.
46
+
47
+ [rst]: http://docutils.sourceforge.net/rst.html
48
+ [md]: https://tools.ietf.org/html/rfc7764#section-3.5 "CommonMark variant"
49
+ [md use]: https://packaging.python.org/specifications/core-metadata/#description-content-type-optional
50
+
@@ -0,0 +1,24 @@
1
+ # A sample Python project from Rust binary
2
+
3
+ Inspired [sampleproject](https://github.com/pypa/sampleproject/).
4
+
5
+ *Currently distributed to GitHub Codespace (Ubuntu) only.*
6
+
7
+ ----
8
+
9
+ This is the README file for the project.
10
+
11
+ The file should use UTF-8 encoding and can be written using
12
+ [reStructuredText][rst] or [markdown][md use] with the appropriate [key set][md
13
+ use]. It will be used to generate the project webpage on PyPI and will be
14
+ displayed as the project homepage on common code-hosting services, and should be
15
+ written for that purpose.
16
+
17
+ Typical contents for this file would include an overview of the project, basic
18
+ usage examples, etc. Generally, including the project changelog in here is not a
19
+ good idea, although a simple “What's New” section for the most recent version
20
+ may be appropriate.
21
+
22
+ [rst]: http://docutils.sourceforge.net/rst.html
23
+ [md]: https://tools.ietf.org/html/rfc7764#section-3.5 "CommonMark variant"
24
+ [md use]: https://packaging.python.org/specifications/core-metadata/#description-content-type-optional
@@ -0,0 +1,146 @@
1
+ [build-system]
2
+ # A list of packages that are needed to build your package:
3
+ requires = ["maturin>=1.8,<2.0"] # REQUIRED if [build-system] table is used
4
+ # The name of the Python object that frontends will use to perform the build:
5
+ build-backend = "maturin"
6
+
7
+ [project]
8
+ # This is the name of your project. The first time you publish this
9
+ # package, this name will be registered for you. It will determine how
10
+ # users can install this project, e.g.:
11
+ #
12
+ # $ pip install sampleproject-rs
13
+ #
14
+ # And where it will live on PyPI: https://pypi.org/project/sampleproject-rs/
15
+ #
16
+ # There are some restrictions on what makes a valid project name
17
+ # specification here:
18
+ # https://packaging.python.org/specifications/core-metadata/#name
19
+ name = "sampleproject-rs" # REQUIRED, is the only field that cannot be marked as dynamic.
20
+
21
+ # Versions should comply with PEP 440:
22
+ # https://www.python.org/dev/peps/pep-0440/
23
+ #
24
+ # For a discussion on single-sourcing the version, see
25
+ # https://packaging.python.org/guides/single-sourcing-package-version/
26
+ version = "0.0.2" # REQUIRED, although can be dynamic
27
+
28
+ # This is a one-line description or tagline of what your project does. This
29
+ # corresponds to the "Summary" metadata field:
30
+ # https://packaging.python.org/specifications/core-metadata/#summary
31
+ description = "A sample Python project from Rust binary"
32
+
33
+ # This is an optional longer description of your project that represents
34
+ # the body of text which users will see when they visit PyPI.
35
+ #
36
+ # Often, this is the same as your README, so you can just read it in from
37
+ # that file directly.
38
+ #
39
+ # This field corresponds to the "Description" metadata field:
40
+ # https://packaging.python.org/specifications/core-metadata/#description-optional
41
+ readme = "README.md"
42
+
43
+ # Specify which Python versions you support. In contrast to the
44
+ # 'Programming Language' classifiers in this file, 'pip install' will check this
45
+ # and refuse to install the project if the version does not match. See
46
+ # https://packaging.python.org/guides/distributing-packages-using-setuptools/#python-requires
47
+ requires-python = ">=3.10"
48
+
49
+ # This is either text indicating the license for the distribution, or a file
50
+ # that contains the license.
51
+ # https://packaging.python.org/en/latest/specifications/core-metadata/#license
52
+ license = { file = "LICENSE" }
53
+
54
+ # This field adds keywords for your project which will appear on the
55
+ # project page. What does your project relate to?
56
+ #
57
+ # Note that this is a list of additional keywords, separated
58
+ # by commas, to be used to assist searching for the distribution in a
59
+ # larger catalog.
60
+ keywords = ["sample", "maturin", "development"]
61
+
62
+ # This should be your name or the name of the organization who originally
63
+ # authored the project, and a valid email address corresponding to the name
64
+ # listed.
65
+ authors = [{ name = "ftnext", email = "takuyafjp+develop@gmail.com" }]
66
+
67
+ # This should be your name or the names of the organization who currently
68
+ # maintains the project, and a valid email address corresponding to the name
69
+ # listed.
70
+ maintainers = []
71
+
72
+ # Classifiers help users find your project by categorizing it.
73
+ #
74
+ # For a list of valid classifiers, see https://pypi.org/classifiers/
75
+ classifiers = [
76
+ # How mature is this project? Common values are
77
+ # 3 - Alpha
78
+ # 4 - Beta
79
+ # 5 - Production/Stable
80
+ "Development Status :: 1 - Planning",
81
+
82
+ # Indicate who your project is intended for
83
+ "Intended Audience :: Developers",
84
+ "Topic :: Software Development :: Build Tools",
85
+
86
+ # Pick your license as you wish
87
+ "License :: OSI Approved :: MIT License",
88
+
89
+ # Specify the Python versions you support here. In particular, ensure
90
+ # that you indicate you support Python 3. These classifiers are *not*
91
+ # checked by "pip install". See instead "requires-python" key in this file.
92
+ "Programming Language :: Python :: 3",
93
+ "Programming Language :: Python :: 3.10",
94
+ "Programming Language :: Python :: 3.11",
95
+ "Programming Language :: Python :: 3.12",
96
+ "Programming Language :: Python :: 3.13",
97
+ "Programming Language :: Python :: 3 :: Only",
98
+ ]
99
+
100
+ # This field lists other packages that your project depends on to run.
101
+ # Any package you put here will be installed by pip when your project is
102
+ # installed, so they must be valid existing projects.
103
+ #
104
+ # For an analysis of this field vs pip's requirements files see:
105
+ # https://packaging.python.org/discussions/install-requires-vs-requirements/
106
+ dependencies = []
107
+
108
+ # List additional groups of dependencies here (e.g. development
109
+ # dependencies). Users will be able to install these using the "extras"
110
+ # syntax, for example:
111
+ #
112
+ # $ pip install sampleproject-rs[dev]
113
+ #
114
+ # Optional dependencies the project provides. These are commonly
115
+ # referred to as "extras". For a more extensive definition see:
116
+ # https://packaging.python.org/en/latest/specifications/dependency-specifiers/#extras
117
+ [project.optional-dependencies]
118
+ dev = []
119
+ test = []
120
+
121
+ # List URLs that are relevant to your project
122
+ #
123
+ # This field corresponds to the "Project-URL" and "Home-Page" metadata fields:
124
+ # https://packaging.python.org/specifications/core-metadata/#project-url-multiple-use
125
+ # https://packaging.python.org/specifications/core-metadata/#home-page-optional
126
+ #
127
+ # Examples listed include a pattern for specifying where the package tracks
128
+ # issues, where the source is hosted, where to say thanks to the package
129
+ # maintainers, and where to support the project financially. The key is
130
+ # what's used to render the link text on PyPI.
131
+ [project.urls]
132
+ "Homepage" = "https://github.com/ftnext/sampleproject-rs"
133
+ "Bug Reports" = "https://github.com/ftnext/sampleproject-rs/issues"
134
+ "Source" = "https://github.com/ftnext/sampleproject-rs/"
135
+
136
+ # The following would provide a command line executable called `sample`
137
+ # which executes the function `main` from this package when invoked.
138
+ # [project.scripts]
139
+ # sample = "sample:main"
140
+
141
+
142
+ # This is configuration specific to the `maturin` build backend.
143
+ # If you are using a different build backend, you will need to change this.
144
+ [tool.maturin]
145
+ bindings = "bin"
146
+ strip = true
@@ -0,0 +1,3 @@
1
+ fn main() {
2
+ println!("Call your main application code here");
3
+ }
@@ -0,0 +1,8 @@
1
+ use assert_cmd::Command;
2
+
3
+ #[test]
4
+ fn test_cli() {
5
+ let mut cmd = Command::cargo_bin("sample").unwrap();
6
+ let assert = cmd.assert();
7
+ assert.success().stdout("Call your main application code here\n");
8
+ }