From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Scott Fan <fancp2007@gmail.com>
Cc: buildroot@buildroot.org,
James Hilliard <james.hilliard1@gmail.com>,
Asaf Kahlon <asafka7@gmail.com>
Subject: Re: [Buildroot] [PATCH v3] package/python-pgcopy: new package
Date: Wed, 30 Oct 2024 14:35:55 +0100 [thread overview]
Message-ID: <20241030143555.5a69a4bf@windsurf> (raw)
In-Reply-To: <CAFkzVZZc=i02CTkxRHSXwrQb=BALPtxD0sSQudCoLtVOj+qfYg@mail.gmail.com>
Hello Scott,
James: question for you below.
On Wed, 30 Oct 2024 21:28:24 +0800
Scott Fan <fancp2007@gmail.com> wrote:
> > Are you sure python-psycopg2 and python-pytz are build-time
> > dependencies? I.e are they needed during the build, or only at runtime?
>
> In pgcopy's setup.py file, has the next line:
> install_requires=["psycopg2", "pytz"]
>
> So I understand, those are build-time dependencies.
I'll let James comment on this, but I believe install_requires are
run-time dependencies, not build-time dependencies.
> Meanwhile, the psycopg2 module depends on postgres.
> Do I need to remove postgres dependency from this package?
If you select BR2_PACKAGE_PYTHON_PSYCOPG2, it will automatically select
BR2_PACKAGE_POSTGRESQL.
Now whether you need postgresql as a build-time dependency or not
depends on whether your package is building native code that links
against Postgresql libraries.
> > What is this hook needed? A small comment would be useful.
>
> The py2.py file is just for Python 2, it will cause compilation errors
> in Buildroot:
> File "/usr/lib/python3.12/site-packages/pgcopy/errors/py2.py", line 19
> raise newexc, None, sys.exc_info()[2]
> ^
> SyntaxError: invalid syntax
>
> I'll add a comment before the hook definition.
Yes, good.
> This hook will be removed, i copied it from package/python-psycopg2,
> It is redundant.
Thanks!
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2024-10-30 13:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-14 1:40 [Buildroot] [PATCH] package/python-pgcopy: new package Scott Fan
2024-10-24 0:28 ` [Buildroot] [PATCH v2] " Scott Fan
2024-10-29 5:47 ` [Buildroot] [PATCH v3] " Scott Fan
2024-10-29 18:50 ` Thomas Petazzoni via buildroot
2024-10-30 13:28 ` Scott Fan
2024-10-30 13:35 ` Thomas Petazzoni via buildroot [this message]
2024-10-30 13:43 ` [Buildroot] [PATCH v4] " Scott Fan
2024-10-30 14:59 ` [Buildroot] [PATCH v5 1/2] package/python-psycopg2: add config dependencies from postgresql Scott Fan
2024-10-30 14:59 ` [Buildroot] [PATCH v5 2/2] package/python-pgcopy: new package Scott Fan
2024-10-30 15:11 ` [Buildroot] [PATCH v2] package/python-psycopg2: add config dependencies from postgresql Scott Fan
2024-12-04 20:12 ` Arnout Vandecappelle via buildroot
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=20241030143555.5a69a4bf@windsurf \
--to=buildroot@buildroot.org \
--cc=asafka7@gmail.com \
--cc=fancp2007@gmail.com \
--cc=james.hilliard1@gmail.com \
--cc=thomas.petazzoni@bootlin.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox