<?xml version="1.0" encoding="iso-8859-1"?>
<rss version="2.0"><channel><title>RasadaCrea rss feeds aggregator</title><link>http://www.rasadacrea.com</link><description>rss feed aggregated news on web services and technologies by RasadaCrea France</description><lastBuildDate>Fri, 21 Aug 2026 15:31:40 GMT</lastBuildDate><generator>PyRSS2Gen-1.0.0</generator><docs>http://blogs.law.harvard.edu/tech/rss</docs><item><title>DSF Membership Open Space at DjangoCon US</title><link>https://www.djangoproject.com/weblog/2026/aug/20/dsf-membership-open-space-at-djangocon-us/</link><description>If you are at DjangoCon US this year, join us for 45 minutes to talk about the Django Software Foundation. 
 
 What: Django Software Foundation Membership Open Space 
 When: Wednesday, August 26th, 1:00 pm to 1:45 pm 
 Where: Wolf Point Ballroom, voco Chicago Downtown 
 Schedule: Talks: Wednesday, Aug 26 
 
 DSF Board Directors Jeff Triplett, Abigail Afi Gbadago, and Paolo Melchiorre will be there, along with Django Fellows, Steering Council members, and other DSF members. This is an open space, not a talk. Pull up a chair and bring your questions. 
 What We Want to Talk About 
 
 Fundraising and finances. We raised our 2026 goal to $500,000. We'll cover what it funds, most of it the Django Fellows, and how we are tracking against it. If your company depends on Django, or you know one that does, ask us about corporate membership and sponsorship. 
 The Executive Director search. The DSF is hiring its first Executive Director, and applications are open through midnight Central Time on September 14, 2026. If you are thinking about applying, or know someone who should, ask us about the role. 
 Membership. How individual membership works, how people become members, and what members do. Members vote in DSF elections, and we would like more .. cntd</description><pubDate>Fri, 21 Aug 2026 02:11:52 GMT</pubDate></item><item><title>Bob Belderbos: Guardrails Protect Your Codebase. What Protects Your Judgment?</title><link>https://belderbos.dev/blog/ai-skill-atrophy-keep-the-friction/</link><description>Cal Newport's On AI Coding and Its Discontents lands on an uncomfortable point: the speed AI gives you is paid for with the thinking that made us good engineers in the first place. 
 Read code instead of writing it and you get passive recognition where you used to have an active model of the code. 
 
 The vendors sell one answer to this: more AI. The nostalgic answer is the opposite: go back to writing everything by hand. I am searching for a midway. 
 No right answer, but at least a direction to pursue 
 When I posted about this recently, I offered 3 options: write more code manually, double down on AI, or find some middle with more friction. I got some valuable comments from developers picking the middle. And that's where I've landed too. 
 The more I read and think about it, the more the middle stops looking like a compromise. It seems the way forward, but only if you specify what friction to keep. 
 Skill atrophy isn't caused by using AI per se. It's caused by delegating the part that builds your internal model. 
 I've argued that the friction is where the learning lives , and nothing about agents changes that. What changes is that it's now easier to bypass friction and it's on us to keep it in. 
 It helps to separate two problems .. cntd</description><pubDate>Tue, 18 Aug 2026 00:00:00 GMT</pubDate></item><item><title>PyCharm: We Gave AI Agents a Live Jupyter Kernel in PyCharm</title><link>https://blog.jetbrains.com/pycharm/2026/08/we-gave-ai-agents-a-live-jupyter-kernel-in-pycharm/</link><description>If you've handed notebook work to an AI agent, you know how it tends to go: More often than not, it corrupts your .ipynb, loses your trained model the moment the run finishes, or burns budget sitting idle through a long job while you watch. 
 To solve this, we're introducing a brand-new Jupyter skill. Built directly into PyCharm, it lets your AI agent work inside a live Jupyter kernel instead of handing the job to a subprocess and losing your progress. This one change means state persists across cells, the .ipynb isn't corrupted, and long jobs wait until execution is completed instead of constantly checking and wasting precious tokens. 
 
 
 
 JUPYTER SKILL FOR PYCHARM
 A live kernel made Opus
 cheaper than the shell.
 12%
 cheaper
 Claude Opus 5 across 12 ML tasks
 
 
 Kernel
 USD 59.09
 
 
 Shell
 USD 67.06
 
 12
 ML tasks
 
 98%
 cache reads
 
 
 
 State persists across cells
 
 For Opus, the kernel ran cheaper than the shell 
 We tested the efficiency of the Jupyter skill by comparing the performance of agents when solving twelve different machine learning problems. We compared three different modes: strictly using bash, strictly using the kernel via the Jupyter skill, and a mixture of both. 
 While the agent was able to solve .. cntd</description><pubDate>Wed, 12 Aug 2026 12:00:34 GMT</pubDate></item><item><title>Django Weblog: Django 6.1 released</title><link>https://www.djangoproject.com/weblog/2026/aug/05/django-61-released/</link><description>The Django team is happy to announce the release of Django 6.1. 
 The release notes 
