| Name | configurematic JSON |
| Version |
0.0.1
JSON |
| download |
| home_page | None |
| Summary | Put configuration from one file into multiple files |
| upload_time | 2024-12-08 09:19:54 |
| maintainer | None |
| docs_url | None |
| author | None |
| requires_python | >=3.10 |
| license | 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. |
| keywords |
feed
reader
tutorial
|
| VCS |
 |
| bugtrack_url |
|
| requirements |
python-dotenv
|
| Travis-CI |
No Travis.
|
| coveralls test coverage |
No coveralls.
|
# Configurematic
## Description
Have you found yourself in the situation where you have the same configuration
in multiple configuration files? We all know config should be in one place
only but sometimes we have several `.env` files, for example, for related apps,
and `env` file for docker plus some configuration in places like
`pyproject.toml`, `package.json`, etc.
Configurematic lets you write a single `.env` file (called `config.env` by
default) and have variable from that file substituted into any other file.
It is a lightweight, compact script with `python-dotenv` as its only
dependency.
## Installing
Install with
```shell
pip install configurematic
```
Alternatively, install it with `pipx`:
```shell
pipx install configurematic
```
## Using Configurematic
First create your `config.env` file. An example might be
```shell
APP_NAME="My App Name"
DBPASSWORD="SecretPassword"
```
This is parsed by `dotenv` so you can have blank lines, comments starting
with `#`, etc.
Next create files you want to substitute these into. Prefix them with
`example-` (though this can be overridden with the `--prefix` option).
For example you might have
`example-env`:
```shell
APP_NAME="__APP_NAME__"
```
`app/example-.env`:
```shell
APP_NAME="__APP_NAME__"
PWD="__DBPASSWORD__"
```
Anything between the `__` pairs is substituted by the variable matching that
name in your `config.env`, provided it exists.
Your `example-*` files don't have to be `.env`-like and can have multiple
variables on one line, eg
```python
print("The current version is __MAJOR__VERSION__.__MINOR_VERSION__")
```
Variables starting and ending with `__` will only be substituted if they
are in your `config.env` file.
Next, create a file listing your templates (without the `example-` prefix),
one per line:
`files.txt`:
```
env
app/.env
```
This file can also contain blank lines and comments starting with `#`.
Alternatively you can list the files on the command line. Whitespace at the
start and end of each line though is stripped, therefore filenames cannot
start or end with a whitespace character (not that they should). Whitespace
inside a filename is fine. They also cannot start with a `#`, though it can
appear elsewhere in the filename.
If for some reason you do want a space at the beginning or end of a filename
or you do want a file to start with `#`, list the files on the command line
instead of in a file.
Finally, run Configurematic:
```shell
configurematic -f files.txt
```
Next to each of your `example-*` files you will see a new file without
the `example-` prefix.
Run it again and the new files will be overwritten (warning, you will
lose any manual changes) but the old versions will be copied to a new file
next to it with a `.old` suffix (which can be overridden with `--backup-ext`).
## Options
Use `--conf-file` or `-c` to use a different file instead of `config.env`.
To output all the files to a different directory (with the same directory
hierarchy within it), use `--outdir` or `-o`.
Change the prefix with `-p` or `--prefix`.
`-r` or `--recursive` turns on recusion (see below).
Change `__` to something else with `-d` or `--delimeter`.
Change the backup extension with `-b` or `--backup-ext`. Set this to `""`
to not write backup files.
Turn off verbose output with `-q` or `--silent`.
Instead of listing the files in a file pointed to with `-f`, you can list
them on the command line, eg:
```shell
configurematic env app/.env
```
## Recursion
You can make substitution recursive with the `-r` or `--recursive` flag.
Say you have the following in your `config.env`:
```shell
VAR1="__VAR2__"
VAR2="Value Here"
```
and the following in a template:
```shell
MY_VAR1="__VAR1__"
```
The result will be
```shell
MY_VAR1="Value Here"
```
By default, recursion is off, meaning only one level of substitution is made.
## Changing files
If you edit a generated file, then run Configurematic again, you will lose
your changes (though they are kept in the backup file). Thus it is best
to edit your `example-*` files only (and of course `config.env`), and rerun
Configurematic to generate the files again.
## Licence
Configurematic is distributed under the Apache licence.
## Author
Matthew Baker is an IT manager at ETH Zurich. He also does consultancy work.
Contact him at `matt@mattbaker.ch`.
Raw data
{
"_id": null,
"home_page": null,
"name": "configurematic",
"maintainer": null,
"docs_url": null,
"requires_python": ">=3.10",
"maintainer_email": null,
"keywords": "feed, reader, tutorial",
"author": null,
"author_email": "Matthew Baker <matt@mattbaker.ch>",
"download_url": "https://files.pythonhosted.org/packages/58/2b/8d351bac6c7652f68d11084474c2c2d6e503e6e557a50e0bf22f5ac0cc85/configurematic-0.0.1.tar.gz",
"platform": null,
"description": "# Configurematic\n\n## Description\n\nHave you found yourself in the situation where you have the same configuration\nin multiple configuration files? We all know config should be in one place\nonly but sometimes we have several `.env` files, for example, for related apps,\nand `env` file for docker plus some configuration in places like\n`pyproject.toml`, `package.json`, etc.\n\nConfigurematic lets you write a single `.env` file (called `config.env` by\ndefault) and have variable from that file substituted into any other file. \nIt is a lightweight, compact script with `python-dotenv` as its only\ndependency.\n\n## Installing\n\nInstall with\n\n```shell\npip install configurematic\n```\n\nAlternatively, install it with `pipx`:\n\n```shell\npipx install configurematic\n```\n\n## Using Configurematic\n\nFirst create your `config.env` file. An example might be\n\n```shell\nAPP_NAME=\"My App Name\"\nDBPASSWORD=\"SecretPassword\"\n```\n\nThis is parsed by `dotenv` so you can have blank lines, comments starting\nwith `#`, etc.\n\nNext create files you want to substitute these into. Prefix them with\n`example-` (though this can be overridden with the `--prefix` option).\n\nFor example you might have\n\n`example-env`:\n\n```shell\nAPP_NAME=\"__APP_NAME__\"\n```\n\n`app/example-.env`:\n\n```shell\nAPP_NAME=\"__APP_NAME__\"\nPWD=\"__DBPASSWORD__\"\n```\n\nAnything between the `__` pairs is substituted by the variable matching that\nname in your `config.env`, provided it exists.\n\nYour `example-*` files don't have to be `.env`-like and can have multiple \nvariables on one line, eg\n\n```python\nprint(\"The current version is __MAJOR__VERSION__.__MINOR_VERSION__\")\n```\n\nVariables starting and ending with `__` will only be substituted if they\nare in your `config.env` file.\n\nNext, create a file listing your templates (without the `example-` prefix),\none per line:\n\n`files.txt`:\n\n```\nenv\napp/.env\n```\n\nThis file can also contain blank lines and comments starting with `#`.\nAlternatively you can list the files on the command line. Whitespace at the\nstart and end of each line though is stripped, therefore filenames cannot\nstart or end with a whitespace character (not that they should). Whitespace\ninside a filename is fine. They also cannot start with a `#`, though it can\nappear elsewhere in the filename.\n\nIf for some reason you do want a space at the beginning or end of a filename\nor you do want a file to start with `#`, list the files on the command line\ninstead of in a file.\n\nFinally, run Configurematic:\n\n```shell\nconfigurematic -f files.txt\n```\n\nNext to each of your `example-*` files you will see a new file without\nthe `example-` prefix.\n\nRun it again and the new files will be overwritten (warning, you will\nlose any manual changes) but the old versions will be copied to a new file\nnext to it with a `.old` suffix (which can be overridden with `--backup-ext`).\n\n## Options\n\nUse `--conf-file` or `-c` to use a different file instead of `config.env`.\n\nTo output all the files to a different directory (with the same directory\nhierarchy within it), use `--outdir` or `-o`.\n\nChange the prefix with `-p` or `--prefix`.\n\n`-r` or `--recursive` turns on recusion (see below).\n\nChange `__` to something else with `-d` or `--delimeter`.\n\nChange the backup extension with `-b` or `--backup-ext`. Set this to `\"\"`\nto not write backup files.\n\nTurn off verbose output with `-q` or `--silent`.\n\nInstead of listing the files in a file pointed to with `-f`, you can list\nthem on the command line, eg:\n\n```shell\nconfigurematic env app/.env\n```\n## Recursion\n\nYou can make substitution recursive with the `-r` or `--recursive` flag.\n\nSay you have the following in your `config.env`:\n\n```shell\nVAR1=\"__VAR2__\"\nVAR2=\"Value Here\"\n```\n\nand the following in a template:\n\n```shell\nMY_VAR1=\"__VAR1__\"\n```\n\nThe result will be\n\n```shell\nMY_VAR1=\"Value Here\"\n```\n\nBy default, recursion is off, meaning only one level of substitution is made.\n\n## Changing files\n\nIf you edit a generated file, then run Configurematic again, you will lose\nyour changes (though they are kept in the backup file). Thus it is best\nto edit your `example-*` files only (and of course `config.env`), and rerun \nConfigurematic to generate the files again.\n\n## Licence\n\nConfigurematic is distributed under the Apache licence.\n\n## Author\n\nMatthew Baker is an IT manager at ETH Zurich. He also does consultancy work.\nContact him at `matt@mattbaker.ch`.\n\n\n",
"bugtrack_url": null,
"license": " 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. ",
"summary": "Put configuration from one file into multiple files",
"version": "0.0.1",
"project_urls": {
"repository": "https://github.com/mbakereth/configurematic"
},
"split_keywords": [
"feed",
" reader",
" tutorial"
],
"urls": [
{
"comment_text": "",
"digests": {
"blake2b_256": "1bb4c62060b7b2d38ae6dc429b72386d6dd6c0ebbeda6d29aa96508b6be4a216",
"md5": "506526fe617270d8bde85d3e8dcc5e78",
"sha256": "7c70d24fad5e8be4ed098fc36851798dd3eac1dd9520ad6c18947a3dce24c47f"
},
"downloads": -1,
"filename": "configurematic-0.0.1-py3-none-any.whl",
"has_sig": false,
"md5_digest": "506526fe617270d8bde85d3e8dcc5e78",
"packagetype": "bdist_wheel",
"python_version": "py3",
"requires_python": ">=3.10",
"size": 13845,
"upload_time": "2024-12-08T09:19:52",
"upload_time_iso_8601": "2024-12-08T09:19:52.135070Z",
"url": "https://files.pythonhosted.org/packages/1b/b4/c62060b7b2d38ae6dc429b72386d6dd6c0ebbeda6d29aa96508b6be4a216/configurematic-0.0.1-py3-none-any.whl",
"yanked": false,
"yanked_reason": null
},
{
"comment_text": "",
"digests": {
"blake2b_256": "582b8d351bac6c7652f68d11084474c2c2d6e503e6e557a50e0bf22f5ac0cc85",
"md5": "5d61da8f7871842867d1aa0751abee3b",
"sha256": "f1985c25f0b01cf2879ded4d89f1f12346aa0a524e31a016c9de8ece38a87f8c"
},
"downloads": -1,
"filename": "configurematic-0.0.1.tar.gz",
"has_sig": false,
"md5_digest": "5d61da8f7871842867d1aa0751abee3b",
"packagetype": "sdist",
"python_version": "source",
"requires_python": ">=3.10",
"size": 17043,
"upload_time": "2024-12-08T09:19:54",
"upload_time_iso_8601": "2024-12-08T09:19:54.127917Z",
"url": "https://files.pythonhosted.org/packages/58/2b/8d351bac6c7652f68d11084474c2c2d6e503e6e557a50e0bf22f5ac0cc85/configurematic-0.0.1.tar.gz",
"yanked": false,
"yanked_reason": null
}
],
"upload_time": "2024-12-08 09:19:54",
"github": true,
"gitlab": false,
"bitbucket": false,
"codeberg": false,
"github_user": "mbakereth",
"github_project": "configurematic",
"travis_ci": false,
"coveralls": false,
"github_actions": true,
"requirements": [
{
"name": "python-dotenv",
"specs": []
}
],
"lcname": "configurematic"
}
