@m2jr Would friendly view/suggest/diff/approve/comment functionality for the Markdown files in git work for you? Google Docs/Notion UI/UX backed directly by GitHub and GitHub PRs, to keep non-technical and technical people sync.
Check out Arthur Pastel's talk at #EuroPython2023, in their words: We'll cover the basics of Rust and demonstrate how to create a Rust module that can be imported and used within Python 🐍
https://t.co/bIpbmlHasa
Lots of people have been asking for my thoughts on Generative Pre-trained Transformer (GPT) models. I have now written them down. https://t.co/zUcHB5hJPC
@joegaudet Not sure about contexts. But I'm pretty sure insted of unittest you should use pytest which gives you the option to use pytest-bdd, besides other advantages.
The reality of automated testing is often hard and messy, but it is a great and beautiful concept. I'm looking forward to what the future will bring :).
will polish and publish soon! (for #pytest assertions)
>>> pat = RegexEqual('^foo')
>>> pat == 'fork'
False
>>> pat
RegexEqual(...)
# pattern = regex.Regex('^foo', flags=regex.V0)
# regex failed to match at:
#> fork
#> ^
Clear thoughts about CI/trunk based development: https://t.co/lG3xz6SEwB I especially liked https://t.co/zNdTULuptQ . It essentially argues doing pair programming and committing to master is superior to branching and code reviews.
If you are like me and never had time to check out what Anaconda is about, I recommend this (9 monhts old) episode . It's actually cooler than I would expect. https://t.co/r6rqAIPtie
My colleague reported that but I think the issue he mentions is a duplicate and goes quite far analyzing it and even offering workaround https://t.co/PTh9vnl4tt Did you see, it? Does it seem correct to you?
Unfortunately @PyCharm 2019 has problems running #pytest's own test suite, so I'm stuck on 2018 for now. 😰
https://t.co/IdpmxNLZM0
Please help to bring awareness to the issue by voting on it if you can. 🙏
(This is only for pytest's own suite, running pytest tests works fine)
CI is usually not the practice "of merging all developers' working copies to a shared mainline several times a day." but "in which frequent, isolated changes are immediately tested and reported on when they are added to a larger code base" Maybe a new term would be helpful.