[arch-commits] Commit in python-poetry/repos/community-any (8 files)
Date: Monday, August 22, 2022 @ 11:45:39
Author: alerque
Revision: 1274674
archrelease: copy trunk to community-any
Added:
python-poetry/repos/community-any/0001-Suppress-dependency-versions-which-are-known-to-be-t.patch
(from rev 1274673,
python-poetry/trunk/0001-Suppress-dependency-versions-which-are-known-to-be-t.patch)
python-poetry/repos/community-any/0001-tests-cleanup-cache-and-http-usage.patch
(from rev 1274673,
python-poetry/trunk/0001-tests-cleanup-cache-and-http-usage.patch)
python-poetry/repos/community-any/PKGBUILD
(from rev 1274673, python-poetry/trunk/PKGBUILD)
python-poetry/repos/community-any/poetry-completions-generator
(from rev 1274673, python-poetry/trunk/poetry-completions-generator)
Deleted:
python-poetry/repos/community-any/0001-Suppress-dependency-versions-which-are-known-to-be-t.patch
python-poetry/repos/community-any/0001-tests-cleanup-cache-and-http-usage.patch
python-poetry/repos/community-any/PKGBUILD
python-poetry/repos/community-any/poetry-completions-generator
-+
0001-Suppress-dependency-versions-which-are-known-to-be-t.patch | 126 -
0001-tests-cleanup-cache-and-http-usage.patch | 1116
+-
PKGBUILD| 184 -
poetry-completions-generator| 30
4 files changed, 728 insertions(+), 728 deletions(-)
Deleted: 0001-Suppress-dependency-versions-which-are-known-to-be-t.patch
===
--- 0001-Suppress-dependency-versions-which-are-known-to-be-t.patch
2022-08-22 11:45:26 UTC (rev 1274673)
+++ 0001-Suppress-dependency-versions-which-are-known-to-be-t.patch
2022-08-22 11:45:39 UTC (rev 1274674)
@@ -1,63 +0,0 @@
-poetry habitually engages in:
-
-* dependency versions which are known to be too pessimistic
-* multiple editions of dependencies per python version
-
-The former all work just fine in reported use and should not be pinned; we
-package versions in Arch which are "too new". This is what unittests are
-for, anyway.
-
-The latter tries to enforce minimum versions of dependencies, but pins
-it twice, once with more relaxed pinning for older versions of python.
-If an old version works, it works irrespective of the python version,
-and you don't need to use minimum requirements as your mallet to force
-people to upgrade to the latest version anyway.
-
-https://github.com/dephell/dephell/issues/330
- pyproject.toml | 17 +++--
- 1 file changed, 3 insertions(+), 14 deletions(-)
-
-diff --git a/pyproject.toml b/pyproject.toml
-index 4fff27d..ea11504 100644
a/pyproject.toml
-+++ b/pyproject.toml
-@@ -31,10 +31,7 @@ crashtest = { version = "^0.3.0", python = "^3.6" }
- requests = "^2.18"
- cachy = "^0.3.0"
- requests-toolbelt = "^0.9.1"
--cachecontrol = [
--{ version = "^0.12.4", extras = ["filecache"], python = "<3.6" },
--{ version = "^0.12.9", extras = ["filecache"], python = "^3.6" }
--]
-+cachecontrol = { version = "*", extras = ["filecache"] }
- pkginfo = "^1.4"
- html5lib = "^1.0"
- shellingham = "^1.1"
-@@ -54,21 +51,13 @@ futures = { version = "^3.3.0", python = "~2.7" }
- glob2 = { version = "^0.6", python = "~2.7" }
- # functools32 is needed for Python 2.7
- functools32 = { version = "^3.2.3", python = "~2.7" }
--keyring = [
--{ version = "^18.0.1", python = "~2.7" },
--{ version = "^20.0.1", python = "~3.5" },
--{ version = ">=21.2.0", python = "^3.6" }
--]
-+keyring = "*"
- # Use subprocess32 for Python 2.7
- subprocess32 = { version = "^3.5", python = "~2.7" }
- importlib-metadata = {version = "^1.6.0", python = "<3.8"}
-
- [tool.poetry.dev-dependencies]
--pytest = [
--{version = "^4.1", python = "<3.5"},
--{version = "^5.4.3", python = "~3.5"},
--{version = "^6.2.5", python = ">=3.6"}
--]
-+pytest = "*"
- pytest-cov = "^2.5"
- pytest-mock = "^1.9"
- pre-commit = { version = "^2.6", python = "^3.6.1" }
---
-2.35.1
-
Copied:
python-poetry/repos/community-any/0001-Suppress-dependency-versions-which-are-known-to-be-t.patch
(from rev 1274673,
python-poetry/trunk/0001-Suppress-dependency-versions-which-are-known-to-be-t.patch)
===
--- 0001-Suppress-dependency-versions-which-are-known-to-be-t.patch
(rev 0)
+++ 0001-Suppress-dependency-versions-which-are-known-to-be-t.patch
2022-08-22 11:45:39 UTC (rev 1274674)
@@ -0,0 +1,63 @@
+poetry habitually engages in:
+
+* dependency versions which are known to be too pessimistic
+* multiple editions of dependencies per python version
+
+The former all work just fine in reported use and should not be pinned; we
+package versions in Arch which are "too new". This is what unittests are
+for, anyway.
+
+The latter tries to enforce minimum versions of dependencies, but pins
+it twice, once
[arch-commits] Commit in python-poetry/repos/community-any (8 files)
Date: Monday, August 1, 2022 @ 07:32:56
Author: arojas
Revision: 1259585
archrelease: copy trunk to community-any
Added:
python-poetry/repos/community-any/0001-Suppress-dependency-versions-which-are-known-to-be-t.patch
(from rev 1259584,
python-poetry/trunk/0001-Suppress-dependency-versions-which-are-known-to-be-t.patch)
python-poetry/repos/community-any/0001-tests-cleanup-cache-and-http-usage.patch
(from rev 1259584,
python-poetry/trunk/0001-tests-cleanup-cache-and-http-usage.patch)
python-poetry/repos/community-any/PKGBUILD
(from rev 1259584, python-poetry/trunk/PKGBUILD)
python-poetry/repos/community-any/poetry-completions-generator
(from rev 1259584, python-poetry/trunk/poetry-completions-generator)
Deleted:
python-poetry/repos/community-any/0001-Suppress-dependency-versions-which-are-known-to-be-t.patch
python-poetry/repos/community-any/0001-tests-cleanup-cache-and-http-usage.patch
python-poetry/repos/community-any/PKGBUILD
python-poetry/repos/community-any/poetry-completions-generator
-+
0001-Suppress-dependency-versions-which-are-known-to-be-t.patch | 126 -
0001-tests-cleanup-cache-and-http-usage.patch | 1116
+-
PKGBUILD| 182 -
poetry-completions-generator| 30
4 files changed, 728 insertions(+), 726 deletions(-)
Deleted: 0001-Suppress-dependency-versions-which-are-known-to-be-t.patch
===
--- 0001-Suppress-dependency-versions-which-are-known-to-be-t.patch
2022-08-01 07:32:42 UTC (rev 1259584)
+++ 0001-Suppress-dependency-versions-which-are-known-to-be-t.patch
2022-08-01 07:32:56 UTC (rev 1259585)
@@ -1,63 +0,0 @@
-poetry habitually engages in:
-
-* dependency versions which are known to be too pessimistic
-* multiple editions of dependencies per python version
-
-The former all work just fine in reported use and should not be pinned; we
-package versions in Arch which are "too new". This is what unittests are
-for, anyway.
-
-The latter tries to enforce minimum versions of dependencies, but pins
-it twice, once with more relaxed pinning for older versions of python.
-If an old version works, it works irrespective of the python version,
-and you don't need to use minimum requirements as your mallet to force
-people to upgrade to the latest version anyway.
-
-https://github.com/dephell/dephell/issues/330
- pyproject.toml | 17 +++--
- 1 file changed, 3 insertions(+), 14 deletions(-)
-
-diff --git a/pyproject.toml b/pyproject.toml
-index 4fff27d..ea11504 100644
a/pyproject.toml
-+++ b/pyproject.toml
-@@ -31,10 +31,7 @@ crashtest = { version = "^0.3.0", python = "^3.6" }
- requests = "^2.18"
- cachy = "^0.3.0"
- requests-toolbelt = "^0.9.1"
--cachecontrol = [
--{ version = "^0.12.4", extras = ["filecache"], python = "<3.6" },
--{ version = "^0.12.9", extras = ["filecache"], python = "^3.6" }
--]
-+cachecontrol = { version = "*", extras = ["filecache"] }
- pkginfo = "^1.4"
- html5lib = "^1.0"
- shellingham = "^1.1"
-@@ -54,21 +51,13 @@ futures = { version = "^3.3.0", python = "~2.7" }
- glob2 = { version = "^0.6", python = "~2.7" }
- # functools32 is needed for Python 2.7
- functools32 = { version = "^3.2.3", python = "~2.7" }
--keyring = [
--{ version = "^18.0.1", python = "~2.7" },
--{ version = "^20.0.1", python = "~3.5" },
--{ version = ">=21.2.0", python = "^3.6" }
--]
-+keyring = "*"
- # Use subprocess32 for Python 2.7
- subprocess32 = { version = "^3.5", python = "~2.7" }
- importlib-metadata = {version = "^1.6.0", python = "<3.8"}
-
- [tool.poetry.dev-dependencies]
--pytest = [
--{version = "^4.1", python = "<3.5"},
--{version = "^5.4.3", python = "~3.5"},
--{version = "^6.2.5", python = ">=3.6"}
--]
-+pytest = "*"
- pytest-cov = "^2.5"
- pytest-mock = "^1.9"
- pre-commit = { version = "^2.6", python = "^3.6.1" }
---
-2.35.1
-
Copied:
python-poetry/repos/community-any/0001-Suppress-dependency-versions-which-are-known-to-be-t.patch
(from rev 1259584,
python-poetry/trunk/0001-Suppress-dependency-versions-which-are-known-to-be-t.patch)
===
--- 0001-Suppress-dependency-versions-which-are-known-to-be-t.patch
(rev 0)
+++ 0001-Suppress-dependency-versions-which-are-known-to-be-t.patch
2022-08-01 07:32:56 UTC (rev 1259585)
@@ -0,0 +1,63 @@
+poetry habitually engages in:
+
+* dependency versions which are known to be too pessimistic
+* multiple editions of dependencies per python version
+
+The former all work just fine in reported use and should not be pinned; we
+package versions in Arch which are "too new". This is what unittests are
+for, anyway.
+
+The latter tries to enforce minimum versions of dependencies, but pins
+it twice, once
[arch-commits] Commit in python-poetry/repos/community-any (8 files)
Date: Friday, July 8, 2022 @ 15:31:24
Author: alerque
Revision: 1248703
archrelease: copy trunk to community-any
Added:
python-poetry/repos/community-any/0001-Suppress-dependency-versions-which-are-known-to-be-t.patch
(from rev 1248702,
python-poetry/trunk/0001-Suppress-dependency-versions-which-are-known-to-be-t.patch)
python-poetry/repos/community-any/0001-tests-cleanup-cache-and-http-usage.patch
(from rev 1248702,
python-poetry/trunk/0001-tests-cleanup-cache-and-http-usage.patch)
python-poetry/repos/community-any/PKGBUILD
(from rev 1248702, python-poetry/trunk/PKGBUILD)
python-poetry/repos/community-any/poetry-completions-generator
(from rev 1248702, python-poetry/trunk/poetry-completions-generator)
Deleted:
python-poetry/repos/community-any/0001-Suppress-dependency-versions-which-are-known-to-be-t.patch
python-poetry/repos/community-any/0001-tests-cleanup-cache-and-http-usage.patch
python-poetry/repos/community-any/PKGBUILD
python-poetry/repos/community-any/poetry-completions-generator
-+
0001-Suppress-dependency-versions-which-are-known-to-be-t.patch | 126 -
0001-tests-cleanup-cache-and-http-usage.patch | 1116
+-
PKGBUILD| 180 -
poetry-completions-generator| 30
4 files changed, 726 insertions(+), 726 deletions(-)
Deleted: 0001-Suppress-dependency-versions-which-are-known-to-be-t.patch
===
--- 0001-Suppress-dependency-versions-which-are-known-to-be-t.patch
2022-07-08 15:31:11 UTC (rev 1248702)
+++ 0001-Suppress-dependency-versions-which-are-known-to-be-t.patch
2022-07-08 15:31:24 UTC (rev 1248703)
@@ -1,63 +0,0 @@
-poetry habitually engages in:
-
-* dependency versions which are known to be too pessimistic
-* multiple editions of dependencies per python version
-
-The former all work just fine in reported use and should not be pinned; we
-package versions in Arch which are "too new". This is what unittests are
-for, anyway.
-
-The latter tries to enforce minimum versions of dependencies, but pins
-it twice, once with more relaxed pinning for older versions of python.
-If an old version works, it works irrespective of the python version,
-and you don't need to use minimum requirements as your mallet to force
-people to upgrade to the latest version anyway.
-
-https://github.com/dephell/dephell/issues/330
- pyproject.toml | 17 +++--
- 1 file changed, 3 insertions(+), 14 deletions(-)
-
-diff --git a/pyproject.toml b/pyproject.toml
-index 4fff27d..ea11504 100644
a/pyproject.toml
-+++ b/pyproject.toml
-@@ -31,10 +31,7 @@ crashtest = { version = "^0.3.0", python = "^3.6" }
- requests = "^2.18"
- cachy = "^0.3.0"
- requests-toolbelt = "^0.9.1"
--cachecontrol = [
--{ version = "^0.12.4", extras = ["filecache"], python = "<3.6" },
--{ version = "^0.12.9", extras = ["filecache"], python = "^3.6" }
--]
-+cachecontrol = { version = "*", extras = ["filecache"] }
- pkginfo = "^1.4"
- html5lib = "^1.0"
- shellingham = "^1.1"
-@@ -54,21 +51,13 @@ futures = { version = "^3.3.0", python = "~2.7" }
- glob2 = { version = "^0.6", python = "~2.7" }
- # functools32 is needed for Python 2.7
- functools32 = { version = "^3.2.3", python = "~2.7" }
--keyring = [
--{ version = "^18.0.1", python = "~2.7" },
--{ version = "^20.0.1", python = "~3.5" },
--{ version = ">=21.2.0", python = "^3.6" }
--]
-+keyring = "*"
- # Use subprocess32 for Python 2.7
- subprocess32 = { version = "^3.5", python = "~2.7" }
- importlib-metadata = {version = "^1.6.0", python = "<3.8"}
-
- [tool.poetry.dev-dependencies]
--pytest = [
--{version = "^4.1", python = "<3.5"},
--{version = "^5.4.3", python = "~3.5"},
--{version = "^6.2.5", python = ">=3.6"}
--]
-+pytest = "*"
- pytest-cov = "^2.5"
- pytest-mock = "^1.9"
- pre-commit = { version = "^2.6", python = "^3.6.1" }
---
-2.35.1
-
Copied:
python-poetry/repos/community-any/0001-Suppress-dependency-versions-which-are-known-to-be-t.patch
(from rev 1248702,
python-poetry/trunk/0001-Suppress-dependency-versions-which-are-known-to-be-t.patch)
===
--- 0001-Suppress-dependency-versions-which-are-known-to-be-t.patch
(rev 0)
+++ 0001-Suppress-dependency-versions-which-are-known-to-be-t.patch
2022-07-08 15:31:24 UTC (rev 1248703)
@@ -0,0 +1,63 @@
+poetry habitually engages in:
+
+* dependency versions which are known to be too pessimistic
+* multiple editions of dependencies per python version
+
+The former all work just fine in reported use and should not be pinned; we
+package versions in Arch which are "too new". This is what unittests are
+for, anyway.
+
+The latter tries to enforce minimum versions of dependencies, but pins
+it twice, once
[arch-commits] Commit in python-poetry/repos/community-any (8 files)
Date: Tuesday, February 22, 2022 @ 19:40:29
Author: alerque
Revision: 1136091
archrelease: copy trunk to community-any
Added:
python-poetry/repos/community-any/0001-Suppress-dependency-versions-which-are-known-to-be-t.patch
(from rev 1136090,
python-poetry/trunk/0001-Suppress-dependency-versions-which-are-known-to-be-t.patch)
python-poetry/repos/community-any/0001-tests-cleanup-cache-and-http-usage.patch
(from rev 1136090,
python-poetry/trunk/0001-tests-cleanup-cache-and-http-usage.patch)
python-poetry/repos/community-any/PKGBUILD
(from rev 1136090, python-poetry/trunk/PKGBUILD)
python-poetry/repos/community-any/poetry-completions-generator
(from rev 1136090, python-poetry/trunk/poetry-completions-generator)
Deleted:
python-poetry/repos/community-any/0001-Suppress-dependency-versions-which-are-known-to-be-t.patch
python-poetry/repos/community-any/0001-tests-cleanup-cache-and-http-usage.patch
python-poetry/repos/community-any/PKGBUILD
python-poetry/repos/community-any/poetry-completions-generator
-+
0001-Suppress-dependency-versions-which-are-known-to-be-t.patch | 126 -
0001-tests-cleanup-cache-and-http-usage.patch | 1116
+-
PKGBUILD| 173 -
poetry-completions-generator| 30
4 files changed, 722 insertions(+), 723 deletions(-)
Deleted: 0001-Suppress-dependency-versions-which-are-known-to-be-t.patch
===
--- 0001-Suppress-dependency-versions-which-are-known-to-be-t.patch
2022-02-22 19:40:18 UTC (rev 1136090)
+++ 0001-Suppress-dependency-versions-which-are-known-to-be-t.patch
2022-02-22 19:40:29 UTC (rev 1136091)
@@ -1,63 +0,0 @@
-poetry habitually engages in:
-
-* dependency versions which are known to be too pessimistic
-* multiple editions of dependencies per python version
-
-The former all work just fine in reported use and should not be pinned; we
-package versions in Arch which are "too new". This is what unittests are
-for, anyway.
-
-The latter tries to enforce minimum versions of dependencies, but pins
-it twice, once with more relaxed pinning for older versions of python.
-If an old version works, it works irrespective of the python version,
-and you don't need to use minimum requirements as your mallet to force
-people to upgrade to the latest version anyway.
-
-https://github.com/dephell/dephell/issues/330
- pyproject.toml | 17 +++--
- 1 file changed, 3 insertions(+), 14 deletions(-)
-
-diff --git a/pyproject.toml b/pyproject.toml
-index 4fff27d..ea11504 100644
a/pyproject.toml
-+++ b/pyproject.toml
-@@ -31,10 +31,7 @@ crashtest = { version = "^0.3.0", python = "^3.6" }
- requests = "^2.18"
- cachy = "^0.3.0"
- requests-toolbelt = "^0.9.1"
--cachecontrol = [
--{ version = "^0.12.4", extras = ["filecache"], python = "<3.6" },
--{ version = "^0.12.9", extras = ["filecache"], python = "^3.6" }
--]
-+cachecontrol = { version = "*", extras = ["filecache"] }
- pkginfo = "^1.4"
- html5lib = "^1.0"
- shellingham = "^1.1"
-@@ -54,21 +51,13 @@ futures = { version = "^3.3.0", python = "~2.7" }
- glob2 = { version = "^0.6", python = "~2.7" }
- # functools32 is needed for Python 2.7
- functools32 = { version = "^3.2.3", python = "~2.7" }
--keyring = [
--{ version = "^18.0.1", python = "~2.7" },
--{ version = "^20.0.1", python = "~3.5" },
--{ version = ">=21.2.0", python = "^3.6" }
--]
-+keyring = "*"
- # Use subprocess32 for Python 2.7
- subprocess32 = { version = "^3.5", python = "~2.7" }
- importlib-metadata = {version = "^1.6.0", python = "<3.8"}
-
- [tool.poetry.dev-dependencies]
--pytest = [
--{version = "^4.1", python = "<3.5"},
--{version = "^5.4.3", python = "~3.5"},
--{version = "^6.2.5", python = ">=3.6"}
--]
-+pytest = "*"
- pytest-cov = "^2.5"
- pytest-mock = "^1.9"
- pre-commit = { version = "^2.6", python = "^3.6.1" }
---
-2.35.1
-
Copied:
python-poetry/repos/community-any/0001-Suppress-dependency-versions-which-are-known-to-be-t.patch
(from rev 1136090,
python-poetry/trunk/0001-Suppress-dependency-versions-which-are-known-to-be-t.patch)
===
--- 0001-Suppress-dependency-versions-which-are-known-to-be-t.patch
(rev 0)
+++ 0001-Suppress-dependency-versions-which-are-known-to-be-t.patch
2022-02-22 19:40:29 UTC (rev 1136091)
@@ -0,0 +1,63 @@
+poetry habitually engages in:
+
+* dependency versions which are known to be too pessimistic
+* multiple editions of dependencies per python version
+
+The former all work just fine in reported use and should not be pinned; we
+package versions in Arch which are "too new". This is what unittests are
+for, anyway.
+
+The latter tries to enforce minimum versions of dependencies, but pins
+it twice,
[arch-commits] Commit in python-poetry/repos/community-any (8 files)
Date: Friday, February 11, 2022 @ 09:57:24
Author: alerque
Revision: 1131821
archrelease: copy trunk to community-any
Added:
python-poetry/repos/community-any/0001-Suppress-dependency-versions-which-are-known-to-be-t.patch
(from rev 1131820,
python-poetry/trunk/0001-Suppress-dependency-versions-which-are-known-to-be-t.patch)
python-poetry/repos/community-any/0001-tests-cleanup-cache-and-http-usage.patch
(from rev 1131820,
python-poetry/trunk/0001-tests-cleanup-cache-and-http-usage.patch)
python-poetry/repos/community-any/PKGBUILD
(from rev 1131820, python-poetry/trunk/PKGBUILD)
python-poetry/repos/community-any/poetry-completions-generator
(from rev 1131820, python-poetry/trunk/poetry-completions-generator)
Deleted:
python-poetry/repos/community-any/0001-Suppress-dependency-versions-which-are-known-to-be-t.patch
python-poetry/repos/community-any/0001-tests-cleanup-cache-and-http-usage.patch
python-poetry/repos/community-any/PKGBUILD
python-poetry/repos/community-any/poetry-completions-generator
-+
0001-Suppress-dependency-versions-which-are-known-to-be-t.patch | 120 -
0001-tests-cleanup-cache-and-http-usage.patch | 1116
+-
PKGBUILD| 172 -
poetry-completions-generator| 30
4 files changed, 723 insertions(+), 715 deletions(-)
Deleted: 0001-Suppress-dependency-versions-which-are-known-to-be-t.patch
===
--- 0001-Suppress-dependency-versions-which-are-known-to-be-t.patch
2022-02-11 09:57:13 UTC (rev 1131820)
+++ 0001-Suppress-dependency-versions-which-are-known-to-be-t.patch
2022-02-11 09:57:24 UTC (rev 1131821)
@@ -1,57 +0,0 @@
-poetry habitually engages in:
-- dependency versions which are known to be too pessimistic
-- multiple editions of dependencies per python version
-
-The former all work just fine in reported use and should not be pinned; we
-package versions in Arch which are "too new". This is what unittests are
-for, anyway.
-
-The latter tries to enforce minimum versions of dependencies, but pins
-it twice, once with more relaxed pinning for older versions of python.
-If an old version works, it works irrespective of the python version,
-and you don't need to use minimum requirements as your mallet to force
-people to upgrade to the latest version anyway.
-https://github.com/dephell/dephell/issues/330
- pyproject.toml | 11 ++-
- 1 file changed, 2 insertions(+), 9 deletions(-)
-
-diff --git a/pyproject.toml b/pyproject.toml
-index 8c1f137..81ebc89 100644
a/pyproject.toml
-+++ b/pyproject.toml
-@@ -31,10 +31,7 @@
- requests = "^2.18"
- cachy = "^0.3.0"
- requests-toolbelt = "^0.9.1"
--cachecontrol = [
--{ version = "^0.12.4", extras = ["filecache"], python = "<3.6" },
--{ version = "^0.12.9", extras = ["filecache"], python = "^3.6" }
--]
-+cachecontrol = { version = "*", extras = ["filecache"] }
- pkginfo = "^1.4"
- html5lib = "^1.0"
- shellingham = "^1.1"
-@@ -54,20 +51,13 @@
- glob2 = { version = "^0.6", python = "~2.7" }
- # functools32 is needed for Python 2.7
- functools32 = { version = "^3.2.3", python = "~2.7" }
--keyring = [
--{ version = "^18.0.1", python = "~2.7" },
--{ version = "^20.0.1", python = "~3.5" },
--{ version = "^21.2.0", python = "^3.6" }
--]
-+keyring = "*"
- # Use subprocess32 for Python 2.7
- subprocess32 = { version = "^3.5", python = "~2.7" }
- importlib-metadata = {version = "^1.6.0", python = "<3.8"}
-
- [tool.poetry.dev-dependencies]
--pytest = [
--{version = "^4.1", python = "<3.5"},
--{version = "^5.4.3", python = ">=3.5"}
--]
-+pytest = "*"
- pytest-cov = "^2.5"
- pytest-mock = "^1.9"
- pre-commit = { version = "^2.6", python = "^3.6.1" }
Copied:
python-poetry/repos/community-any/0001-Suppress-dependency-versions-which-are-known-to-be-t.patch
(from rev 1131820,
python-poetry/trunk/0001-Suppress-dependency-versions-which-are-known-to-be-t.patch)
===
--- 0001-Suppress-dependency-versions-which-are-known-to-be-t.patch
(rev 0)
+++ 0001-Suppress-dependency-versions-which-are-known-to-be-t.patch
2022-02-11 09:57:24 UTC (rev 1131821)
@@ -0,0 +1,63 @@
+poetry habitually engages in:
+
+* dependency versions which are known to be too pessimistic
+* multiple editions of dependencies per python version
+
+The former all work just fine in reported use and should not be pinned; we
+package versions in Arch which are "too new". This is what unittests are
+for, anyway.
+
+The latter tries to enforce minimum versions of dependencies, but pins
+it twice, once with more relaxed pinning for older versions of python.
+If an old version works, it works irrespective of the python version,
+and you don't need to use minimum
[arch-commits] Commit in python-poetry/repos/community-any (8 files)
Date: Wednesday, January 5, 2022 @ 17:55:37
Author: alerque
Revision: 1093312
archrelease: copy trunk to community-any
Added:
python-poetry/repos/community-any/0001-Suppress-dependency-versions-which-are-known-to-be-t.patch
(from rev 1093311,
python-poetry/trunk/0001-Suppress-dependency-versions-which-are-known-to-be-t.patch)
python-poetry/repos/community-any/0001-tests-cleanup-cache-and-http-usage.patch
(from rev 1093311,
python-poetry/trunk/0001-tests-cleanup-cache-and-http-usage.patch)
python-poetry/repos/community-any/PKGBUILD
(from rev 1093311, python-poetry/trunk/PKGBUILD)
python-poetry/repos/community-any/poetry-completions-generator
(from rev 1093311, python-poetry/trunk/poetry-completions-generator)
Deleted:
python-poetry/repos/community-any/0001-Suppress-dependency-versions-which-are-known-to-be-t.patch
python-poetry/repos/community-any/0001-tests-cleanup-cache-and-http-usage.patch
python-poetry/repos/community-any/PKGBUILD
python-poetry/repos/community-any/poetry-completions-generator
-+
0001-Suppress-dependency-versions-which-are-known-to-be-t.patch | 114 -
0001-tests-cleanup-cache-and-http-usage.patch | 1116
+-
PKGBUILD| 168 -
poetry-completions-generator| 30
4 files changed, 715 insertions(+), 713 deletions(-)
Deleted: 0001-Suppress-dependency-versions-which-are-known-to-be-t.patch
===
--- 0001-Suppress-dependency-versions-which-are-known-to-be-t.patch
2022-01-05 17:54:27 UTC (rev 1093311)
+++ 0001-Suppress-dependency-versions-which-are-known-to-be-t.patch
2022-01-05 17:55:37 UTC (rev 1093312)
@@ -1,57 +0,0 @@
-poetry habitually engages in:
-- dependency versions which are known to be too pessimistic
-- multiple editions of dependencies per python version
-
-The former all work just fine in reported use and should not be pinned; we
-package versions in Arch which are "too new". This is what unittests are
-for, anyway.
-
-The latter tries to enforce minimum versions of dependencies, but pins
-it twice, once with more relaxed pinning for older versions of python.
-If an old version works, it works irrespective of the python version,
-and you don't need to use minimum requirements as your mallet to force
-people to upgrade to the latest version anyway.
-https://github.com/dephell/dephell/issues/330
- pyproject.toml | 11 ++-
- 1 file changed, 2 insertions(+), 9 deletions(-)
-
-diff --git a/pyproject.toml b/pyproject.toml
-index 8c1f137..81ebc89 100644
a/pyproject.toml
-+++ b/pyproject.toml
-@@ -31,10 +31,7 @@
- requests = "^2.18"
- cachy = "^0.3.0"
- requests-toolbelt = "^0.9.1"
--cachecontrol = [
--{ version = "^0.12.4", extras = ["filecache"], python = "<3.6" },
--{ version = "^0.12.9", extras = ["filecache"], python = "^3.6" }
--]
-+cachecontrol = { version = "*", extras = ["filecache"] }
- pkginfo = "^1.4"
- html5lib = "^1.0"
- shellingham = "^1.1"
-@@ -54,20 +51,13 @@
- glob2 = { version = "^0.6", python = "~2.7" }
- # functools32 is needed for Python 2.7
- functools32 = { version = "^3.2.3", python = "~2.7" }
--keyring = [
--{ version = "^18.0.1", python = "~2.7" },
--{ version = "^20.0.1", python = "~3.5" },
--{ version = "^21.2.0", python = "^3.6" }
--]
-+keyring = "*"
- # Use subprocess32 for Python 2.7
- subprocess32 = { version = "^3.5", python = "~2.7" }
- importlib-metadata = {version = "^1.6.0", python = "<3.8"}
-
- [tool.poetry.dev-dependencies]
--pytest = [
--{version = "^4.1", python = "<3.5"},
--{version = "^5.4.3", python = ">=3.5"}
--]
-+pytest = "*"
- pytest-cov = "^2.5"
- pytest-mock = "^1.9"
- pre-commit = { version = "^2.6", python = "^3.6.1" }
Copied:
python-poetry/repos/community-any/0001-Suppress-dependency-versions-which-are-known-to-be-t.patch
(from rev 1093311,
python-poetry/trunk/0001-Suppress-dependency-versions-which-are-known-to-be-t.patch)
===
--- 0001-Suppress-dependency-versions-which-are-known-to-be-t.patch
(rev 0)
+++ 0001-Suppress-dependency-versions-which-are-known-to-be-t.patch
2022-01-05 17:55:37 UTC (rev 1093312)
@@ -0,0 +1,57 @@
+poetry habitually engages in:
+- dependency versions which are known to be too pessimistic
+- multiple editions of dependencies per python version
+
+The former all work just fine in reported use and should not be pinned; we
+package versions in Arch which are "too new". This is what unittests are
+for, anyway.
+
+The latter tries to enforce minimum versions of dependencies, but pins
+it twice, once with more relaxed pinning for older versions of python.
+If an old version works, it works irrespective of the python version,
+and you don't need to use minimum requirements
[arch-commits] Commit in python-poetry/repos/community-any (8 files)
Date: Saturday, December 11, 2021 @ 19:31:23
Author: alerque
Revision: 1068315
archrelease: copy trunk to community-any
Added:
python-poetry/repos/community-any/0001-Suppress-dependency-versions-which-are-known-to-be-t.patch
(from rev 1068314,
python-poetry/trunk/0001-Suppress-dependency-versions-which-are-known-to-be-t.patch)
python-poetry/repos/community-any/0001-tests-cleanup-cache-and-http-usage.patch
(from rev 1068314,
python-poetry/trunk/0001-tests-cleanup-cache-and-http-usage.patch)
python-poetry/repos/community-any/PKGBUILD
(from rev 1068314, python-poetry/trunk/PKGBUILD)
python-poetry/repos/community-any/poetry-completions-generator
(from rev 1068314, python-poetry/trunk/poetry-completions-generator)
Deleted:
python-poetry/repos/community-any/0001-Suppress-dependency-versions-which-are-known-to-be-t.patch
python-poetry/repos/community-any/0001-tests-cleanup-cache-and-http-usage.patch
python-poetry/repos/community-any/PKGBUILD
python-poetry/repos/community-any/poetry-completions-generator
-+
0001-Suppress-dependency-versions-which-are-known-to-be-t.patch | 110
0001-tests-cleanup-cache-and-http-usage.patch | 1116
+-
PKGBUILD| 162 -
poetry-completions-generator| 30
4 files changed, 713 insertions(+), 705 deletions(-)
Deleted: 0001-Suppress-dependency-versions-which-are-known-to-be-t.patch
===
--- 0001-Suppress-dependency-versions-which-are-known-to-be-t.patch
2021-12-11 19:31:13 UTC (rev 1068314)
+++ 0001-Suppress-dependency-versions-which-are-known-to-be-t.patch
2021-12-11 19:31:23 UTC (rev 1068315)
@@ -1,53 +0,0 @@
-From cc5b938f7f9e3c536f4a60c35cdd2085b3933618 Mon Sep 17 00:00:00 2001
-From: Eli Schwartz
-Date: Mon, 27 Apr 2020 21:51:57 -0400
-Subject: [PATCH] Fix completely broken dependencies.
-
-poetry habitually engages in:
-- dependency versions which are known to be too pessimistic
-- multiple editions of dependencies per python version
-
-The former all work just fine in reported use and should not be pinned; we
-package versions in Arch which are "too new". This is what unittests are
-for, anyway.
-
-The latter tries to enforce minimum versions of dependencies, but pins
-it twice, once with more relaxed pinning for older versions of python.
-If an old version works, it works irrespective of the python version,
-and you don't need to use minimum requirements as your mallet to force
-people to upgrade to the latest version anyway.
-https://github.com/dephell/dephell/issues/330
- pyproject.toml | 11 ++-
- 1 file changed, 2 insertions(+), 9 deletions(-)
-
-diff --git a/pyproject.toml b/pyproject.toml
-index 8c1f137..81ebc89 100644
a/pyproject.toml
-+++ b/pyproject.toml
-@@ -51,20 +51,13 @@ futures = { version = "^3.3.0", python = "~2.7" }
- glob2 = { version = "^0.6", python = "~2.7" }
- # functools32 is needed for Python 2.7
- functools32 = { version = "^3.2.3", python = "~2.7" }
--keyring = [
--{ version = "^18.0.1", python = "~2.7" },
--{ version = "^20.0.1", python = "~3.5" },
--{ version = "^21.2.0", python = "^3.6" }
--]
-+keyring = "*"
- # Use subprocess32 for Python 2.7
- subprocess32 = { version = "^3.5", python = "~2.7" }
- importlib-metadata = {version = "^1.6.0", python = "<3.8"}
-
- [tool.poetry.dev-dependencies]
--pytest = [
--{version = "^4.1", python = "<3.5"},
--{version = "^5.4.3", python = ">=3.5"}
--]
-+pytest = { version = ">=4.1" }
- pytest-cov = "^2.5"
- pytest-mock = "^1.9"
- pre-commit = { version = "^2.6", python = "^3.6.1" }
---
-2.28.0
-
Copied:
python-poetry/repos/community-any/0001-Suppress-dependency-versions-which-are-known-to-be-t.patch
(from rev 1068314,
python-poetry/trunk/0001-Suppress-dependency-versions-which-are-known-to-be-t.patch)
===
--- 0001-Suppress-dependency-versions-which-are-known-to-be-t.patch
(rev 0)
+++ 0001-Suppress-dependency-versions-which-are-known-to-be-t.patch
2021-12-11 19:31:23 UTC (rev 1068315)
@@ -0,0 +1,57 @@
+poetry habitually engages in:
+- dependency versions which are known to be too pessimistic
+- multiple editions of dependencies per python version
+
+The former all work just fine in reported use and should not be pinned; we
+package versions in Arch which are "too new". This is what unittests are
+for, anyway.
+
+The latter tries to enforce minimum versions of dependencies, but pins
+it twice, once with more relaxed pinning for older versions of python.
+If an old version works, it works irrespective of the python version,
+and you don't need to use minimum requirements as your mallet to force
+people to upgrade to the latest version anyway.
[arch-commits] Commit in python-poetry/repos/community-any (8 files)
Date: Tuesday, October 5, 2021 @ 21:24:11
Author: svenstaro
Revision: 1027811
archrelease: copy trunk to community-any
Added:
python-poetry/repos/community-any/0001-Suppress-dependency-versions-which-are-known-to-be-t.patch
(from rev 1027810,
python-poetry/trunk/0001-Suppress-dependency-versions-which-are-known-to-be-t.patch)
python-poetry/repos/community-any/0001-tests-cleanup-cache-and-http-usage.patch
(from rev 1027810,
python-poetry/trunk/0001-tests-cleanup-cache-and-http-usage.patch)
python-poetry/repos/community-any/PKGBUILD
(from rev 1027810, python-poetry/trunk/PKGBUILD)
python-poetry/repos/community-any/poetry-completions-generator
(from rev 1027810, python-poetry/trunk/poetry-completions-generator)
Deleted:
python-poetry/repos/community-any/0001-Suppress-dependency-versions-which-are-known-to-be-t.patch
python-poetry/repos/community-any/0001-tests-cleanup-cache-and-http-usage.patch
python-poetry/repos/community-any/PKGBUILD
python-poetry/repos/community-any/poetry-completions-generator
-+
0001-Suppress-dependency-versions-which-are-known-to-be-t.patch | 106
0001-tests-cleanup-cache-and-http-usage.patch | 1116
+-
PKGBUILD| 158 -
poetry-completions-generator| 30
4 files changed, 705 insertions(+), 705 deletions(-)
Deleted: 0001-Suppress-dependency-versions-which-are-known-to-be-t.patch
===
--- 0001-Suppress-dependency-versions-which-are-known-to-be-t.patch
2021-10-05 21:24:00 UTC (rev 1027810)
+++ 0001-Suppress-dependency-versions-which-are-known-to-be-t.patch
2021-10-05 21:24:11 UTC (rev 1027811)
@@ -1,53 +0,0 @@
-From cc5b938f7f9e3c536f4a60c35cdd2085b3933618 Mon Sep 17 00:00:00 2001
-From: Eli Schwartz
-Date: Mon, 27 Apr 2020 21:51:57 -0400
-Subject: [PATCH] Fix completely broken dependencies.
-
-poetry habitually engages in:
-- dependency versions which are known to be too pessimistic
-- multiple editions of dependencies per python version
-
-The former all work just fine in reported use and should not be pinned; we
-package versions in Arch which are "too new". This is what unittests are
-for, anyway.
-
-The latter tries to enforce minimum versions of dependencies, but pins
-it twice, once with more relaxed pinning for older versions of python.
-If an old version works, it works irrespective of the python version,
-and you don't need to use minimum requirements as your mallet to force
-people to upgrade to the latest version anyway.
-https://github.com/dephell/dephell/issues/330
- pyproject.toml | 11 ++-
- 1 file changed, 2 insertions(+), 9 deletions(-)
-
-diff --git a/pyproject.toml b/pyproject.toml
-index 8c1f137..81ebc89 100644
a/pyproject.toml
-+++ b/pyproject.toml
-@@ -51,20 +51,13 @@ futures = { version = "^3.3.0", python = "~2.7" }
- glob2 = { version = "^0.6", python = "~2.7" }
- # functools32 is needed for Python 2.7
- functools32 = { version = "^3.2.3", python = "~2.7" }
--keyring = [
--{ version = "^18.0.1", python = "~2.7" },
--{ version = "^20.0.1", python = "~3.5" },
--{ version = "^21.2.0", python = "^3.6" }
--]
-+keyring = "*"
- # Use subprocess32 for Python 2.7
- subprocess32 = { version = "^3.5", python = "~2.7" }
- importlib-metadata = {version = "^1.6.0", python = "<3.8"}
-
- [tool.poetry.dev-dependencies]
--pytest = [
--{version = "^4.1", python = "<3.5"},
--{version = "^5.4.3", python = ">=3.5"}
--]
-+pytest = { version = ">=4.1" }
- pytest-cov = "^2.5"
- pytest-mock = "^1.9"
- pre-commit = { version = "^2.6", python = "^3.6.1" }
---
-2.28.0
-
Copied:
python-poetry/repos/community-any/0001-Suppress-dependency-versions-which-are-known-to-be-t.patch
(from rev 1027810,
python-poetry/trunk/0001-Suppress-dependency-versions-which-are-known-to-be-t.patch)
===
--- 0001-Suppress-dependency-versions-which-are-known-to-be-t.patch
(rev 0)
+++ 0001-Suppress-dependency-versions-which-are-known-to-be-t.patch
2021-10-05 21:24:11 UTC (rev 1027811)
@@ -0,0 +1,53 @@
+From cc5b938f7f9e3c536f4a60c35cdd2085b3933618 Mon Sep 17 00:00:00 2001
+From: Eli Schwartz
+Date: Mon, 27 Apr 2020 21:51:57 -0400
+Subject: [PATCH] Fix completely broken dependencies.
+
+poetry habitually engages in:
+- dependency versions which are known to be too pessimistic
+- multiple editions of dependencies per python version
+
+The former all work just fine in reported use and should not be pinned; we
+package versions in Arch which are "too new". This is what unittests are
+for, anyway.
+
+The latter tries to enforce minimum versions of dependencies, but pins
+it twice, once with more relaxed pinning for older versions of python.
+If an old version works, it works
[arch-commits] Commit in python-poetry/repos/community-any (8 files)
Date: Wednesday, September 22, 2021 @ 20:39:11
Author: svenstaro
Revision: 1021674
archrelease: copy trunk to community-any
Added:
python-poetry/repos/community-any/0001-Suppress-dependency-versions-which-are-known-to-be-t.patch
(from rev 1021673,
python-poetry/trunk/0001-Suppress-dependency-versions-which-are-known-to-be-t.patch)
python-poetry/repos/community-any/0001-tests-cleanup-cache-and-http-usage.patch
(from rev 1021673,
python-poetry/trunk/0001-tests-cleanup-cache-and-http-usage.patch)
python-poetry/repos/community-any/PKGBUILD
(from rev 1021673, python-poetry/trunk/PKGBUILD)
python-poetry/repos/community-any/poetry-completions-generator
(from rev 1021673, python-poetry/trunk/poetry-completions-generator)
Deleted:
python-poetry/repos/community-any/0001-Suppress-dependency-versions-which-are-known-to-be-t.patch
python-poetry/repos/community-any/0001-tests-cleanup-cache-and-http-usage.patch
python-poetry/repos/community-any/PKGBUILD
python-poetry/repos/community-any/poetry-completions-generator
-+
0001-Suppress-dependency-versions-which-are-known-to-be-t.patch | 106
0001-tests-cleanup-cache-and-http-usage.patch | 1116
+-
PKGBUILD| 158 -
poetry-completions-generator| 30
4 files changed, 705 insertions(+), 705 deletions(-)
Deleted: 0001-Suppress-dependency-versions-which-are-known-to-be-t.patch
===
--- 0001-Suppress-dependency-versions-which-are-known-to-be-t.patch
2021-09-22 20:38:57 UTC (rev 1021673)
+++ 0001-Suppress-dependency-versions-which-are-known-to-be-t.patch
2021-09-22 20:39:11 UTC (rev 1021674)
@@ -1,53 +0,0 @@
-From cc5b938f7f9e3c536f4a60c35cdd2085b3933618 Mon Sep 17 00:00:00 2001
-From: Eli Schwartz
-Date: Mon, 27 Apr 2020 21:51:57 -0400
-Subject: [PATCH] Fix completely broken dependencies.
-
-poetry habitually engages in:
-- dependency versions which are known to be too pessimistic
-- multiple editions of dependencies per python version
-
-The former all work just fine in reported use and should not be pinned; we
-package versions in Arch which are "too new". This is what unittests are
-for, anyway.
-
-The latter tries to enforce minimum versions of dependencies, but pins
-it twice, once with more relaxed pinning for older versions of python.
-If an old version works, it works irrespective of the python version,
-and you don't need to use minimum requirements as your mallet to force
-people to upgrade to the latest version anyway.
-https://github.com/dephell/dephell/issues/330
- pyproject.toml | 11 ++-
- 1 file changed, 2 insertions(+), 9 deletions(-)
-
-diff --git a/pyproject.toml b/pyproject.toml
-index 8c1f137..81ebc89 100644
a/pyproject.toml
-+++ b/pyproject.toml
-@@ -51,20 +51,13 @@ futures = { version = "^3.3.0", python = "~2.7" }
- glob2 = { version = "^0.6", python = "~2.7" }
- # functools32 is needed for Python 2.7
- functools32 = { version = "^3.2.3", python = "~2.7" }
--keyring = [
--{ version = "^18.0.1", python = "~2.7" },
--{ version = "^20.0.1", python = "~3.5" },
--{ version = "^21.2.0", python = "^3.6" }
--]
-+keyring = "*"
- # Use subprocess32 for Python 2.7
- subprocess32 = { version = "^3.5", python = "~2.7" }
- importlib-metadata = {version = "^1.6.0", python = "<3.8"}
-
- [tool.poetry.dev-dependencies]
--pytest = [
--{version = "^4.1", python = "<3.5"},
--{version = "^5.4.3", python = ">=3.5"}
--]
-+pytest = { version = ">=4.1" }
- pytest-cov = "^2.5"
- pytest-mock = "^1.9"
- pre-commit = { version = "^2.6", python = "^3.6.1" }
---
-2.28.0
-
Copied:
python-poetry/repos/community-any/0001-Suppress-dependency-versions-which-are-known-to-be-t.patch
(from rev 1021673,
python-poetry/trunk/0001-Suppress-dependency-versions-which-are-known-to-be-t.patch)
===
--- 0001-Suppress-dependency-versions-which-are-known-to-be-t.patch
(rev 0)
+++ 0001-Suppress-dependency-versions-which-are-known-to-be-t.patch
2021-09-22 20:39:11 UTC (rev 1021674)
@@ -0,0 +1,53 @@
+From cc5b938f7f9e3c536f4a60c35cdd2085b3933618 Mon Sep 17 00:00:00 2001
+From: Eli Schwartz
+Date: Mon, 27 Apr 2020 21:51:57 -0400
+Subject: [PATCH] Fix completely broken dependencies.
+
+poetry habitually engages in:
+- dependency versions which are known to be too pessimistic
+- multiple editions of dependencies per python version
+
+The former all work just fine in reported use and should not be pinned; we
+package versions in Arch which are "too new". This is what unittests are
+for, anyway.
+
+The latter tries to enforce minimum versions of dependencies, but pins
+it twice, once with more relaxed pinning for older versions of python.
+If an old version works, it
[arch-commits] Commit in python-poetry/repos/community-any (8 files)
Date: Monday, September 20, 2021 @ 20:29:01
Author: svenstaro
Revision: 1019698
archrelease: copy trunk to community-any
Added:
python-poetry/repos/community-any/0001-Suppress-dependency-versions-which-are-known-to-be-t.patch
(from rev 1019697,
python-poetry/trunk/0001-Suppress-dependency-versions-which-are-known-to-be-t.patch)
python-poetry/repos/community-any/0001-tests-cleanup-cache-and-http-usage.patch
(from rev 1019697,
python-poetry/trunk/0001-tests-cleanup-cache-and-http-usage.patch)
python-poetry/repos/community-any/PKGBUILD
(from rev 1019697, python-poetry/trunk/PKGBUILD)
python-poetry/repos/community-any/poetry-completions-generator
(from rev 1019697, python-poetry/trunk/poetry-completions-generator)
Deleted:
python-poetry/repos/community-any/0001-Suppress-dependency-versions-which-are-known-to-be-t.patch
python-poetry/repos/community-any/0001-tests-cleanup-cache-and-http-usage.patch
python-poetry/repos/community-any/PKGBUILD
python-poetry/repos/community-any/poetry-completions-generator
-+
0001-Suppress-dependency-versions-which-are-known-to-be-t.patch | 106
0001-tests-cleanup-cache-and-http-usage.patch | 1116
+-
PKGBUILD| 158 -
poetry-completions-generator| 30
4 files changed, 705 insertions(+), 705 deletions(-)
Deleted: 0001-Suppress-dependency-versions-which-are-known-to-be-t.patch
===
--- 0001-Suppress-dependency-versions-which-are-known-to-be-t.patch
2021-09-20 20:28:50 UTC (rev 1019697)
+++ 0001-Suppress-dependency-versions-which-are-known-to-be-t.patch
2021-09-20 20:29:01 UTC (rev 1019698)
@@ -1,53 +0,0 @@
-From cc5b938f7f9e3c536f4a60c35cdd2085b3933618 Mon Sep 17 00:00:00 2001
-From: Eli Schwartz
-Date: Mon, 27 Apr 2020 21:51:57 -0400
-Subject: [PATCH] Fix completely broken dependencies.
-
-poetry habitually engages in:
-- dependency versions which are known to be too pessimistic
-- multiple editions of dependencies per python version
-
-The former all work just fine in reported use and should not be pinned; we
-package versions in Arch which are "too new". This is what unittests are
-for, anyway.
-
-The latter tries to enforce minimum versions of dependencies, but pins
-it twice, once with more relaxed pinning for older versions of python.
-If an old version works, it works irrespective of the python version,
-and you don't need to use minimum requirements as your mallet to force
-people to upgrade to the latest version anyway.
-https://github.com/dephell/dephell/issues/330
- pyproject.toml | 11 ++-
- 1 file changed, 2 insertions(+), 9 deletions(-)
-
-diff --git a/pyproject.toml b/pyproject.toml
-index 8c1f137..81ebc89 100644
a/pyproject.toml
-+++ b/pyproject.toml
-@@ -51,20 +51,13 @@ futures = { version = "^3.3.0", python = "~2.7" }
- glob2 = { version = "^0.6", python = "~2.7" }
- # functools32 is needed for Python 2.7
- functools32 = { version = "^3.2.3", python = "~2.7" }
--keyring = [
--{ version = "^18.0.1", python = "~2.7" },
--{ version = "^20.0.1", python = "~3.5" },
--{ version = "^21.2.0", python = "^3.6" }
--]
-+keyring = "*"
- # Use subprocess32 for Python 2.7
- subprocess32 = { version = "^3.5", python = "~2.7" }
- importlib-metadata = {version = "^1.6.0", python = "<3.8"}
-
- [tool.poetry.dev-dependencies]
--pytest = [
--{version = "^4.1", python = "<3.5"},
--{version = "^5.4.3", python = ">=3.5"}
--]
-+pytest = { version = ">=4.1" }
- pytest-cov = "^2.5"
- pytest-mock = "^1.9"
- pre-commit = { version = "^2.6", python = "^3.6.1" }
---
-2.28.0
-
Copied:
python-poetry/repos/community-any/0001-Suppress-dependency-versions-which-are-known-to-be-t.patch
(from rev 1019697,
python-poetry/trunk/0001-Suppress-dependency-versions-which-are-known-to-be-t.patch)
===
--- 0001-Suppress-dependency-versions-which-are-known-to-be-t.patch
(rev 0)
+++ 0001-Suppress-dependency-versions-which-are-known-to-be-t.patch
2021-09-20 20:29:01 UTC (rev 1019698)
@@ -0,0 +1,53 @@
+From cc5b938f7f9e3c536f4a60c35cdd2085b3933618 Mon Sep 17 00:00:00 2001
+From: Eli Schwartz
+Date: Mon, 27 Apr 2020 21:51:57 -0400
+Subject: [PATCH] Fix completely broken dependencies.
+
+poetry habitually engages in:
+- dependency versions which are known to be too pessimistic
+- multiple editions of dependencies per python version
+
+The former all work just fine in reported use and should not be pinned; we
+package versions in Arch which are "too new". This is what unittests are
+for, anyway.
+
+The latter tries to enforce minimum versions of dependencies, but pins
+it twice, once with more relaxed pinning for older versions of python.
+If an old version works, it works
[arch-commits] Commit in python-poetry/repos/community-any (8 files)
Date: Saturday, August 21, 2021 @ 19:27:53
Author: svenstaro
Revision: 1004172
archrelease: copy trunk to community-any
Added:
python-poetry/repos/community-any/0001-Suppress-dependency-versions-which-are-known-to-be-t.patch
(from rev 1004171,
python-poetry/trunk/0001-Suppress-dependency-versions-which-are-known-to-be-t.patch)
python-poetry/repos/community-any/0001-tests-cleanup-cache-and-http-usage.patch
(from rev 1004171,
python-poetry/trunk/0001-tests-cleanup-cache-and-http-usage.patch)
python-poetry/repos/community-any/PKGBUILD
(from rev 1004171, python-poetry/trunk/PKGBUILD)
python-poetry/repos/community-any/poetry-completions-generator
(from rev 1004171, python-poetry/trunk/poetry-completions-generator)
Deleted:
python-poetry/repos/community-any/0001-Suppress-dependency-versions-which-are-known-to-be-t.patch
python-poetry/repos/community-any/0001-tests-cleanup-cache-and-http-usage.patch
python-poetry/repos/community-any/PKGBUILD
python-poetry/repos/community-any/poetry-completions-generator
-+
0001-Suppress-dependency-versions-which-are-known-to-be-t.patch | 106
0001-tests-cleanup-cache-and-http-usage.patch | 1116
+-
PKGBUILD| 158 -
poetry-completions-generator| 30
4 files changed, 705 insertions(+), 705 deletions(-)
Deleted: 0001-Suppress-dependency-versions-which-are-known-to-be-t.patch
===
--- 0001-Suppress-dependency-versions-which-are-known-to-be-t.patch
2021-08-21 19:27:46 UTC (rev 1004171)
+++ 0001-Suppress-dependency-versions-which-are-known-to-be-t.patch
2021-08-21 19:27:53 UTC (rev 1004172)
@@ -1,53 +0,0 @@
-From cc5b938f7f9e3c536f4a60c35cdd2085b3933618 Mon Sep 17 00:00:00 2001
-From: Eli Schwartz
-Date: Mon, 27 Apr 2020 21:51:57 -0400
-Subject: [PATCH] Fix completely broken dependencies.
-
-poetry habitually engages in:
-- dependency versions which are known to be too pessimistic
-- multiple editions of dependencies per python version
-
-The former all work just fine in reported use and should not be pinned; we
-package versions in Arch which are "too new". This is what unittests are
-for, anyway.
-
-The latter tries to enforce minimum versions of dependencies, but pins
-it twice, once with more relaxed pinning for older versions of python.
-If an old version works, it works irrespective of the python version,
-and you don't need to use minimum requirements as your mallet to force
-people to upgrade to the latest version anyway.
-https://github.com/dephell/dephell/issues/330
- pyproject.toml | 11 ++-
- 1 file changed, 2 insertions(+), 9 deletions(-)
-
-diff --git a/pyproject.toml b/pyproject.toml
-index 8c1f137..81ebc89 100644
a/pyproject.toml
-+++ b/pyproject.toml
-@@ -51,20 +51,13 @@ futures = { version = "^3.3.0", python = "~2.7" }
- glob2 = { version = "^0.6", python = "~2.7" }
- # functools32 is needed for Python 2.7
- functools32 = { version = "^3.2.3", python = "~2.7" }
--keyring = [
--{ version = "^18.0.1", python = "~2.7" },
--{ version = "^20.0.1", python = "~3.5" },
--{ version = "^21.2.0", python = "^3.6" }
--]
-+keyring = "*"
- # Use subprocess32 for Python 2.7
- subprocess32 = { version = "^3.5", python = "~2.7" }
- importlib-metadata = {version = "^1.6.0", python = "<3.8"}
-
- [tool.poetry.dev-dependencies]
--pytest = [
--{version = "^4.1", python = "<3.5"},
--{version = "^5.4.3", python = ">=3.5"}
--]
-+pytest = { version = ">=4.1" }
- pytest-cov = "^2.5"
- pytest-mock = "^1.9"
- pre-commit = { version = "^2.6", python = "^3.6.1" }
---
-2.28.0
-
Copied:
python-poetry/repos/community-any/0001-Suppress-dependency-versions-which-are-known-to-be-t.patch
(from rev 1004171,
python-poetry/trunk/0001-Suppress-dependency-versions-which-are-known-to-be-t.patch)
===
--- 0001-Suppress-dependency-versions-which-are-known-to-be-t.patch
(rev 0)
+++ 0001-Suppress-dependency-versions-which-are-known-to-be-t.patch
2021-08-21 19:27:53 UTC (rev 1004172)
@@ -0,0 +1,53 @@
+From cc5b938f7f9e3c536f4a60c35cdd2085b3933618 Mon Sep 17 00:00:00 2001
+From: Eli Schwartz
+Date: Mon, 27 Apr 2020 21:51:57 -0400
+Subject: [PATCH] Fix completely broken dependencies.
+
+poetry habitually engages in:
+- dependency versions which are known to be too pessimistic
+- multiple editions of dependencies per python version
+
+The former all work just fine in reported use and should not be pinned; we
+package versions in Arch which are "too new". This is what unittests are
+for, anyway.
+
+The latter tries to enforce minimum versions of dependencies, but pins
+it twice, once with more relaxed pinning for older versions of python.
+If an old version works, it works
[arch-commits] Commit in python-poetry/repos/community-any (8 files)
Date: Wednesday, June 30, 2021 @ 03:26:40
Author: eschwartz
Revision: 967914
archrelease: copy trunk to community-any
Added:
python-poetry/repos/community-any/0001-Suppress-dependency-versions-which-are-known-to-be-t.patch
(from rev 967913,
python-poetry/trunk/0001-Suppress-dependency-versions-which-are-known-to-be-t.patch)
python-poetry/repos/community-any/0001-tests-cleanup-cache-and-http-usage.patch
(from rev 967913,
python-poetry/trunk/0001-tests-cleanup-cache-and-http-usage.patch)
python-poetry/repos/community-any/PKGBUILD
(from rev 967913, python-poetry/trunk/PKGBUILD)
python-poetry/repos/community-any/poetry-completions-generator
(from rev 967913, python-poetry/trunk/poetry-completions-generator)
Deleted:
python-poetry/repos/community-any/0001-Suppress-dependency-versions-which-are-known-to-be-t.patch
python-poetry/repos/community-any/0001-tests-cleanup-cache-and-http-usage.patch
python-poetry/repos/community-any/PKGBUILD
python-poetry/repos/community-any/poetry-completions-generator
-+
0001-Suppress-dependency-versions-which-are-known-to-be-t.patch | 106
0001-tests-cleanup-cache-and-http-usage.patch | 1116
+-
PKGBUILD| 158 -
poetry-completions-generator| 30
4 files changed, 705 insertions(+), 705 deletions(-)
Deleted: 0001-Suppress-dependency-versions-which-are-known-to-be-t.patch
===
--- 0001-Suppress-dependency-versions-which-are-known-to-be-t.patch
2021-06-30 03:26:15 UTC (rev 967913)
+++ 0001-Suppress-dependency-versions-which-are-known-to-be-t.patch
2021-06-30 03:26:40 UTC (rev 967914)
@@ -1,53 +0,0 @@
-From cc5b938f7f9e3c536f4a60c35cdd2085b3933618 Mon Sep 17 00:00:00 2001
-From: Eli Schwartz
-Date: Mon, 27 Apr 2020 21:51:57 -0400
-Subject: [PATCH] Fix completely broken dependencies.
-
-poetry habitually engages in:
-- dependency versions which are known to be too pessimistic
-- multiple editions of dependencies per python version
-
-The former all work just fine in reported use and should not be pinned; we
-package versions in Arch which are "too new". This is what unittests are
-for, anyway.
-
-The latter tries to enforce minimum versions of dependencies, but pins
-it twice, once with more relaxed pinning for older versions of python.
-If an old version works, it works irrespective of the python version,
-and you don't need to use minimum requirements as your mallet to force
-people to upgrade to the latest version anyway.
-https://github.com/dephell/dephell/issues/330
- pyproject.toml | 11 ++-
- 1 file changed, 2 insertions(+), 9 deletions(-)
-
-diff --git a/pyproject.toml b/pyproject.toml
-index 8c1f137..81ebc89 100644
a/pyproject.toml
-+++ b/pyproject.toml
-@@ -51,20 +51,13 @@ futures = { version = "^3.3.0", python = "~2.7" }
- glob2 = { version = "^0.6", python = "~2.7" }
- # functools32 is needed for Python 2.7
- functools32 = { version = "^3.2.3", python = "~2.7" }
--keyring = [
--{ version = "^18.0.1", python = "~2.7" },
--{ version = "^20.0.1", python = "~3.5" },
--{ version = "^21.2.0", python = "^3.6" }
--]
-+keyring = "*"
- # Use subprocess32 for Python 2.7
- subprocess32 = { version = "^3.5", python = "~2.7" }
- importlib-metadata = {version = "^1.6.0", python = "<3.8"}
-
- [tool.poetry.dev-dependencies]
--pytest = [
--{version = "^4.1", python = "<3.5"},
--{version = "^5.4.3", python = ">=3.5"}
--]
-+pytest = { version = ">=4.1" }
- pytest-cov = "^2.5"
- pytest-mock = "^1.9"
- pre-commit = { version = "^2.6", python = "^3.6.1" }
---
-2.28.0
-
Copied:
python-poetry/repos/community-any/0001-Suppress-dependency-versions-which-are-known-to-be-t.patch
(from rev 967913,
python-poetry/trunk/0001-Suppress-dependency-versions-which-are-known-to-be-t.patch)
===
--- 0001-Suppress-dependency-versions-which-are-known-to-be-t.patch
(rev 0)
+++ 0001-Suppress-dependency-versions-which-are-known-to-be-t.patch
2021-06-30 03:26:40 UTC (rev 967914)
@@ -0,0 +1,53 @@
+From cc5b938f7f9e3c536f4a60c35cdd2085b3933618 Mon Sep 17 00:00:00 2001
+From: Eli Schwartz
+Date: Mon, 27 Apr 2020 21:51:57 -0400
+Subject: [PATCH] Fix completely broken dependencies.
+
+poetry habitually engages in:
+- dependency versions which are known to be too pessimistic
+- multiple editions of dependencies per python version
+
+The former all work just fine in reported use and should not be pinned; we
+package versions in Arch which are "too new". This is what unittests are
+for, anyway.
+
+The latter tries to enforce minimum versions of dependencies, but pins
+it twice, once with more relaxed pinning for older versions of python.
+If an old version works, it works irrespective
[arch-commits] Commit in python-poetry/repos/community-any (8 files)
Date: Thursday, April 15, 2021 @ 02:16:14
Author: eschwartz
Revision: 918938
archrelease: copy trunk to community-any
Added:
python-poetry/repos/community-any/0001-Suppress-dependency-versions-which-are-known-to-be-t.patch
(from rev 918937,
python-poetry/trunk/0001-Suppress-dependency-versions-which-are-known-to-be-t.patch)
python-poetry/repos/community-any/0001-tests-cleanup-cache-and-http-usage.patch
(from rev 918937,
python-poetry/trunk/0001-tests-cleanup-cache-and-http-usage.patch)
python-poetry/repos/community-any/PKGBUILD
(from rev 918937, python-poetry/trunk/PKGBUILD)
python-poetry/repos/community-any/poetry-completions-generator
(from rev 918937, python-poetry/trunk/poetry-completions-generator)
Deleted:
python-poetry/repos/community-any/0001-Suppress-dependency-versions-which-are-known-to-be-t.patch
python-poetry/repos/community-any/0001-tests-cleanup-cache-and-http-usage.patch
python-poetry/repos/community-any/PKGBUILD
python-poetry/repos/community-any/poetry-completions-generator
-+
0001-Suppress-dependency-versions-which-are-known-to-be-t.patch | 106
0001-tests-cleanup-cache-and-http-usage.patch | 1116
+-
PKGBUILD| 158 -
poetry-completions-generator| 30
4 files changed, 705 insertions(+), 705 deletions(-)
Deleted: 0001-Suppress-dependency-versions-which-are-known-to-be-t.patch
===
--- 0001-Suppress-dependency-versions-which-are-known-to-be-t.patch
2021-04-15 02:15:50 UTC (rev 918937)
+++ 0001-Suppress-dependency-versions-which-are-known-to-be-t.patch
2021-04-15 02:16:14 UTC (rev 918938)
@@ -1,53 +0,0 @@
-From cc5b938f7f9e3c536f4a60c35cdd2085b3933618 Mon Sep 17 00:00:00 2001
-From: Eli Schwartz
-Date: Mon, 27 Apr 2020 21:51:57 -0400
-Subject: [PATCH] Fix completely broken dependencies.
-
-poetry habitually engages in:
-- dependency versions which are known to be too pessimistic
-- multiple editions of dependencies per python version
-
-The former all work just fine in reported use and should not be pinned; we
-package versions in Arch which are "too new". This is what unittests are
-for, anyway.
-
-The latter tries to enforce minimum versions of dependencies, but pins
-it twice, once with more relaxed pinning for older versions of python.
-If an old version works, it works irrespective of the python version,
-and you don't need to use minimum requirements as your mallet to force
-people to upgrade to the latest version anyway.
-https://github.com/dephell/dephell/issues/330
- pyproject.toml | 11 ++-
- 1 file changed, 2 insertions(+), 9 deletions(-)
-
-diff --git a/pyproject.toml b/pyproject.toml
-index 8c1f137..81ebc89 100644
a/pyproject.toml
-+++ b/pyproject.toml
-@@ -51,20 +51,13 @@ futures = { version = "^3.3.0", python = "~2.7" }
- glob2 = { version = "^0.6", python = "~2.7" }
- # functools32 is needed for Python 2.7
- functools32 = { version = "^3.2.3", python = "~2.7" }
--keyring = [
--{ version = "^18.0.1", python = "~2.7" },
--{ version = "^20.0.1", python = "~3.5" },
--{ version = "^21.2.0", python = "^3.6" }
--]
-+keyring = "*"
- # Use subprocess32 for Python 2.7
- subprocess32 = { version = "^3.5", python = "~2.7" }
- importlib-metadata = {version = "^1.6.0", python = "<3.8"}
-
- [tool.poetry.dev-dependencies]
--pytest = [
--{version = "^4.1", python = "<3.5"},
--{version = "^5.4.3", python = ">=3.5"}
--]
-+pytest = { version = ">=4.1" }
- pytest-cov = "^2.5"
- pytest-mock = "^1.9"
- pre-commit = { version = "^2.6", python = "^3.6.1" }
---
-2.28.0
-
Copied:
python-poetry/repos/community-any/0001-Suppress-dependency-versions-which-are-known-to-be-t.patch
(from rev 918937,
python-poetry/trunk/0001-Suppress-dependency-versions-which-are-known-to-be-t.patch)
===
--- 0001-Suppress-dependency-versions-which-are-known-to-be-t.patch
(rev 0)
+++ 0001-Suppress-dependency-versions-which-are-known-to-be-t.patch
2021-04-15 02:16:14 UTC (rev 918938)
@@ -0,0 +1,53 @@
+From cc5b938f7f9e3c536f4a60c35cdd2085b3933618 Mon Sep 17 00:00:00 2001
+From: Eli Schwartz
+Date: Mon, 27 Apr 2020 21:51:57 -0400
+Subject: [PATCH] Fix completely broken dependencies.
+
+poetry habitually engages in:
+- dependency versions which are known to be too pessimistic
+- multiple editions of dependencies per python version
+
+The former all work just fine in reported use and should not be pinned; we
+package versions in Arch which are "too new". This is what unittests are
+for, anyway.
+
+The latter tries to enforce minimum versions of dependencies, but pins
+it twice, once with more relaxed pinning for older versions of python.
+If an old version works, it works irrespective
[arch-commits] Commit in python-poetry/repos/community-any (8 files)
Date: Thursday, March 4, 2021 @ 21:50:39
Author: eschwartz
Revision: 880743
archrelease: copy trunk to community-any
Added:
python-poetry/repos/community-any/0001-Suppress-dependency-versions-which-are-known-to-be-t.patch
(from rev 880742,
python-poetry/trunk/0001-Suppress-dependency-versions-which-are-known-to-be-t.patch)
python-poetry/repos/community-any/0001-tests-cleanup-cache-and-http-usage.patch
(from rev 880742,
python-poetry/trunk/0001-tests-cleanup-cache-and-http-usage.patch)
python-poetry/repos/community-any/PKGBUILD
(from rev 880742, python-poetry/trunk/PKGBUILD)
python-poetry/repos/community-any/poetry-completions-generator
(from rev 880742, python-poetry/trunk/poetry-completions-generator)
Deleted:
python-poetry/repos/community-any/0001-Suppress-dependency-versions-which-are-known-to-be-t.patch
python-poetry/repos/community-any/0001-tests-cleanup-cache-and-http-usage.patch
python-poetry/repos/community-any/PKGBUILD
python-poetry/repos/community-any/poetry-completions-generator
-+
0001-Suppress-dependency-versions-which-are-known-to-be-t.patch | 106
0001-tests-cleanup-cache-and-http-usage.patch | 1116
+-
PKGBUILD| 158 -
poetry-completions-generator| 30
4 files changed, 705 insertions(+), 705 deletions(-)
Deleted: 0001-Suppress-dependency-versions-which-are-known-to-be-t.patch
===
--- 0001-Suppress-dependency-versions-which-are-known-to-be-t.patch
2021-03-04 21:50:14 UTC (rev 880742)
+++ 0001-Suppress-dependency-versions-which-are-known-to-be-t.patch
2021-03-04 21:50:39 UTC (rev 880743)
@@ -1,53 +0,0 @@
-From cc5b938f7f9e3c536f4a60c35cdd2085b3933618 Mon Sep 17 00:00:00 2001
-From: Eli Schwartz
-Date: Mon, 27 Apr 2020 21:51:57 -0400
-Subject: [PATCH] Fix completely broken dependencies.
-
-poetry habitually engages in:
-- dependency versions which are known to be too pessimistic
-- multiple editions of dependencies per python version
-
-The former all work just fine in reported use and should not be pinned; we
-package versions in Arch which are "too new". This is what unittests are
-for, anyway.
-
-The latter tries to enforce minimum versions of dependencies, but pins
-it twice, once with more relaxed pinning for older versions of python.
-If an old version works, it works irrespective of the python version,
-and you don't need to use minimum requirements as your mallet to force
-people to upgrade to the latest version anyway.
-https://github.com/dephell/dephell/issues/330
- pyproject.toml | 11 ++-
- 1 file changed, 2 insertions(+), 9 deletions(-)
-
-diff --git a/pyproject.toml b/pyproject.toml
-index 8c1f137..81ebc89 100644
a/pyproject.toml
-+++ b/pyproject.toml
-@@ -51,20 +51,13 @@ futures = { version = "^3.3.0", python = "~2.7" }
- glob2 = { version = "^0.6", python = "~2.7" }
- # functools32 is needed for Python 2.7
- functools32 = { version = "^3.2.3", python = "~2.7" }
--keyring = [
--{ version = "^18.0.1", python = "~2.7" },
--{ version = "^20.0.1", python = "~3.5" },
--{ version = "^21.2.0", python = "^3.6" }
--]
-+keyring = "*"
- # Use subprocess32 for Python 2.7
- subprocess32 = { version = "^3.5", python = "~2.7" }
- importlib-metadata = {version = "^1.6.0", python = "<3.8"}
-
- [tool.poetry.dev-dependencies]
--pytest = [
--{version = "^4.1", python = "<3.5"},
--{version = "^5.4.3", python = ">=3.5"}
--]
-+pytest = { version = ">=4.1" }
- pytest-cov = "^2.5"
- pytest-mock = "^1.9"
- pre-commit = { version = "^2.6", python = "^3.6.1" }
---
-2.28.0
-
Copied:
python-poetry/repos/community-any/0001-Suppress-dependency-versions-which-are-known-to-be-t.patch
(from rev 880742,
python-poetry/trunk/0001-Suppress-dependency-versions-which-are-known-to-be-t.patch)
===
--- 0001-Suppress-dependency-versions-which-are-known-to-be-t.patch
(rev 0)
+++ 0001-Suppress-dependency-versions-which-are-known-to-be-t.patch
2021-03-04 21:50:39 UTC (rev 880743)
@@ -0,0 +1,53 @@
+From cc5b938f7f9e3c536f4a60c35cdd2085b3933618 Mon Sep 17 00:00:00 2001
+From: Eli Schwartz
+Date: Mon, 27 Apr 2020 21:51:57 -0400
+Subject: [PATCH] Fix completely broken dependencies.
+
+poetry habitually engages in:
+- dependency versions which are known to be too pessimistic
+- multiple editions of dependencies per python version
+
+The former all work just fine in reported use and should not be pinned; we
+package versions in Arch which are "too new". This is what unittests are
+for, anyway.
+
+The latter tries to enforce minimum versions of dependencies, but pins
+it twice, once with more relaxed pinning for older versions of python.
+If an old version works, it works irrespective
