Well, well, well, it’s time for Python 3.13.0 alpha 2!

https://www.python.org/downloads/release/python-3130a2/

This is an early developer preview of Python 3.13

 

Major new features of the 3.13 series, compared to 3.12

 

Python 3.13 is still in development. This release, 3.13.0a2 is the second of seven planned alpha releases.

Alpha releases are intended to make it easier to test the current state of new features and bug fixes and to test the release process.

During the alpha phase, features may be added up until the start of the beta phase (2024-05-07) and, if necessary, may be modified or deleted up until the release candidate phase (2024-07-30). Please keep in mind that this is a preview release and its use is not recommended for production environments.

Many new features for Python 3.13 are still being planned and written. The most notable change so far:

• PEP 594 (Removing dead batteries from the standard library) scheduled removals of many deprecated modules: aifc, audioop, chunk, cgi, cgitb, crypt, imghdr, mailcap, msilib, nis, nntplib, ossaudiodev, pipes, sndhdr, spwd, sunau, telnetlib, uu, xdrlib, lib2to3.
• Many other removals of deprecated classes, functions and methods in various standard library modules.
• New deprecations, most of which are scheduled for removal from Python 3.15 or 3.16.
• C API removals and deprecations. (Some removals present in alpha 1 have been reverted in alpha 2, as the removals were deemed too disruptive at this time.)

(Hey, fellow core developer, if a feature you find important is missing from this list, let Thomas know.)

The next pre-release of Python 3.13 will be 3.13.0a3, currently scheduled for 2023-12-19.

 

More resources

• Online Documentation
• PEP 719, 3.13 Release Schedule
• Report bugs at https://github.com/python/cpython/issues.
• Help fund Python and its community.

 

Enjoy the new releases

Thanks to all of the many volunteers who help make Python Development
and these releases possible! Please consider supporting our efforts by
volunteering yourself or through organization contributions to the
Python Software Foundation.

Regards from lovely Czechia,

Your release team,
Thomas Wouters
Ned Deily
Steve Dower
Łukasz Langa

A (scientific) software developer position that has just opened up in CEFCA for the development of Gnuastro for the data reduction pipeline of European Space Agency (ESA’s) newly approved ARRAKIHS mission (to be launched in 2030), as well as other data from our Astronomical Observatory of Javalambre (OAJ):

https://www.cefca.es/cefca_en/reference_0119

(For 2 years, deadline: January 15th 2024)

ARRAKIHS is expected to last until ~2035 and we will be applying for future grants to keep the core pipeline team until the end of the project.

The job will be based in Teruel/Spain, which is a beautiful city (recognized as a UNESCO World heritage for its “Mudejar” architecture). Teruel just 1.5 hours from Valencia by car and with a population of 35000 people, everything is nicely within reach and you will not waste hours every day in traffic or long commutes as in large cities! Our observatory (OAJ) is also just 1.5 hours away by car (we have one of the darkest skies with fewest cloudy nights in continental Europe)!

As the ARRAKIHS pipeline engineer, the successful applicant will also be visiting other ARRAKIHS consortium members: IFCA/Santander, ESAC/Madrid; UCM/Madrid, IAA/Granada, EPFL/Switzerland, Univ. Lund/Sweden, Univ. Innsbruck/Austria.

The job will involve major developments in Gnuastro for the missing features or things that can be improved for Low Surface Brightness optimized reduction pipelines and high-level science from it (Gnuastro’s MakeCatalog for example).

Once tested in the ARRAKIHS/OAJ pipelines, all those features will be brought into the core of Gnuastro for everyone to use in any pipeline! This is thus a major development in Gnuastro’s history!

Anyone with a B.Sc degree or higher can apply! So please share this email with anyone you think may be interested. People with a M.Sc or PhD are also welcome to apply; it is “scientific”/Research software engineer position after all; and we expect to publish many papers on the algorithms/tools that we develop.

If you can’t wait to get your hands dirty, and want to improve your profile for the application, there is a nice checklist in our Google Summer of Code guidelines to help you get started and fix a bug or two until the deadline to include in the application (you have almost two months from now):

https://savannah.gnu.org/support/?110827#comment0

Please don’t hesitate to ask any questions from the contact person in the main announcement above; we’d be happy to help clarify any doubts.

Earlier this month, Microsoft released new preview updates with changes to make its operating systems compliant with European Union regulations. Those changes include the ability to uninstall Edge, decouple the OS from Bing, turn on third-party news feeds in Widgets, and more. Sadly, only EU citizens can enjoy those changes without messing with their PCs’ software intestines. Other people must tweak Windows Registry to spoof their location, which can lead to unnecessary complications. Luckily, there is a much simpler method that does not require editing the registry or faking your location. As it turned out (via Deskmodder), Windows manages new region policies using a JSON file inside the system32 folder. Modifying that file allows force-enabling specific features in unsupported regions. What follows is a 19 step process involving taking ownership of protected system files, dowloading additional tools, editing the registry, a few reboots, and more. A very simple process. So anyway if you want to remove Firefox from Fedora or Ubuntu or whatever, just run sudo dnf remove firefox or sudo apt remove firefox respectively, because as we all know, Linux is very hard to use and just not ready for desktop use. Good for servers, though. The tech world is a clown show.

#MansoorAnwar #windows10

This app can’t open using the Built-in Administrator Accounts || Mansoor Anwar || (Urdu)

Detail:

Call & SMS
+92-332-5173356

WhatsApp
https://wa.me/923325173356

===========================================================

One of the drivers taking part in the event was Jimmy Gordon of Sacramento, CA, that had won the championship at Capitol Speedway a few weeks earlier. Gordon usually drove a pearl color, number 1 Roddy-Quipped super modified, but that day he was driving the Don Edmunds Research Chevy V8 copper-brownish sprint car number 96. This was Gordon’s second outing on a sprint car, a week earlier he had finished second in a race in Phoenix.

Gordon started the race from the eighth place on the grid. On the thirty-fifth lap of the main event, he locked wheels with Bud Gilbert of Santa Ana, CA, as the two went into Turn 3. Gordon’s vehicle cartwheeled and, in a facsimile of Purssell’s accident of a few hours before, landed upside and was hit by another competitor – as Ron Rea of Sepulveda, CA, could not avoid crashing against the Gordon’s wreckage. The impact ripped out the fuel tank of Gordon’s car and flames spread across the track. Officials moved quickly to put out the fire, but Gordon’s roll cage had collapsed, causing the driver fatal injuries. Gordon was pronounced dead at the hospital. Ron Rea was able to walk away before the fire erupted.

Promoter J. C. Agajanian told the California Racing Association members on hand that he was ending the race at that point, and not a single voice of dissent was heard. Having lost Purssell, Reiff and Gordon racing had become a futile exercise. Jerry Blundy, who was leading the race, was declared the winner and registered his third straight victory at the 100-mile championship.

It is also of interest that one racing report indicated Gordon’s car had a chromed roll cage. It wasn’t too much later that chromed roll cages were banned as it was discovered the chroming process weakened the integrity of the cages.

The race was also marred by the death of Ernie Purssell and spectator Walt Reiff.

R.I.P

La vase concentre toutes les briques nécessaires à la construction de la vie. Les premières étapes de la création de la matière vivante s’y déroulent en toute discrétion.