On Wed, Jun 11, 2025 at 9:47 AM Karolina Surma via python-devel
wrote:
> ## How to run things locally?
>
> You can use mock. Make sure to:
> 1. Clear all caches first: $ mock -r fedora-rawhide-x86_64--scrub=all
> 2. Use the Koji repo: $ mock -r fedora-rawhide-x86_64
> --enablerepo=loca
On Wed, Apr 17, 2024 at 2:38 PM Miro Hrončok wrote:
> Victor, do you think it would be possible to build in the JIT support but have
> a runtime opt-out/opt-in switch? That way, we can build it, but disable it by
> default, unless our users want to experiment with it.
PEP 744 "JIT Compilation" in
On Wed, Apr 10, 2024 at 8:23 PM Miro Hrončok wrote:
> Python 3.13 has an experimental JIT compiler:
> https://docs.python.org/dev/whatsnew/3.13.html#experimental-jit-compiler
>
> Enabling it is a configure (hence build-time) option.
>
> How do we handle this in Fedora?
>
> - We can keep it disable
Hi,
On Tue, Oct 18, 2022 at 11:34 AM Miro Hrončok wrote:
> The Python standard library distutils module will be removed from Python 3.12+
> https://peps.python.org/pep-0632/
It's done:
https://github.com/python/cpython/commit/0faa0ba240e815614e5a2900e48007acac41b214
I created a discussion to co
Which kind of computers and hardware use 32-bit ARM these days?
Raspberry Pi Zero 2 (2021), Raspberry Pi 3 (2018), Raspberry Pi 4
(2019) use 64-bit ARM, whereas older Raspberry Pi 1 (2012), Raspberry
Pi 2 (2015) and Raspberry Pi Zero (2015) use 32-bit ARM.
Victor
On Thu, Oct 13, 2022 at 11:08 AM
Hi,
Some background on pathfix.py. On Fedora, pathfix.py is available as
/usr/bin/pathfix.py but also /usr/bin/pathfixX.Y.py where X.Y is the
Python version (ex: pathfix3.10.py). So it's an executable program
(implemented in Python).
Yep, I just removed pathfix.py from Python 3.12, as part of the
That's great! It makes Python 3.11 usable in more cases.
Victor
On Tue, May 3, 2022 at 7:19 PM Miro Hrončok wrote:
>
> On 16. 03. 22 17:12, Tomáš Orsava wrote:
> > Hi Python-devel,
> > we are considering splitting the alternative Python versions from a
> > single-package format (e.g. python3.11)
Thanks, I reported the issue to PyPy:
https://foss.heptapod.net/pypy/pypy/-/issues/3702
Victor
On Mon, Mar 7, 2022 at 1:26 PM Miro Hrončok wrote:
>
> On 07. 03. 22 10:51, Victor Stinner wrote:
> > How can someone reproduce the issue? I was asked by a developer
> > running U
How can someone reproduce the issue? I was asked by a developer
running Ubuntu. Is there an easy way to:
(*) Get Fedora 36
(*) Build PyPy 2.7 for 32-bit: can it be done on x86-64? What is the
command line for that?
Victor
___
python-devel mailing list -
Congrats, that's amazing! :-) Let's fix remaining broken packages!
Victor
On Sun, Jun 13, 2021 at 9:52 PM Miro Hrončok wrote:
>
> On 08. 06. 21 1:01, Miro Hrončok wrote:
> > On 02. 06. 21 10:02, Tomas Hrnciar wrote:
> >> Hello, in order to deliver Python 3.10, we are running a coordinated
> >>
Congratulations, this change impacted tons of packages! That's also a
nice step towards more explicit build dependencies. I understood that
it's also the purpose of the pyproject.toml file ;-)
Victor
On Mon, Apr 19, 2021 at 2:39 PM Tomas Hrnciar wrote:
>
> Hello everyone,
>
> we successfully pus
Wow, impressive list of enhancements, that's really great! I didn't
realized that so many things were done only in 2020!
Fedora is and remains my favorite OS to develop on Python!
Victor
On Thu, Jan 21, 2021 at 4:38 PM Miro Hrončok wrote:
>
> Inspired by a similar report from the Copr team, I’v
On Mon, Dec 14, 2020 at 4:20 PM Jeff Law wrote:
> I would expect it'll be in Jakub's next Fedora GCC build. He's on PTO
> right now, but I wouldn't be surprised if he spins up a build between
> now and Christmas to pick up this (and other) fixes.
Ok, fine, IMO it can wait for a few days, it does
On Mon, Dec 7, 2020 at 4:08 PM Victor Stinner wrote:
> Oh, GCC 11 already landed on the Fedora Python buildbots running
> Rawhide. I created an issue to track the bugs on Python upstream:
>
> test_buffer fails on Python built with GCC 11
> https://bugs.python.org/issue42587
I bi
Oh, GCC 11 already landed on the Fedora Python buildbots running
Rawhide. I created an issue to track the bugs on Python upstream:
test_buffer fails on Python built with GCC 11
https://bugs.python.org/issue42587
Victor
On Mon, Dec 7, 2020 at 1:26 PM Miro Hrončok wrote:
>
> Hello.
>
> I've been
Hi José,
On Fri, Dec 4, 2020 at 1:17 PM José Abílio Matos wrote:
> Probably the build was erased, another place where it can be found is:
> https://copr-be.cloud.fedoraproject.org/results/nonamedotc/nbconvert-6.0.7/fedora-rawhide-x86_64/01795144-python-nbconvert/
I cannot find "xelatex" nor "OSE
I replied on the issue.
Victor
On Fri, Oct 23, 2020 at 3:11 AM Orion Poplawski wrote:
>
> I've attempted to update python-pyface to 7.1.0 in Rawhide, however a
> test is segfaulting. I've reported upstream here:
>
> https://github.com/enthought/pyface/issues/784
>
> but perhaps someone with kno
That's great, thanks!
Victor
On Wed, Aug 5, 2020 at 1:21 AM Miro Hrončok wrote:
>
> Hey Pythonistas,
>
> I've just retired Python 2.6 and Python 3.4 from rawhide (Fedora 33+).
>
> - https://fedoraproject.org/wiki/Changes/RetirePython26
> - https://fedoraproject.org/wiki/Changes/RetirePython3
Hi,
There are currently 4 issues which prevent to build the Python package
on Fedora Rawhide: Python 3.8.1 and Python 3.9.0a3 packages are
impacted, at least.
My Python 3.9.0a3 PR:
https://src.fedoraproject.org/rpms/python39/pull-request/16
Example of Python 3.8.1 PR with failing tests:
https://
> Solution 4: ZIP the entire standard library
> (...)
> Nevertheless, this might (in theory) **save 17.8 MiB / 47 %**.
It's my favorite option. Almost 50% smaller is quite good! It would be
very efficient to have such disk space gain!
Using a ZIP file for the stdlib is commonly suggested solution
Hi,
I'm not used to poetry yet. Is it a flaw in poetry to skip
documentation and tests by default? On my personal projects, I'm
trying to ensure that the sdist contains all files of the Git
repository using MANIFEST.in.
I agree with Miro that it's better to collaborate with upstream to
ensure tha
Hi,
It sounds like an issue in SWIG which access directly the
PyInterpreterState structure which became opaque in Python 3.8.
SWIG should use PyImport_GetModuleDict() public function instead, to
access PyImport_GetModuleDict(). In short, it returns interp->modules.
Victor
Le mar. 24 sept. 2019
Hi,
I saw many changes related to pyc last week, so I had a look. I don't
understand well these issues. Here are my notes to try to understand the
context ;-) I don't request any change, I'm fine with the latest choices
made in Fedora.
--
There are different issues:
(1) Performance regre
23 matches
Mail list logo
