@jupyter.org Security workshop on March 31st (TDOV) in Berkeley with @ucbids.bsky.social events.linuxfoundation.org/security-too... #jupyterworkshops #jupyter
@jupyter.org Security workshop on March 31st (TDOV) in Berkeley with @ucbids.bsky.social events.linuxfoundation.org/security-too... #jupyterworkshops #jupyter
>>> ast.Constant('a').n
DeprecationWarning: Attribute n is deprecated and will be removed in Python 3.14; use value instead.
Since when can I use `.value` ? Or should I have a conditional depending on version?
How long does it takes you, and multiply this by dozen of warnings.
And it's a UI problem, because almost none of the libraries says since when replacement are available dev glance over DeprecationWarnings, thinking "I don't want to spend 1/2h diving into release notes of git blame". Example
Well, but that's a generic comment for deprecation warnings. And I don't have the full APIs of all libraries when I fix things. X added; it's bad; add Y; deprecated X; "please use Y". I don't want to go spelunk to know since when I can use Y. "Use Y that was always available" is better.
Suggestion: I see in the the PR you link to that it list when the removal will be; but I almost only care about since when the replacement is available. if > my_min_version, I can update my code; if not, I need a conditional When it will be removed is not useful for me except putting pressure.
group of about 50 people pose for the camera in a large room, with the JupyterCon logo on the side of the photo
So much activity at #JupyterCon 2025 -> tutorials 🧠, meetups 🤝, talks 🎤! Thankfully, Silas Santini captured some highlights and shared some valuable resources!
Read "Themes of Day 1, JupyterCon 2025: Collaboration and Modularity" for details:
bids.berkeley.edu/news/themes-...
Wow, it looks like deepnote does not understand that Jupyter is several repo and have many maintainers. It looks like they confuse "commits in one repo of one dev taking 6 month off" with "The full project has no-one working on it".
🔥 Meet our Keynote Speakers for #SciPy2025!
Hon. Dr. Kathryn D. Huff 🇺🇸, nuclear engineer, policy leader, and former Assistant Secretary for the Office of Nuclear Energy will be joining us in Tacoma! 🙌
Don't miss her talk, grab your ticket now: hubs.la/Q03sdlsb0
those are two uppercase i.
Damned IIm
keming crimes ?
Use #Python at all? I would like to do a silly thing, which I hope will bring amusement to others as well as me (if it works out).
If you wouldn't mind, please fill out this form, and boost for reach:
docs.google.com/forms/d/e/1F...
In a parallel world, "Python Community" is an "American Drama" on "LetFlix". ... "Last episode in python community: Pep 741 has been delayed due to Guido concern, Will the unexpected alliance of Brett and Carol be enough to convince the Former BDFL?"
I guess drama might be a strong word. I always knew there were issues and disagreements, but I felt the community is always forging ahead in the same direction.
Is that the recent layoffs? did I miss some things ?
I'm also going to clarify that moving this is a _recognition_ of spyder maintainers work who have been doing most of the maintenance and features for years, that we 100% trust them, and want to give them more freedom to push it in the direction they wish.
BREAKING: Pink smoke emerges from the chimney at the Vatican, indicating that the new Pope will be a girl
I'm guessing you could also ask @jupyter.org, but i'm not sure it is monitored, nor who controls it...
No, but as far as I can tell nobody has the bandwidth to work on it. See github.com/jupyterlab/j... For why it's a lot more work than expected
We have a website version of the Project 2025 tracker now
(Big thanks to u/mollynaquafina)
project2025-tracker.vercel.app
🙌 The right community makes all the difference in #OpenSource! Hear Pavithra Eswaramoorthy, our Developer Advocate, share her experience working with bokeh, Nebari, and other #PyData projects at pyOpenSci's community call on May 5. 🔥 Register now: www.pyopensci.org/events/pyope... #QuansightTeam
🙌 We're thrilled to be a Silver Sponsor of PyCon Greece 2025! At Quansight, we're committed to supporting the Python community and open source projects that power data science innovation. Looking forward to seeing the amazing talks and connections made at this event! #PyConGreece2025 #OpenSource
Same for me, bluesky is limited, and I have other reasons not to come this year, but for the foreseeable future, US conferences/travel for me is a No. I know conference planning is a multi-year process though, ant that it can be out of your control.
Unfortunately – I know you understand – currently, many cannot take the risk of travelling to the US for their safety, refuse to do so in solidarity. Hopping next year may be in a suitable country.
Is there by any chance a way to told the organisers: I would have come, but it's in the US ?
A young Indian male wearing a green shirt and beige pants is standing in front of a podium and speaking with a hands-free mic.
A colourful conference badge is placed on the keyboard of a laptop.
I had a great time speaking on @zarr.dev at @pyconde.bsky.social. 🚀
It was great to see the increased adoption of the project across various domains.
Huge thanks to the organisers, maintainers, attendees, and everyone involved! 💙
PhD Timeline xkcd.com/3081
Due to maintenance, Research.gov (including access to NSF-PAR, GRFP, PES, and ETAP) will be unavailable from Fri., 4/25 at 10:00 PM ET to Sat., 4/26 at 1:00 PM ET. NSF apologizes for any inconvenience.
🚨 Practical URGENT tip for NSF grantees:
Out of an abundance of caution, I would right now go into Research.gov and…
1. Download your NSF award letters.
2. Print PDF your annual reports.
3. Screenshot the status table for annual reports.
NSF is planning maintenance tomorrow to Research.gov
URGENT ACTION FOR NSF GRANTEES.
For current & recent (since 2020) awards, archive your award history this afternoon/tonight. Screenshot/download/print your work in research.gov & alert your partners.
We have credible threats to integrity of awards tracking systems (via @jeremymberg.bsky.social)
There is a bash kernel for jupyter, but i'm looking fwd to try this. (big cli fan already)
A lot of my infra workflows live in Slack threads, docs, or buried in shell history. That sucked.
I've been building Atuin Desktop. Local-first, CRDT-powered, executable runbooks - with integrated terminals, sql queries + monitoring
blog.atuin.sh/atuin-deskto...
Lmk if you have any questions <3