Github messages for voidlinux
 help / color / mirror / Atom feed
From: NeelChotai <NeelChotai@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] New package: python3-pydantic-1.8.2
Date: Fri, 15 Oct 2021 14:03:31 +0200	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-33566@inbox.vuxu.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1606 bytes --]

There is a new pull request by NeelChotai against master on the void-packages repository

https://github.com/NeelChotai/void-packages pydantic
https://github.com/void-linux/void-packages/pull/33566

New package: python3-pydantic-1.8.2
<!-- Mark items with [x] where applicable -->

#### General
- [ ] This is a new package and it conforms to the [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements)

#### Have the results of the proposed changes been tested?
- [ ] I use the packages affected by the proposed changes on a regular basis and confirm this PR works for me
- [ x ] I generally don't use the affected packages but briefly tested this PR

<!--
If GitHub CI cannot be used to validate the build result (for example, if the
build is likely to take several hours), make sure to
[skip CI](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration).
When skipping CI, uncomment and fill out the following section.
Note: for builds that are likely to complete in less than 2 hours, it is not
acceptable to skip CI.
-->
<!-- 
#### Does it build and run successfully? 
(Please choose at least one native build and, if supported, at least one cross build. More are better.)
- [ ] I built this PR locally for my native architecture, (ARCH-LIBC)
- [ ] I built this PR locally for these architectures (if supported. mark crossbuilds):
  - [ ] aarch64-musl
  - [ ] armv7l
  - [ ] armv6l-musl
-->


A patch file from https://github.com/void-linux/void-packages/pull/33566.patch is attached

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-pydantic-33566.patch --]
[-- Type: text/x-diff, Size: 1308 bytes --]

From ff1a21ea8854d99951b556e8e45488e9932d61be Mon Sep 17 00:00:00 2001
From: Neel Chotai <neel@chot.ai>
Date: Sun, 21 Mar 2021 01:33:10 +0000
Subject: [PATCH] New package: python3-pydantic-1.8.2

---
 srcpkgs/python3-pydantic/template | 22 ++++++++++++++++++++++
 1 file changed, 22 insertions(+)
 create mode 100644 srcpkgs/python3-pydantic/template

diff --git a/srcpkgs/python3-pydantic/template b/srcpkgs/python3-pydantic/template
new file mode 100644
index 000000000000..04aa511c55ab
--- /dev/null
+++ b/srcpkgs/python3-pydantic/template
@@ -0,0 +1,22 @@
+# Template file for 'python3-pydantic'
+pkgname=python3-pydantic
+version=1.8.2
+revision=1
+wrksrc="pydantic-${version}"
+build_style=python3-module
+hostmakedepends="python3-setuptools python3-typing_extensions"
+depends="python3 python3-typing_extensions
+$(vopt_if email python3-email-validator)"
+checkdepends="python3-pip python3-pytest-mock"
+short_desc="Data parsing and validation using Python type hints"
+maintainer="Neel Chotai <neel@chot.ai>"
+license="MIT"
+homepage="https://github.com/samuelcolvin/pydantic"
+distfiles="https://github.com/samuelcolvin/pydantic/archive/v${version}.tar.gz"
+checksum=4419cc01218f54ce54976a446c81513bd5a1424923b98817d6dcec260c143783
+
+build_options="email"
+
+post_install() {
+	vlicense LICENSE
+}

             reply	other threads:[~2021-10-15 12:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-15 12:03 NeelChotai [this message]
2021-10-15 16:04 ` NeelChotai
2022-06-08  2:12 ` [nomerge: wait for >1.8.2] " github-actions
2022-06-22  2:13 ` [PR PATCH] [Closed]: " github-actions

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-33566@inbox.vuxu.org \
    --to=neelchotai@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).