roadmap
cf2tf
| roadmap | cf2tf | |
|---|---|---|
| 4 | 6 | |
| 2 | 434 | |
| - | 5.1% | |
| 1.8 | 8.7 | |
| over 2 years ago | 7 days ago | |
| Python | ||
| - | GNU General Public License v3.0 only |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
roadmap
-
Python Packaging, One Year Later: A Look Back at 2023 in Python Packaging
I wish Poetry were PEP-621 compliant though. [1]
Currently, it uses a proprietary configuration group (or "tool section", as they seem to call it in `pyproject.toml` speech).
[1]: https://github.com/python-poetry/roadmap/issues/3
-
How to improve Python packaging, or why 14 tools are at least 12 too many
https://github.com/python-poetry/roadmap/issues/3
-
What are people using to organize virtual environments these days?
Sorry for the late reply. I cannot recall the exact source, but I found this issue in the poetry repo: https://github.com/python-poetry/roadmap/issues/3. IIUC, they are trying to make poetry compliant with PEP621 but the PR was not merged yet? Will update the original comment to add this nuance.
-
How to create a Python package in 2022
I believe that Poetry does conform to PEP 518 (i.e. it specifies `[build-system]requires`), but not to the `dependencies` part of PEP 621 [1]. There are plans for this in the future though [2].
[1] https://peps.python.org/pep-0621/
[2] https://github.com/python-poetry/roadmap/issues/3
cf2tf
-
Ubuntu Desktop 24.04 LTS: Noble Numbat
The container image for 24.04 is different from that of 22.04 and 20.04. The 24.04 container includes a "ubuntu" user with a UID of 1000, where the previous containers shipped with only a "root" user. The "ubuntu" user does not have sudo turned on by default.
This gave me issues with my vscode devcontainer setup. You can see my work around here https://github.com/DontShaveTheYak/cf2tf/pull/288/files
-
How do I convert my CloudFormation template into a Terraform file?
Not really just because there are basic limitations with certain resources mappings. You might be able to knock out reasonable chunks of busy work with something like this https://github.com/DontShaveTheYak/cf2tf
-
How to create a Python package in 2022
You can take this a step further and completely automate the release of your package. That means the tagging the publishing and the GitHub release notes.
I don't have a blog post but you can see the process on my personal project https://github.com/DontShaveTheYak/cf2tf
Check out the merged PR's and the GitHub actions.
I even do alpha releases to test pypi.
- cf2tf: A tool to automatically convert Cloudformation templates to Terraform
-
Gitflow users – What's your process for merging between develop/release/main?
I have automated this completely in several of my projects but I dont use `release` branches. Here is an example https://github.com/DontShaveTheYak/cf2tf
- Show HN: Convert Cloudformation Templates to Terraform
What are some alternatives?
tox-poetry-installer - A plugin for Tox that lets you install test environment dependencies from the Poetry lockfile
cloud-radar - Create Functional and Unit tests for Cloudformation Stacks.
sigstore-python - A Sigstore client for Python
awesome-devops - A curated list of awesome DevOps platforms, tools, practices and resources
publishing-python-packages - Examples and exercises for Publishing Python Packages from Manning Books 🐍 📦 ⬆️
Nuitka - Nuitka is a Python compiler written in Python. It's fully compatible with Python 2.6, 2.7, 3.4, 3.5, 3.6, 3.7, 3.8, 3.9, 3.10, and 3.11. You feed it your Python app, it does a lot of clever things, and spits out an executable or extension module.
pigar - :coffee: A tool to generate requirements.txt for Python project, and more than that. (IT IS NOT A PACKAGE MANAGEMENT TOOL)