From: Lars-Dominik Braun <ldb@leibniz-psychology.org>
To: Leo Famulari <leo@famulari.name>
Cc: 40321-done@debbugs.gnu.org
Subject: [bug#40321] [PATCH] Add python-tortoise-orm
Date: Wed, 1 Apr 2020 08:09:39 +0200 [thread overview]
Message-ID: <20200401060939.GA3075@zpidnp36> (raw)
In-Reply-To: <20200331142716.GA2134@jasmine.lan>
[-- Attachment #1: Type: text/plain, Size: 968 bytes --]
Hi,
> > You mean amend tests_require in setup.py?
(that does not work by the way, because the tests really *do* require pytz)
> Not sure... I noticed your comment said that the PyPi source did not
> include the tests. If we built from that source, would the package still
> build, or would the test phase fail somehow?
Yep, the test phase fails.
---snip---
======================================================================
ERROR: tests (unittest.loader._FailedTest)
----------------------------------------------------------------------
ImportError: Failed to import test module: tests
Traceback (most recent call last):
File "/gnu/store/78w7y0lxar70j512iqw8x3nimzj10yga-python-3.7.4/lib/python3.7/unittest/loader.py", line 154, in loadTestsFromName
module = __import__(module_name)
ModuleNotFoundError: No module named 'tests'
---snap---
I guess we could pass `#:tests? #f`, but is that worth it? pytz is just a
native input and not propagated.
Lars
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
next prev parent reply other threads:[~2020-04-01 6:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-30 6:43 [bug#40321] [PATCH] Add python-tortoise-orm Lars-Dominik Braun
2020-03-30 18:52 ` bug#40321: " Leo Famulari
2020-03-31 6:04 ` [bug#40321] " Lars-Dominik Braun
2020-03-31 14:27 ` Leo Famulari
2020-04-01 6:09 ` Lars-Dominik Braun [this message]
2020-04-01 16:09 ` Leo Famulari
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=20200401060939.GA3075@zpidnp36 \
--to=ldb@leibniz-psychology.org \
--cc=40321-done@debbugs.gnu.org \
--cc=leo@famulari.name \
/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.