This release is a pre-release and may not be stable for production use.
th2 gRPC generator template library (1.4.0)
This is the template project for creating custom gRPC libraries. It contains an example of proto messages and services.
The tool generates code from .proto files and uploads built packages (.proto files and generated code) to the specified repositories.
How to transform the template
- Create a directory with the same name as the project name (use underscores instead of dashes) under
src/main/protodirectory (remove other files and directories if they exist). - Place your custom
.protofiles in the created directory. Pay attention to both thepackagespecifier and to theimportstatements. - Edit
release_versionandvcs_urlproperties ingradle.propertiesfile. - Edit
rootProject.namevariable insettings.gradlefile. This will be the name of the Java package. - Edit
package_info.jsonfile in order to specify its name and its version for Python package (create the file in case it's absent). - Edit parameters of
setup.pyinsetupfunction invocation such as:author,author_email,url. Do not edit the other's parameters. - Edit
README.mdfile according to the new project.
Note that the name of the created directory under src/main/proto directory is used in Python (it's a package name).
How to maintain a project
- Perform the necessary changes.
- Update the package version of Java in
gradle.propertiesfile. - Update the package version of Python in
package_info.jsonfile. - Commit everything.
How to run project
Java
If you wish to manually create and publish a package for Java, run the following command:
gradle --no-daemon clean build publish artifactoryPublish \
-Purl=${URL} \
-Puser=${USER} \
-Ppassword=${PASSWORD}
URL, USER and PASSWORD are parameters for publishing.
Python
If you wish to manually create and publish a package for Python:
- Generate services with
Gradle:
You can find the generated files by following path:gradle --no-daemon clean generateProtosrc/gen/main/services/python - Generate code from
.protofiles and publish everything usingtwine:pip install -r requirements.txt pip install twine python setup.py generate python setup.py sdist twine upload --repository-url ${PYPI_REPOSITORY_URL} --username ${PYPI_USER} --password ${PYPI_PASSWORD} dist/*PYPI_REPOSITORY_URL,PYPI_USERandPYPI_PASSWORDare parameters for publishing.
Release notes
1.4.0
- Implement stubs creation for Python
Metadata
Release files for th2-grpc-generator-template 1.4.0.dev3902254300
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| th2_grpc_generator_template-1.4.0.dev3902254300.tar.gz | 8.0 kB | Without provenance | Details for th2_grpc_generator_template-1.4.0.dev3902254300.tar.gz |
Release files / th2_grpc_generator_template-1.4.0.dev3902254300.tar.gz
| Download URL | th2_grpc_generator_template-1.4.0.dev3902254300.tar.gz |
|---|---|
| Size | 8.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0fa3e4151c3896c8f136f188911fea0bfa4b3b5bc7844e9a71f4e79e5922706f
|
|
BLAKE2b-256 checksum How to use checksums |
b4c18dacb9e9115ea7477d2431668cc1f76eecf58350b76c52f5362e57a0f54b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.9.16
|
Security for th2-grpc-generator-template 1.4.0.dev3902254300
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.