all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Xinglu Chen <public@yoctocell.xyz>
To: Hartmut Goebel <h.goebel@crazy-compilers.com>, 50724@debbugs.gnu.org
Subject: [bug#50724] [PATCH 3/3] gnu: Add python-zeep.
Date: Tue, 21 Sep 2021 22:16:27 +0200	[thread overview]
Message-ID: <87mto5fzvo.fsf@yoctocell.xyz> (raw)
In-Reply-To: <6514049df6c3b4bfd534252eec1ecce93f66619f.1632251925.git.h.goebel@crazy-compilers.com>

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

On Tue, Sep 21 2021, Hartmut Goebel wrote:

> * gnu/packages/python-web.scm (python-zeep): New variable.
> ---
>  gnu/packages/python-web.scm | 42 +++++++++++++++++++++++++++++++++++++
>  1 file changed, 42 insertions(+)
>
> diff --git a/gnu/packages/python-web.scm b/gnu/packages/python-web.scm
> index 302e5d6459..10507240e1 100644
> --- a/gnu/packages/python-web.scm
> +++ b/gnu/packages/python-web.scm
> @@ -6234,3 +6234,45 @@ communicate with Microsoft Azure Storage services.")
>  or tags from HTML snippets, extract base url from HTML snippets, translate entites
>  on HTML strings, among other things.")
>      (license license:bsd-3)))
> +
> +(define-public python-zeep
> +  (package
> +    (name "python-zeep")
> +    (version "4.1.0")
> +    (source
> +     (origin
> +       (method url-fetch)
> +       (uri (pypi-uri "zeep" version))
> +       (sha256
> +        (base32 "1ranr4hkjd2kbbhxa3is1qlgkankj3sml5gla6bqs0kbvpmg4rsq"))))
> +    (build-system python-build-system)
> +    (propagated-inputs
> +     `(("python-attrs" ,python-attrs)
> +       ("python-cached-property" ,python-cached-property)
> +       ("python-isodate" ,python-isodate)
> +       ("python-lxml" ,python-lxml)
> +       ("python-platformdirs" ,python-platformdirs)
> +       ("python-pytz" ,python-pytz)
> +       ("python-requests" ,python-requests)
> +       ("python-requests-file" ,python-requests-file)
> +       ("python-requests-toolbelt" ,python-requests-toolbelt)))
> +    (native-inputs
> +     `(("python-coverage" ,python-coverage)
> +       ;;("python-flake8" ,python-flake8)
> +       ;; ("python-flake8-blind-except" ,python-flake8-blind-except)
> +       ;; ("python-flake8-debugger" ,python-flake8-debugger)
> +       ;; ("python-flake8-imports" ,python-flake8-imports)
> +       ("python-freezegun" ,python-freezegun)
> +       ;;("python-isort" ,python-isort)

Why are some of these inputs commented out?

> +       ("python-mock" ,python-mock)
> +       ("python-pretend" ,python-pretend)
> +       ("python-pytest" ,python-pytest)
> +       ("python-pytest-asyncio" ,python-pytest-asyncio)
> +       ("python-pytest-cov" ,python-pytest-cov)
> +       ("python-pytest-httpx" ,python-pytest-httpx)

‘python-pytest-httpx’ doesn’t seem to exist; which commit are you basing
these patches off of?  My checkout is based off of commit
5966d48d1c9e48b7098845193469f5b5fe07d540.

This is why people should be using the ‘--base’ flag when invoking ‘git
format-patch’.  :-)

> +       ("python-requests-mock" ,python-requests-mock)))
> +    (home-page "http://docs.python-zeep.org")

Why not HTTPS?

> +    (synopsis "Fast and modern Python SOAP client")
> +    (description "This package provides a fast and modern Python SOAP client
> +based on lxml and requests.")

I would use @code{python-lxml} and @code{python-requests} to make it
clear that these are packages and not just regular words.



[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 861 bytes --]

  reply	other threads:[~2021-09-21 20:17 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-21 19:19 [bug#50724] [PATCH 1/3] gnu: Add python-charset-normalizer Hartmut Goebel
2021-09-21 19:22 ` [bug#50724] [PATCH 2/3] gnu: Add python-platformdirs Hartmut Goebel
2021-09-21 20:12   ` Xinglu Chen
2021-09-23 17:11     ` Hartmut Goebel
2021-09-21 19:22 ` [bug#50724] [PATCH 3/3] gnu: Add python-zeep Hartmut Goebel
2021-09-21 20:16   ` Xinglu Chen [this message]
2021-09-23 17:09     ` Hartmut Goebel

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=87mto5fzvo.fsf@yoctocell.xyz \
    --to=public@yoctocell.xyz \
    --cc=50724@debbugs.gnu.org \
    --cc=h.goebel@crazy-compilers.com \
    /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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.