One more FreeBSD centric update for the road, you can now explicitly synchronize pkg repositories, provided you configure sudo policies for it.
https://github.com/mrdaemon/exosphere/releases/tag/v1.3.4
#exosphere #FreeBSD #HomeLab #Python #linux
If there's never any reason to have two instances of your class, you might consider not making a class at all and instead just use the global state within your module.
Read more 👉 https://trey.io/RAvlR1
Ever wonder why Python is called 'Python'? 🐍 It's not because of snakes! Guido van Rossum, its creator, was a big fan of 'Monty Python\'s Flying Circus'. So, next time you're coding, think of absurd British comedy. What's your favorite programming language origin story? #Python #Programming #CodingFacts #DidYouKnow
The minimal setup for codiung #python on #vim with auto complete, help, syntax check.
vim -u <(cat << 'EOF'
let mapleader=' '|set nu rnu bs=2 ts=4 sw=4 et ai si nocp wmnu tw=79 cc=80 stal=2 cot=menuone,longest,preview ph=10
let g:p=executable('uv')?'uv run python3':'python3'|let g:d=g:p.' -m pydoc'|let g:c=g:p.' -m py_compile'
filetype plugin indent on|sy on|nn <leader>b :ls<cr>:b<space>|nn <leader><Tab> <C-^>
au FileType python setl ofu=python3complete#Complete cot=menuone,longest,preview inc=^\s*\(from\|import\) def=^\s*\(def\|class\)|exe 'setl kp='.escape(g:d,' ')|nn <buffer> <leader>k :exe 'vert term ++close '.g:d.' '.expand('<cWORD>')<CR>|nn <buffer> <leader>r :w<CR>:exe '!'.g:p.' %'<CR>
au BufWritePost *.py silent! exe '!'.g:c.' %'
au CompleteDone * pc
EOF
) file.py
I never knew it was possible to have such config on only 6 lines of code.
https://gist.github.com/rochacbruno/88d7b7b02a16c6971c4bbdda7023f3a1
let mapleader=' '|set nu rnu bs=2 ts=4 sw=4 et ai si nocp wmnu tw=79 cc=80 stal=2 cot=menuone,longest,preview ph=10
let g:p=executable('uv')?'uv run python3':'python3'|let g:d=g:p.' -m pydoc'|let g:c=g:p.' -m py_compile'
filetype plugin indent on|sy on|nn <leader>b :ls<cr>:b<space>|nn <leader><Tab> <C-^>
au FileType python setl ofu=python3complete#Complete cot=menuone,longest,preview inc=^\s*\(from\|import\) def=^\s*\(def\|class\)|exe 'setl kp='.escape(g:d,' ')|nn <buffer> <leader>k :exe 'vert term ++close '.g:d.' '.expand('<cword>')<CR>|nn <buffer> <leader>r :w<CR>:exe '!'.g:p.' %'<CR>
au BufWritePost *.py silent! exe '!'.g:c.' %'
au CompleteDone * pc
Getting Started With Open Source Through Community Events
In July, I joined Raffaella Suardini and Sage Abdullah for the Djangonaut Space Space Reviewers Episode 6, where we reviewed a Django PR during a live stream. This was a fun event. I won’t get into the technical aspects of the review, and I won’t point out the many mistakes I made. Instead, I want to revisit several “getting started with open source” community events and reflect on my personal growth since I first got involved with open source.
I hope this encourages others to attend those events and similarly get involved!
Tutorial office hours 🕐
My first open source contribution happened accidentally during DjangoCon US 2023. I volunteered to host office hours to help tutorial attendees set up their development environments. I went through the tutorial projects, found a missing dependency in one of them, and reported it on the conference chat. A conference organizer, Tim Schilling, responded and suggested that I open a pull request (PR) to the project. I remember thinking to myself, “Really? I can do that?”.
Sprints 🏃
During the Sprint Days of the conference, I participated and opened two PRs to address accessibility issues. I didn’t know much about accessibility at that point, and I would not have known how to navigate the contribution process and pick out issues on my own. Thankfully, the project leaders were there to guide new contributors, and I was able to gain hands-on experience with these first few PRs.
Testathons 🧪
There was another event that took place during the Sprint Days called Testathon. I had heard of hackathons before, but I had not heard of testathons. I attended and found out they were like live stream coding or group pair programming. One person shared their screen and the group chimed in on strategies. The purpose of the testathon was to show people how to test open source projects against Django’s beta release. The code driver (or anyone else in the group) would point out what files to look for, how to run tests, and how to open PRs. Every project is slightly different, from project setup to contributing etiquette, and I learned several different things from attending 2 testathons. I loved the interactive and intimate nature of the event. It exposed me to another aspect of open source projects and contributions. I also thought it was very brave of people to share their screens and work through code together in a group. My brain would have short circuited if I were put on the spot like that!
—
From DjangoCon US 2023, I participated in 3 different types of events where I got hands-on experience with open source contributions, and I wanted more! I was curious about the live stream coding and group pair programming opportunities, too. This was definitely outside of my comfort zone, and I wanted to know how I could overcome my own inhibitions and participate more actively. I wanted to be able to jump into events so nonchalantly as everyone else seemed to do. (Of course, that’s the perception. Now, I know that most people feel some level of nervousness or anxiety when they are hosting or attending such events, and that’s absolutely normal.)
Djangonaut Space 🚀
When the Djangonaut Space program was announced, I jumped at the opportunity. I applied and was accepted for the first session, which took place from mid-January to early March of 2024. With the guidance of the Navigator and Captain on my team, I learned to sift through the Django’s Trac ticket management system, pick out a ticket, and I also faced my fear of posting comments publicly. The PR was merged, and it was thrilling to see my GitHub username in the history of the Django code base.
In March 2024, when the first Djangonaut Space session came to a close, Tim, a program organizer, asked if anyone was interested in hosting a “Getting Started With Contributing” event. I expressed my interest, and Tim suggested a ticket to work on. Unfortunately, I didn’t follow through. How could I host a “Getting Started With Contributing” event? First, I wasn’t sure if I even knew how to get started. Second, I wasn’t ready to lead an event and the discussions while simultaneously sharing my screen and thinking out loud. Finally, I wasn’t ready to be on camera in the public eye. Even though I had just finished the Djangonaut Space program, I hadn’t overcome my own inhibitions. I didn’t ask for guidance, and the event never materialized.
Space Reviewers 👾
About 8 months later in November 2024, Space Reviewers launched its very first episode. I thought it was such a creative format. I wanted to be a part of it. By this time, I was getting a lot of training with event organizing through my role as the Session Organizer for Djangonaut Space, but I wasn’t sure how to ask about joining the Space Reviewers crew, and maybe it was too early in the formation of the group to bring on another member.
It wasn’t until June 2025 that I finally asked if I could help out with Space Reviewers. The crew welcomed me as a new member. I started out by making a pre-recorded video, a PR Review Deep Dive, that was uploaded to the Djangonaut Space YouTube channel. I had a lot of fun recording and editing the video.
A month later, in July 2025, the crew members planned for the next episode. Raffaella scheduled time for the event and created the show notes, and I was taking on Tim’s role as a co-organizer. Because I would be managing the video stream and sharing my screen, I realized that I could be the single point of failure during the event. There was no safety element that a pre-recorded video offers. If my internet went down, or if my computer crashed, or if I stupidly clicked the wrong button, the live stream could come to a halt. It was a terrifying thought, but I took on the risks and pushed forward.
On the day of the event, there was a delay to the start time and some fumbles on my end, but overall, it was very fun and productive. People joined and shared their tips and tricks in the live chat. By the end, we were able to walk through the review process and post our comments on the PR. Looking back, I think making the pre-recorded video was a great stepping stone towards hosting the live stream.
I’m so glad I had the opportunity to work with Raffaella and Sage as part of Space Reviewers. They have a lot of insights and perspectives that I didn’t have. I had a lot of fun taking on the new challenges that came with organizing this event. Initially, I struggled internally as I tried to face some of my fears. There were moments leading up to the event where I thought to myself, “Why did I volunteer to do this???” In the end, I’m glad I did.
Personal growth 🌱
Some of the challenges I overcame might not seem like a big deal, but when I compare myself to where I was at the beginning of DjangoCon US 2023, I can see my personal growth quite prominently. Now, I know how to get started with contributing, and I am able to walk people through the process. I am also a lot more comfortable taking ownership of organizing and leading events. (I remember a time when I constantly needed to ask for permission or confirmation before executing an action.) I can brush off the fumbles I make as the camera is rolling, and I can continue on with the discussion.
When I revisit the community events that I have participated in over the past 2 years, from Space Reviewers, to Sprints, to Testathons, to Tutorial office hours, I realize how far I have come. I am also reminded of what it was like to be absolutely new to open source and to the community. Although I still feel somewhat new, I’m not a deer in headlights anymore. I’m still trying to find my place in open source, and the best way to do that is to continue showing up and continue helping out. One small PR at a time, one small review at a time. One little blog, one little video…
Let’s Get Started! 🌟
If you’re looking to contribute to open source, check out the upcoming events and programs.
- Djangonaut Space Session 5 - An 8-week, semi-structured mentorship program and community. Applications are open now until Sep 14th.
- Django on the Med - 3 days of Sprints to work on Django, taking place 7th-9th Oct 2025, in Palafrugell Spain.
- DjangoCon US 2025 - 3 days of talks and 2 days of Sprints, from 8th-12th Sep 2025, in Chicago, IL, USA.
- Django Girls+ - One-day programming workshops, for women and underrepresented persons. Check out the 26 upcoming events hosted all around the world.
It doesn’t matter if you’ve been making software for 20 years or 20 days, there are many events to help you get started with open source, and many more reasons to stick around.
Thank you to Lilian for proposing this guest post on the Django blog! Lilian was our DSF Member of the Month in August 2025. You can learn more about her at ontowhee.com and follow her writing at buttondown.com/ontowhee.
https://www.djangoproject.com/weblog/2025/sep/08/getting-started-with-open-source-through-community/
New article on the many keyboard shortcuts that the new Python REPL supports.
Alt+Enter will run the current code block.
Ctrl+K deletes text to the end of the line.
Ctrl+U deletes text to the start of the line.
Ctrl+R searches history.
Ctrl+L clears the screen.
https://pym.dev/repl-features/
Fucking #venv, one of the main issues of #python venv is that it doesn't use statically linked versions of python.
"octoprint.service failed to start (...) /opt/octoprint-venv/bin/python: error while loading shared libraries: libpython3.12.so.1.0: cannot open shared object file: (...)"
Python since installing it updated to 3.13.7 on my system....
I really enjoyed the Python documentary. It's well done and I hope for more of this self-preservation of open source culture.
I particularly liked the emphasis on the Python community and how it actively reached out to be more inclusive and is all the better for it. Other projects could learn from that.
It was also reflective on topics such as things that they got wrong, how the community should make decisions without a BDFL, etc.
Highly recommend:
https://youtu.be/GfH4QL4VqJ0?si=9a02Uqi7W0ACqAQv
WebP: Идеальный хамелеон? Разбор формата и LSB-стеганография в режиме Lossless
Всем привет! Мы продолжаем наш цикл статей, посвященный практической стеганографии в самых, казалось бы, обыденных файлах. Мы уже научились прятать данные в «слепых зонах» документов MS Office, внедрять «файлы-призраки» в EPUB и даже создавать скрытые каналы данных внутри PDF. В комментариях к прошлым материалам наши читатели справедливо заметили: « А что насчет WebP? ».
https://habr.com/ru/articles/945136/
#python #webp #стеганография #стегоанализ #chameleonlab #steganography #steghide #stegdetect #stego
Ataque ‘GhostAction’ no GitHub rouba mais de 3.300 segredos de programação
🔗 https://tugatech.com.pt/t71541-ataque-ghostaction-no-github-rouba-mais-de-3-300-segredos-de-programacao
#alcance #API #ataque #aws #cloudflare #detetado #Github #Go #javascript #malware #npm #programação #python #rust #segurança #servidor #software
🌘 為 R 和 Python 設定本地大型語言模型
➤ 善用 Posit 生態系，打造本地 LLM 資料科學工作流程
✤ https://posit.co/blog/setting-up-local-llms-for-r-and-python/
這篇文章介紹瞭如何在 R 和 Python 的資料科學工作流程中整合本地大型語言模型（LLM）。文中強調了 Posit 產品 suites 如何支援開源工具，並提及了 Posit Connect、Posit Workbench 和 Posit Package Manager 等產品，這些產品能協助使用者集中管理、安全分發和部署機器學習模型。雖然文章主要聚焦於 Posit 的產品生態系，但它點出透過 Posit 提供的工具，資料科學家能更有效地利用本地 LLM，同時維持對環境的安全與控制。
+ 這篇文章提供了一個很好的起點，讓我們瞭解如何在 Posit 的環境下整合本地 LLM。我特別感興趣的是 Posit Workbench 如何管理 Jupyter 和 RStudio 環境。
#大型語言模型 #R #Python #Posit #資料科學
Ich arbeite inzwischen vier Monate bei pretix. Davon habe ich mir knapp einen Monat Urlaub genommen (offene Urlaubsregelung funktioniert). Ich habe schon einige Fehler gemacht und wurde nie dafür verurteilt, sondern bekam Unterstützung beim Lernen und Wiederhinbiegen. Das tut gut.
Derzeit wird eine Person gesucht, die gerne mit #Python und #Django arbeitet. Bewerbt euch: https://pretix.eu/about/de/job/webdev