On 29. 10. 21 14:49, Miro Hrončok wrote:
On 29. 10. 21 14:39, Miro Hrončok wrote:
From now on, it will be generated as:
python3.10dist(pyyaml) < 6~
Which will not be satisfied by any alpha/beta/rc release of PyYAML 6.
An only as I was typing this, I have realized that it won't work
On 31. 10. 21 19:21, Gordon Messmer wrote:
(it doesn't even use git snapshot, but upstream release tarball).
In my opinion, calling it an "upstream release tarball" implies intent that is
not in evidence. GitHub's release tarballs are a side-effect of declaring a
release for a project
On 10/31/21 02:45, Miro Hrončok wrote:
See for example
https://src.fedoraproject.org/rpms/python-mako/pull-request/13
Would we upstream that? I think that the "staying close to upstream
projects" policy suggests that we should. And, personally, I don't
think we should patch source
On 30. 10. 21 21:42, Gordon Messmer wrote:
On 10/29/21 05:49, Miro Hrončok wrote:
For some of them (e.g. mako), this seems to be a mistake even.
There are a lot of "dev0" versions in that set, so I took a look for the
cause. It looks like all of the "dev0" packages use github source rather
On 10/30/21 13:57, Ian McInerney wrote:
I disagree. PyPI is basically a packaging environment, so
using the tarballs from there would mean we are then subject
to the curation decisions by the people who package
On 10/30/21 13:12, Felix Schwarz wrote:
Am 30.10.21 um 21:42 schrieb Gordon Messmer:
I'd suggest that we should instead strongly encourage the use of PyPI
URLs.
I agree that pypi downloads are usually preferable. However I had to
use github tarballs sometimes as upstream did not ship the
On Sat, Oct 30, 2021 at 8:42 PM Gordon Messmer
wrote:
> On 10/29/21 05:49, Miro Hrončok wrote:
> > For some of them (e.g. mako), this seems to be a mistake even.
>
>
> There are a lot of "dev0" versions in that set, so I took a look for the
> cause. It looks like all of the "dev0" packages use
Almost all of the Python packages I maintain have something useful in the
GitHub archive that isn’t in the PyPI archive. I find that PyPI source
distributions commonly lack test suites and usually lack documentation. I
choose PyPI sources where all else is equal, but in a lot of cases using
Am 30.10.21 um 21:42 schrieb Gordon Messmer:
I'd suggest that we should instead strongly encourage the use of PyPI URLs.
I agree that pypi downloads are usually preferable. However I had to use github
tarballs sometimes as upstream did not ship the test suite for pypi tarballs...
Just my 2
On 10/29/21 05:49, Miro Hrončok wrote:
For some of them (e.g. mako), this seems to be a mistake even.
There are a lot of "dev0" versions in that set, so I took a look for the
cause. It looks like all of the "dev0" packages use github source
rather than PyPI sources, which means that none
On 29. 10. 21 14:39, Miro Hrončok wrote:
From now on, it will be generated as:
python3.10dist(pyyaml) < 6~
Which will not be satisfied by any alpha/beta/rc release of PyYAML 6.
An only as I was typing this, I have realized that it won't work for dev
releases, because 6~~dev1 < 6~ :(
Hello Pythonistas,
just a heads up that in rawhide, the automatically generated requirements on
Python packages, e.g. python3.Xdist(DISTNAME), ar enow generated in more strict
form.
If a package required "PyYAML < 6", it was previously generated as:
python3.10dist(pyyaml) < 6
Which was
12 matches
Mail list logo