offer a harmonious mélange of new features and usability improvements. A few highlights are: 
 
 
 Model field fetch modes for configuring on-demand fetching behavior 
 
 
 Database-level delete options for ForeignKey.on_delete 
 
 
 Dictionary-based email settings 
 
 
 You can get Django 6.1 from
 our downloads page or from
 the Python Package Index . 
 The PGP key ID used for this release is Jacob Walls: 131403F4D16D8DC7 
 With the release of Django 6.1, Django 6.0 has reached the end of mainstream support. 
The final minor bug fix release, 6.0.8 , which was also a security release, was issued yesterday, Aug. 4, 2026. Django 6.0
will receive security and data loss fixes until April 2027.
All users are encouraged to upgrade before then to continue receiving fixes for
security issues. 
 See the downloads page for a table of
supported versions and the future release schedule.</description><pubDate>Wed, 05 Aug 2026 19:30:00 GMT</pubDate></item><item><title>Mike C. Fletcher: OMI Audio extension for glTF</title><link>http://blog.vrplumber.com/b/2026/08/02/omi-audio-extension-for-gltf/</link><description>Another OMI-based extension, this time for positional audio mixing. Again, Claude-coded, using the OMI/KHR audio extensions for glTF as the base model and then implementing the actual mixing using Numpy. Supports mp3, wav, opus and flac inputs and stereo (headset) outputs. Up on github as omi_audio and on PyPI as omi_audio as well. 
 This is loosely the same model as Web Audio's Panner Node. The only significant difference from the KHR extension is that we also support VRML97 style double-ellipse emitter. The package delegates file retrieval to the application, and doesn't include any special effects or the like.</description><pubDate>Sun, 02 Aug 2026 16:06:56 GMT</pubDate></item><item><title>Django 6.1 release candidate 1 released</title><link>https://www.djangoproject.com/weblog/2026/jul/22/django-61-rc-1-released/</link><description>Django 6.1 release candidate 1 is now available. It represents
the final opportunity for you to try out the version that
 offers a harmonious mélange of new features and usability improvements ,
before Django 6.1 final is released. 
 The release candidate stage marks the string freeze and the call for translators
 to submit translations .
Provided no major bugs are discovered that can't be solved in the next two
weeks, Django 6.1 will be released on or around
August 5. Any delays will be communicated
on the Django forum . 
 Please use this opportunity to help find and fix bugs (which should be reported
to the issue tracker ), you can grab
a copy of the release candidate package from
 our downloads page or on PyPI. 
 The PGP key ID used for this release is Jacob Walls: 131403F4D16D8DC7</description><pubDate>Wed, 22 Jul 2026 20:00:00 GMT</pubDate></item><item><title>PyPy: Moving linux builds to GLIBC==2.28</title><link>https://www.pypy.org/posts/2026/07/moving-linux-builds-to-glibc228.html</link><description>A short note for visibility. 
 PyPy builds tarballs of the python interpreter ready for
download . These include the latest
releases and also nightly builds, fresh from our fleet of buildbots. Over the
next couple of days, the nightly builds on linux will transition from
 manylinux2014 based docker images to manylinux2_28 
images . The practical implication is that
nightly images, and the next releases, will require a minimum of GLIBC&amp;gt;=2.28 ,
i.e. AlmaLinux8, amanzonlinux 2023, debian 10, ubuntu 20.04. For a good
overview of how this glibc/distro/manylinux all works, see the PEP 600 compliance
page . 
 The next release will indicate this change by a new PyPy major version, 8.0.0.
It should include a Python3.12 interpreter, in which case it will be the last
release of the Python 3.11 interpreter.</description><pubDate>Sat, 18 Jul 2026 18:09:11 GMT</pubDate></item><item><title>Tryton News: Release 1.0.0 of Relatorio</title><link>https://discuss.tryton.org/t/release-1-0-0-of-relatorio/9293</link><description>We are proud to announce the release of Relatorio version 1.0.0. 
 Relatorio is a templating library for OpenDocument using also OpenDocument as source format. 
 In addition to bug-fixes, this release contains the following improvements: 
 
 Replace python-magic dependency by puremagic 
 Remove support for chart template 
 Remove support for PDF 
 
 The package is available at Client Challenge 
