-crypto with python-cryptodome is the way forward.
[1]
https://lists.fedoraproject.org/archives/list/de...@lists.fedoraproject.org/message/VYJ7CIR7GMLUNNXYYZAIIMG3POBIVQCB/
-- Sandro
--
___
python-devel mailing list -- python-devel@lists.fedoraproject.org
ytest 8 [2], which no longer supports
running nose tests, it kind of makes sense to drop both packages
simultaneously.
[1] https://docs.pytest.org/en/7.4.x/how-to/nose.html
[2] https://fedoraproject.org/wiki/Changes/Pytest_8
-- Sandro
--
___
python-
re multiple wheels
installed this way? etc.
It's weird in that %{pyproject_files} is explicitly tied to the use of
%pyproject_save_files in the documentation.
-- Sandro
--
___
python-devel mailing list -- python-devel@lists.
le-qcas"
I believe `-C--enable-qcas` is waht you are looking for. It's explained
in the pyproject-rpm-macros README, which is what you see when visiting
https://src.fedoraproject.org/rpms/pyproject-rpm-macros (search for /
scroll down to "Passing config settin
On 25-04-2024 15:15, Sandro wrote:
On 11-04-2024 13:54, Miro Hrončok wrote:
On 11. 04. 24 11:55, Sandro wrote:
While I ponder those thoughts some more, moving forward in either
direction, the next step would be writing a change proposal?
I'd start by:
Packaging pynose without hacks
about new packages? Can those be added to rawhide and will they be
picked up for the rebuild? Or is it better to wait and submit them after
the side tag has been merged?
-- Sandro
--
___
python-devel mailing list -- python-devel@lists.fedoraproj
On 11-04-2024 13:54, Miro Hrončok wrote:
On 11. 04. 24 11:55, Sandro wrote:
While I ponder those thoughts some more, moving forward in either
direction, the next step would be writing a change proposal?
I'd start by:
Packaging pynose without hacks (only making it Conflict with nos
On 11-04-2024 15:30, Sandro wrote:
I see "# Package doesn't provide any tests" in the %check section.
That certainly feels a bit dodgy. This successor of a test framework
decided to ditch all of the tests it used to have? That is certainly a
red flag.
More like a chicken and e
ps://github.com/seleniumbase/SeleniumBase
-- Sandro
--
___
python-devel mailing list -- python-devel@lists.fedoraproject.org
To unsubscribe send an email to python-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/
On 11-04-2024 15:17, Miro Hrončok wrote:
On 11. 04. 24 15:05, Sandro wrote:
On 11-04-2024 13:54, Miro Hrončok wrote:
On 11. 04. 24 11:55, Sandro wrote:
While I ponder those thoughts some more, moving forward in either
direction, the next step would be writing a change proposal?
I'd sta
On 11-04-2024 13:54, Miro Hrončok wrote:
On 11. 04. 24 11:55, Sandro wrote:
While I ponder those thoughts some more, moving forward in either
direction, the next step would be writing a change proposal?
I'd start by:
Packaging pynose without hacks (only making it Conflict with nos
On 10-04-2024 17:50, Miro Hrončok wrote:
On 10. 04. 24 17:30, Sandro wrote:
On 10-04-2024 12:04, Miro Hrončok wrote:
On 09. 04. 24 19:30, Sandro wrote:
Therefore, I'm thinking of introducing pynose as a drop in
replacement of deprecated nose. Pynose uses the same namespace as
nose
On 10-04-2024 12:04, Miro Hrončok wrote:
On 09. 04. 24 19:30, Sandro wrote:
Therefore, I'm thinking of introducing pynose as a drop in replacement
of deprecated nose. Pynose uses the same namespace as nose, but
provides python3dist(pynose). Thus adding Provides: for nose would
make it a
"pynose
is an updated version of nose". Not a successor that needs adaptation,
but basically a continuation. Time will tell.
[1] Ik know that adds up to 16. One package sneaked its way onto the
list, though it works fine with pynose.
-- Sandro
--
_
ainfracloud.org/coprs/gui1ty/nose
Cheers,
--
Sandro
FAS: gui1ty
Matrix:Penguinpee
Elsewhere: [Pp]enguinpee
--
___
python-devel mailing list -- python-devel@lists.fedoraproject.org
To unsubscribe send an email to python-devel-le...@lists.fedorapro
build backends, where it makes
sense enabling -p, e.g. meson-python.
-- Sandro
--
___
python-devel mailing list -- python-devel@lists.fedoraproject.org
To unsubscribe send an email to python-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https
thing.
What do you have in
build/BUILDROOT/*/usr/lib64/python3.12/site-packages/ inside your mock
changeroot?
-- Sandro
--
___
python-devel mailing list -- python-devel@lists.fedoraproject.org
To unsubscribe send an email to python-dev
be great
to get this in before the freeze.
[1] Neither do I. But, it's not always avoidable. If I had the time, I
would have let the two dependent updates go stable before pushing spyder.
Thanks for your help,
Sandro
___
python-deve
lf doing reviewing packages that don't use an explicit
%license.
This might be out of scope, but would it also be possible to have it
fail or issue a warning if %pyproject_save_files -l marks a license, but
the packager also uses an explicit %license in %f
On 27-07-2023 22:57, Sandro wrote:
On 27-07-2023 21:02, Michel Alexandre Salim wrote:
Thanks Miro!
On Thu, 2023-07-27 at 19:28 +0200, Miro Hrončok wrote:
On 27. 07. 23 18:26, Michel Alexandre Salim wrote:
⬢ [fedora-toolbox:38] ❯ rpmdistro-repoquery fedora rawhide --
enablerepo=fedora-source
:2.6.0-2.fc38.src
python-nashpy-0:0.0.37-1.fc39.src
python-pyunicorn-0:0.6.1-12.fc38.src
nashpy is fixed, but I'll take a look at the others. Given the disttags
they look like they FTBFSed anyway (cvise is fc36, ouch!)
I can take care of pyunicorn. It looks simple enough.
-- S
On 07-06-2023 22:15, Sandro wrote:
On 07-06-2023 02:30, Sandro wrote:
On 06-06-2023 09:39, Elliott Sales de Andrade wrote:
On Mon, Jun 5, 2023 at 6:45 AM Sandro wrote:
Hi again,
I'm trying to understand why I'm getting a circular import error
running
tests only in F37 [1].
It
On 07-06-2023 02:30, Sandro wrote:
On 06-06-2023 09:39, Elliott Sales de Andrade wrote:
On Mon, Jun 5, 2023 at 6:45 AM Sandro wrote:
Hi again,
I'm trying to understand why I'm getting a circular import error running
tests only in F37 [1].
It's an easy fix adding an empty
On 06-06-2023 09:39, Elliott Sales de Andrade wrote:
On Mon, Jun 5, 2023 at 6:45 AM Sandro wrote:
Hi again,
I'm trying to understand why I'm getting a circular import error running
tests only in F37 [1].
It's an easy fix adding an empty __init__.py in %prep, but why are
fc38
python-rpm-macros 3.11-5.fc37 3.11-10.fc38
python-pip-wheel 22.2.2-3.fc37 22.3.1-2.fc38
python-setuptools-wheel 62.6.0-3.fc37 65.5.1-2.fc38
[1] https://copr.fedorainfracloud.org/coprs/gui1ty/neuro-sig/build/6002232/
Cheers,
--
Sandro
FAS: gui1ty
IRC: Penguinpee
Elsewhere
s [1]. But I'm using setup.cfg
for backwards compatibility with older setuptools. Otherwise, the
package cannot be build for EL.
[1] https://github.com/munin-monitoring/PyMunin3
-- Sandro
___
python-devel mailing list -- python-devel@lists.fedorapro
know how tool.setuptools.packages.find.exclude behaves, but I
have seen this behavior with pytest, where the default was to exclude a
bunch of directories including ".*", but projects that set their own
excludes (without ".*"
[3]. But I'd like a second opinion
before submitting a PR upstream.
[1] https://kojipkgs.fedoraproject.org//work/tasks/5770/101775770/build.log
[2]
https://setuptools.pypa.io/en/latest/userguide/package_discovery.html#flat-layout
[3] https://copr.fedorainfracloud.org/coprs/gui1ty/neuro-sig/b
consent.
I'll proceed with it all the same. Without the package landing in
Fedora, Bottles will be broken forever. And who likes to spill a nice
drink? ;-)
-- Sandro
___
python-devel mailing list -- python-devel@lists.fedoraproject.org
To unsubscr
On 16-05-2023 15:56, Maxwell G wrote:
On Tue May 16, 2023 at 13:15 +0200, Sandro wrote:
Did I misunderstand/misinterpret the guidelines? The review is currently
stalled due to the PyPI parity issue.
[2] https://bugzilla.redhat.com/show_bug.cgi?id=2188653
I didn't mean to hold up the pa
On 05-05-2023 15:10, Sandro wrote:
On 27-04-2023 14:26, Sandro wrote:
Well, I submitted the package for review [2] and have been told that
vkbasalt not being published on PyPI is an issue wrt naming parity.
So, I filed a bug requesting publication on PyPI [3], but I haven't
heard back
On 27-04-2023 14:26, Sandro wrote:
Well, I submitted the package for review [2] and have been told that
vkbasalt not being published on PyPI is an issue wrt naming parity.
So, I filed a bug requesting publication on PyPI [3], but I haven't
heard back from upstream, yet. If upstream re
ere.
sed -r -i 's/(numpy)==/\1>=/' pyproject.toml
:facepalm:
I pledge tunnelvision (didn't scroll down far enough).
Thanks Ben!
-- Sandro
___
python-devel mailing list -- python-devel@lists.fedoraproject.org
To unsubscribe send an ema
oml#L13
[4] https://github.com/has2k1/scikit-misc/issues/24
Cheers,
--
Sandro
FAS: gui1ty
IRC: Penguinpee
Elsewhere: [Pp]enguinpee
___
python-devel mailing list -- python-devel@lists.fedoraproject.org
To unsubscribe send an email to python-devel-le...@
oach. Only vkbasalt-cli is not on
PyPI, yet.
-- Sandro
___
python-devel mailing list -- python-devel@lists.fedoraproject.org
To unsubscribe send an email to python-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject
on/vkbasalt-cli/-/issues/10
[4]
https://docs.fedoraproject.org/en-US/packaging-guidelines/Python/#_pypi_parity
-- Sandro
___
python-devel mailing list -- python-devel@lists.fedoraproject.org
To unsubscribe send an email to python-devel-le...@lists.fedorapro
On 21-04-2023 12:46, Sandro wrote:
I need to package vkbasalt-cli [1] as a dependency for Bottles. Bottles
will use the Python library, but vkbasalt-cli also provides a command
for independent/direct usage.
And here is the missing link:
[1] https://gitlab.com/TheEvilSkeleton/vkbasalt-cli
r 'python3-vkbasalt-cli'.
Could someone confirm that this is the right approach for vkbasalt-cli?
Thanks in advance,
--
Sandro
FAS: gui1ty
IRC: Penguinpee
Elsewhere: [Pp]enguinpee
___
python-devel mailing list -- python-devel@lists.fedoraprojec
heers,
Sandro
___
python-devel mailing list -- python-devel@lists.fedoraproject.org
To unsubscribe send an email to python-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guide
On 27-10-2022 17:25, Miro Hrončok wrote:
On 26. 10. 22 19:40, Sandro wrote:
Hi,
I'm getting the ImportError from subject specifically when
building python-plotnine for f36 (Python 3.10.7).
Yes, importing from .conftest in tests should not be possible.
The same package builds fine fo
this fails. I also tried with putting an
empty __init__.py in tests/. But this fails with an OSError in conftest.py.
Copr build:
https://copr.fedorainfracloud.org/coprs/gui1ty/neuro-sig/build/4988240/
Cheers,
--
Sandro
FAS: gui1ty
IRC: Penguinpee
Elsewhere: [Pp
On 11-10-2022 22:22, Sandro wrote:
On 11-10-2022 16:20, Ben Beasley wrote:
This is the classic issue where the “un-built” package gets imported
instead of the “built” one in the buildroot that you are trying to test.
I had some luck executing the tests, but ran into a BLAS linking issue
that I
On 13-10-2022 19:22, Neal Gompa wrote:
Would anybody be sad about that?
I'm fine with it. The less ARM in my life, the better.
I feel ya. ;-P
ARM: https://en.wikipedia.org/wiki/Association_of_Radical_Midwives
___
python-devel mailing list -- python
, it will be upgraded to
aarch64 eventually and I don't expect anything to break by not having
Python3.12 available for it.
-- Sandro
___
python-devel mailing list -- python-devel@lists.fedoraproject.org
To unsubscribe send an email to python-dev
fully. Please see
https://bugzilla.redhat.com/show_bug.cgi?id=2133438#c1.
Thanks, Ben. Down the rabbit hole we go!
🤔 Just who flagged this as 'good first issue'?
-- Sandro
PS: I used to go by 'whiterabbit' for some time years ago. My
w_bug.cgi?id=2133438
[2] https://github.com/has2k1/scikit-misc/issues/19
--
Sandro
FAS: gui1ty
IRC: Penguinpee
Elsewhere: [Pp]enguinpee
___
python-devel mailing list -- python-devel@lists.fedoraproject.org
To unsubscribe send an email to python-devel-le...@
On 03-10-2022 13:29, Miro Hrončok wrote:
On 03. 10. 22 12:55, Sandro wrote:
Regarding availability for el9, I didn't know (where to look). I looked on
src.fp.o:
https://src.fedoraproject.org/rpms/python-setuptools_scm
There's an ancient version for el7, but nothing for el8 or e
On 03-10-2022 19:41, Miro Hrončok wrote:
On 03. 10. 22 13:30, Sandro wrote:
I was following the instructions in the project's README:
https://github.com/pypa/setuptools_scm#pyprojecttoml-usage
It's all lies and snake oil.
Upstream lists the requirement of the recent enough versio
On 03-10-2022 12:55, Sandro wrote:
On 03-10-2022 12:14, Miro Hrončok wrote:
On 02. 10. 22 12:10, Sandro wrote:
[setuptools_scm] is currently not available for el9...
But it is. It' part of the RHEL 9 CRB repository. However, also version 6.0.1.
Why do you require >= 6.2 exactly?
On 03-10-2022 12:14, Miro Hrončok wrote:
On 02. 10. 22 12:10, Sandro wrote:
[setuptools_scm] is currently not available for el9...
But it is. It' part of the RHEL 9 CRB repository. However, also version 6.0.1.
Why do you require >= 6.2 exactly?
I was following the instruction
lable to a
broader audience. Although, I haven't done any research on that.
[1] https://github.com/penguinpee/PyMunin3/pull/3
[2] https://github.com/penguinpee/PyMunin3/issues/4
Happy Hacktober everyone,
-- Sandro
___
python-d
On 27-09-2022 19:41, Miro Hrončok wrote:
On 27. 09. 22 17:55, Sandro wrote:
On 27-09-2022 08:17, Lumír Balhar wrote:
Make sure that the build does not use the pyx file from upstream. It
seems to me that the file generated by Cython is in the source tarball
(skmisc/loess/src/_loess.pyx) and I
kage to install: 'changed'
Is there a standard way of handling noisy scripts? Or am I just out of
luck using pyproject macros? Or, my bet, am I missing something?
https://copr.fedorainfracloud.org/coprs/gui1ty/neuro-sig/build/4875750/
-- Sandro
_
).
Build:
https://copr.fedorainfracloud.org/coprs/gui1ty/neuro-sig/build/4869979/
Issue: https://github.com/has2k1/scikit-misc/issues/17
-- Sandro
___
python-devel mailing list -- python-devel@lists.fedoraproject.org
To unsubscribe send an email to pytho
On 04-09-2022 22:52, Miro Hrončok wrote:
On 04. 09. 22 22:08, Sandro wrote:
On 04-09-2022 20:42, Miro Hrončok wrote:
On 04. 09. 22 14:15, Sandro wrote:
Hi,
Hi.
I'm tinkering with a package in review, trying to understand the Python RPM
build process. The package is hatch-fancy-pypi-r
On 04-09-2022 20:42, Miro Hrončok wrote:
On 04. 09. 22 14:15, Sandro wrote:
Hi,
Hi.
I'm tinkering with a package in review, trying to understand the Python RPM
build process. The package is hatch-fancy-pypi-readme [1].
The package uses hatch for build, but it includes a non-license
//github.com/hynek/hatch-fancy-pypi-readme
[2] https://pnemade.fedorapeople.org/python-hatch-fancy-pypi-readme.spec
-- Sandro
___
python-devel mailing list -- python-devel@lists.fedoraproject.org
To unsubscribe send an email to python-devel-le...@lists.fedor
57 matches
Mail list logo
