Furkan Onder
@furkanonder.bsky.social
Python Triage Member | Focusing on CPython #LKD #Python #ArchLinux #Django #eBPF
https://github.com/furkanonder/
https://github.com/furkanonder/
Reposted by Furkan Onder
Just released: Python 3.14.0 release candidate 2! 🚀🐍
🪄 We fixed a bug that required the ".pyc magic number" to be increased.
🪄 The ABI isn't changing, and wheels built for rc1 should still work.
🏆 Bonus: Early Python 3.13.7!
discuss.python.org/t/python-3-1...
#Python #CPython #Python314 #release
🪄 We fixed a bug that required the ".pyc magic number" to be increased.
🪄 The ABI isn't changing, and wheels built for rc1 should still work.
🏆 Bonus: Early Python 3.13.7!
discuss.python.org/t/python-3-1...
#Python #CPython #Python314 #release
Python 3.14.0rc2 and 3.13.7 are go!
Not one but two expedited releases! 🎉 🎉 Python 3.14.0rc2 It’s the final 🪄 penultimate 🪄 3.14 release candidate! https://www.python.org/downloads/release/python-3140rc2/ Note: rc2 was originally plan...
discuss.python.org
August 14, 2025 at 7:41 PM
Just released: Python 3.14.0 release candidate 2! 🚀🐍
🪄 We fixed a bug that required the ".pyc magic number" to be increased.
🪄 The ABI isn't changing, and wheels built for rc1 should still work.
🏆 Bonus: Early Python 3.13.7!
discuss.python.org/t/python-3-1...
#Python #CPython #Python314 #release
🪄 We fixed a bug that required the ".pyc magic number" to be increased.
🪄 The ABI isn't changing, and wheels built for rc1 should still work.
🏆 Bonus: Early Python 3.13.7!
discuss.python.org/t/python-3-1...
#Python #CPython #Python314 #release
congratulations 🎉
March 31, 2025 at 11:27 AM
congratulations 🎉
Congratulations 🎉🎉
February 6, 2025 at 12:10 PM
Congratulations 🎉🎉
In addition, a simple example CLI can be written to show a lot of good practice with positional argument handling, optional arguments and so on.
There could be a bonus section on the most troublesome argparse issues and solutions in CPython :)
There could be a bonus section on the most troublesome argparse issues and solutions in CPython :)
December 31, 2024 at 5:42 AM
In addition, a simple example CLI can be written to show a lot of good practice with positional argument handling, optional arguments and so on.
There could be a bonus section on the most troublesome argparse issues and solutions in CPython :)
There could be a bonus section on the most troublesome argparse issues and solutions in CPython :)
It can be about mistakes when using argparse.
For example, an error I see very often;
parser.add_argument(“age”)
args = parser.parse_args()
the_age = int(args.age)
instead of;
parser.add_argument(“age”, type=int")
args = parser.parse_args()
the_age = args.age
For example, an error I see very often;
parser.add_argument(“age”)
args = parser.parse_args()
the_age = int(args.age)
instead of;
parser.add_argument(“age”, type=int")
args = parser.parse_args()
the_age = args.age
December 31, 2024 at 5:42 AM
It can be about mistakes when using argparse.
For example, an error I see very often;
parser.add_argument(“age”)
args = parser.parse_args()
the_age = int(args.age)
instead of;
parser.add_argument(“age”, type=int")
args = parser.parse_args()
the_age = args.age
For example, an error I see very often;
parser.add_argument(“age”)
args = parser.parse_args()
the_age = int(args.age)
instead of;
parser.add_argument(“age”, type=int")
args = parser.parse_args()
the_age = args.age