The documentation is available at Relatorio A templating library able to output odt files 
 1 post - 1 participant 
 Read full topic</description><pubDate>Thu, 16 Jul 2026 16:42:24 GMT</pubDate></item><item><title>Publicis relève ses prévisions annuelles de croissance grâce à l'IA</title><link>https://www.journaldunet.com/business/1552733-publicis-releve-ses-previsions-annuelles-de-croissance-organique-a-4-5-5-pour-2026-porte-par-l-ia-et-une-forte-performance-au-1er-semestre/</link><description>Le groupe français anticipe une croissance supérieure à celle de ses concurrents, confirmant sa stratégie axée sur la data, l'intelligence artificielle et les acquisitions.</description><pubDate>Thu, 16 Jul 2026 08:40:08 GMT</pubDate></item><item><title>Avec l'évolution de l'IA, l'adaptive learning peut tenir enfin ses promesses</title><link>https://www.journaldunet.com/intelligence-artificielle/1552329-avec-l-evolution-de-l-ia-l-adaptive-learning-peut-tenir-enfin-ses-promesses/</link><description>Avec l'IA générative et agentique, l'adaptive learning devient enfin concret : diagnostic, personnalisation à grande échelle et inclusion pour la réussite de tous les étudiants.</description><pubDate>Mon, 06 Jul 2026 09:38:04 GMT</pubDate></item><item><title>Pourquoi le recrutement par concours va ruiner l'administration en 2026</title><link>https://www.journaldunet.com/management/formation/1552127-pourquoi-le-recrutement-par-concours-va-ruiner-l-administration-en-2026/</link><description>Une critique pragmatique du modèle des concours administratifs. L'article démontre que les épreuves académiques actuelles ne répondent plus aux réalités du terrain. Il propose de valoriser l'intellige.</description><pubDate>Thu, 02 Jul 2026 08:55:39 GMT</pubDate></item><item><title>"La connaissance du comportement des femmes françaises par le JDF est inégalée"</title><link>https://www.journaldunet.com/publishers/1552137-le-journal-des-femmes-est-le-plus-cite-par-chatgpt-sur-30-000-requetes-dans-l-univers-semantique-d-une-grande-marque-de-beaute/</link><description>Ada Mercier, directrice du Journal de Femmes, explique comment la data du pure player nourrit le traitement éditorial pour proposer des dispositifs sur mesure aux annonceurs</description><pubDate>Wed, 01 Jul 2026 10:16:33 GMT</pubDate></item><item><title>How the Django Software Foundation Became a CNA</title><link>https://www.djangoproject.com/weblog/2026/jun/25/how-the-django-software-foundation-became-a-cna/</link><description>Why the DSF pursued CNA status 
 Django has a long history of responsible security practices: a dedicated, private security mailing list, clear advisory policies, and predictable security releases. Even so, we relied on external organizations to assign CVE IDs (Common Vulnerabilities and Exposures) . This sometimes introduced administrative delays and extra coordination overhead. 
 Becoming a CNA (CVE Numbering Authority) allows the DSF to: 
 
 Assign CVEs ourselves for vulnerabilities in Django and selected community projects. 
 Publish advisories more efficiently and in closer alignment with Django's established release workflow. 
 Maintain strong independence in how Django handles security incidents. 
 
 The initial exploration 
 The process began with internal discussions within the DSF Board and Django Security Team . We evaluated: 
 
 Whether our existing security process already met CNA expectations. 
 Whether we had the organizational stability to take on long term responsibility for CVE assignment. 
 The scope of projects we would cover. 
 How to ensure we could meet the operational requirements without overloading volunteers and Django Fellows . 
 
 After confirming that our policies were mature and that the administrative .. cntd</description><pubDate>Thu, 25 Jun 2026 11:00:00 GMT</pubDate></item><item><title>Django 6.1 beta 1 released</title><link>https://www.djangoproject.com/weblog/2026/jun/24/django-61-beta-1-released/</link><description>Django 6.1 beta 1 is now available. It represents the second
stage in the 6.1 release cycle and is an opportunity to try out
the changes coming in Django 6.1. 
 Django 6.1 offers a harmonious mélange of new features and usability improvements, which you
can read about in
 the in-development 6.1 release notes . 
 Only bugs in new features and regressions from earlier Django versions will be
fixed between now and the 6.1 final release. Translations will
be updated following the "string freeze", which occurs when the release
candidate is issued. The
 current release schedule 
calls for a release candidate in about a month, with the final release
scheduled roughly two weeks later on August 5. 
 Early and frequent testing from the community will help minimize the number of
bugs in the release. Updates on the release schedule are available
 on the Django forum . 
 As with all alpha and beta packages, this release is not for production
use. However, if you'd like to try some of the new features or help find and
fix bugs (which should be reported to
 the issue tracker ),
you can grab a copy of the beta package from
 our downloads page or on PyPI. 
 The PGP key ID used for this release is Jacob Walls: 131403F4D16D8DC7</description><pubDate>Wed, 24 Jun 2026 17:00:00 GMT</pubDate></item></channel></rss>