interop-cats
warehouse
Our great sponsors
interop-cats | warehouse | |
---|---|---|
5 | 274 | |
156 | 3,452 | |
0.6% | 0.7% | |
5.4 | 9.7 | |
about 1 month ago | about 20 hours ago | |
Scala | Python | |
Apache License 2.0 | Apache License 2.0 |
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.
interop-cats
-
I have decided to connect my future with Scala (if possible), need little advice
If you're using http4s, don't use ZIO. Yes, ZIO has an interop-cats module, so you can do this. But using http4s means you're working in the conceptual framework the Typelevel ecosystem is based on (and what interop-cats does can be characterized as "describe ZIO's implementation in those terms, so the Typelevel ecosystem can make heads or tails of it.") This is essentially all cost and no benefit: you can't avoid understanding the Typelevel ecosystem if you use http4s (at least, no more than you can by using cats-effect), and you don't get any of the value proposition of ZIO (interop-cats gives you Typelevel typeclass instances for the RIO type alias, which means your error channel is rooted in Throwable, and you're faced with the most complex part of the ZIO ecosystem: ZLayer, which the Typelevel ecosystem doesn't use and doesn't need). Finally the ZIO ecosystem is still quite immature, and this brings us to documentation. There is not (yet!) anything comparable to:
-
Friction-less scala - Tell us what is causing friction in your day-to-day life with Scala
These are necessarily oversimplifications. In particular, the ZIO ecosystem offers the relevant instances of cats-effect typeclasses to support use of the ZIO type in the cats-effect ecosystem.
-
Why Typelevel hates ZIO?
However, ZIO continues to offer cats-effect type classes and I certainly have no doubt cats-effect 3 continues to benefit from John's contributions. Furthermore, I likewise don't doubt the value of the ZIO ecosystem generally, and John's success in building the ZIO community speaks for itself. I personally have chosen to remain closer to the other, let's say "classical," pure FP ecosystems, partially for historical (or, if you prefer, "sunk cost") reasons, but partially because I'm satisfied the value of the Haskell/Typelevel/PureScript/fp-ts/etc. interplay warrants it.
-
Is it possible to use cats' monad transformers (OptionT, EitherT) with an effect type (F) that has >1 type parameter?
It seems that zio/interop-cats faces a similar issue.
warehouse
-
Smooth Packaging: Flowing from Source to PyPi with GitLab Pipelines
python3 -m pip install \ --trusted-host test.pypi.org --trusted-host test-files.pythonhosted.org \ --index-url https://test.pypi.org/simple/ \ --extra-index-url https://pypi.org/simple/ \ piper_whistle==$(python3 -m src.piper_whistle.version)
-
Introducing Flama for Robust Machine Learning APIs
We believe that poetry is currently the best tool for this purpose, besides of being the most popular one at the moment. This is why we will use poetry to manage the dependencies of our project throughout this series of posts. Poetry allows you to declare the libraries your project depends on, and it will manage (install/update) them for you. Poetry also allows you to package your project into a distributable format and publish it to a repository, such as PyPI. We strongly recommend you to learn more about this tool by reading the official documentation.
-
PyPI Packaging
From there, I needed to learn a bit about PyPi or Python Package Index, which is the home for all the wonderful packages that you know if you have ever run the handy pip install command. PyPi has a pretty quick and easy onboarding, which requires a secured account be created and, for the purposes of submitting packages from CLI, an API token be generated. This can be done in your PyPi profile. Once logg just navigate to https://pypi.org/manage/account/ and scroll down to the API tokens section. Click “Add Token” and follow the few steps to generate an API token which is your access point to uploading packages. With all this in place, I was able to use twine to handle the package upload. First I needed to install twine, again as simple as pip install twine. In order for twine to access my API token during the package upload process, it needed to read it from .pypirc file that contains the token info. For some that file may exist already, for me I was required to create it. Working in windows I simply used a text editor to create it in my home user directory ($HOME/.pypirc). The file contents had a TOML like format looked like this:
-
Releasing my Python Project
I have published the package to Python Package Index, commonly called PyPi, and in this post, I'll be sharing the steps I had to follow in the process.
-
Publishing my open source project to PyPI!
Register at PyPI.org
-
Show HN: I mirrored all the code from PyPI to GitHub
According to the stats on the original link, there are over 25,000 identified secret ids/keys/tokens in the data. And it looks like that's just identifiable secrets, e.g. "Google API Keys" that I'm guessing are identifiable because they have a specific pattern, and may be missing other secrets that use less recognizable patterns.
I mean, sure, compared to the 478,876 Projects claimed on https://pypi.org/, that's a pretty small minority. On the other hand, I'd guess a many Python packages don't use these particular services, or even need to connect to a remote service at all, so the area for this class of mistake should be even smaller.
And mistakes do happen, but that's a pretty big thing to miss if you are knowingly publishing your code with the expectation other people will be reading it.
-
Pezzo v0.5 - Dashboards, Caching, Python Client, and More!
PyPi package
-
PyPI Requires 2FA for New User Registrations
https://peps.python.org/pep-0458/
Here's the in-progress roadmap: https://github.com/pypi/warehouse/issues/10672
If there's particular issues you believe you could pick off to help achieve the goal, much appreciated!
-
PSF Hires PyPI Safety and Security Engineer
Having done plenty of work on PyPI, including lots of security work: Mike is an extremely competent engineer, and has been a significant force[1] in PyPI's overall modernization and maintenance efforts. That kind of work is security work, and it's frequently thankless.
[1]: https://github.com/pypi/warehouse/commits?author=miketheman
-
Exploring Django's Third-Party Packages: Top Libraries You Should Know
PyPI - Python Package Index - PyPI is the official Python Package Index, where Python packages can be found and downloaded, including Django packages.
What are some alternatives?
devpi
bandersnatch
localshop - local pypi server (custom packages and auto-mirroring of pypi)
Poe the Poet - A task runner that works well with poetry.
scribd-downloader
Python Packages Project Generator - 🚀 Your next Python package needs a bleeding-edge project structure.
devpi - Python PyPi staging server and packaging, testing, release tool
CPython - The Python programming language
registerit - Have an idea for a Python package? Register the name on PyPI 💡
awesome-python - An opinionated list of awesome Python frameworks, libraries, software and resources.
Django - The Web framework for perfectionists with deadlines.
Poetry - Python packaging and dependency management made easy