[1/2] package/python-entrypoints: new package
diff mbox series

Message ID 20191021134031.20586-4-asafka7@gmail.com
State New
Headers show
Series
  • [1/2] package/python-entrypoints: new package
Related show

Commit Message

Asaf Kahlon Oct. 21, 2019, 1:40 p.m. UTC
Signed-off-by: Asaf Kahlon <asafka7@gmail.com>
---
 package/Config.in                                  |  1 +
 package/python-entrypoints/Config.in               |  6 ++++++
 package/python-entrypoints/python-entrypoints.hash |  5 +++++
 package/python-entrypoints/python-entrypoints.mk   | 14 ++++++++++++++
 4 files changed, 26 insertions(+)
 create mode 100644 package/python-entrypoints/Config.in
 create mode 100644 package/python-entrypoints/python-entrypoints.hash
 create mode 100644 package/python-entrypoints/python-entrypoints.mk

Comments

Thomas Petazzoni Oct. 21, 2019, 5:13 p.m. UTC | #1
Hello Asaf,

On Mon, 21 Oct 2019 16:40:24 +0300
Asaf Kahlon <asafka7@gmail.com> wrote:

> Signed-off-by: Asaf Kahlon <asafka7@gmail.com>

Could you send the patches that go together, at the same time ? Here I
had a long list of patches PATCH 1/1, and in the middle of them, this
PATCH 1/2, which I guess goes with "package/python-keyring: bump to
version  19.2.0". Having them sent separately is quite confusing.

Could you make sure to send series as proper series, this would really
makes things a bit easier.

Also, I see you are doing a lot of version bumps for Python packages.
Is it related to the fact that you know receive e-mail notifications
when Python packages are not up to date ? Are we going to see a point
where this stream of patches reduces, or is there just very frequent
update of Python modules happening upstream ?

Thanks!

Thomas
Asaf Kahlon Oct. 21, 2019, 7:01 p.m. UTC | #2
Hello,

On Mon, Oct 21, 2019 at 8:13 PM Thomas Petazzoni
<thomas.petazzoni@bootlin.com> wrote:
>
> Hello Asaf,
>
> On Mon, 21 Oct 2019 16:40:24 +0300
> Asaf Kahlon <asafka7@gmail.com> wrote:
>
> > Signed-off-by: Asaf Kahlon <asafka7@gmail.com>
>
> Could you send the patches that go together, at the same time ? Here I
> had a long list of patches PATCH 1/1, and in the middle of them, this
> PATCH 1/2, which I guess goes with "package/python-keyring: bump to
> version  19.2.0". Having them sent separately is quite confusing.
>
> Could you make sure to send series as proper series, this would really
> makes things a bit easier.

Yes, python-entrypoints was sent together with python-keyring.
In addition, python-zc-lockfile was sent together with python-cherrypy.
Moreover, I now noticed that my series of python-snmp-apps with
snmpclitools earlier
this month seems to be sent separately too. All the other patches I
sent are single patches.
Next time, I'll send the series at the same time.
Do you need me to resend the existing patches or we'll be fine for that round?

>
> Also, I see you are doing a lot of version bumps for Python packages.
> Is it related to the fact that you know receive e-mail notifications
> when Python packages are not up to date ? Are we going to see a point
> where this stream of patches reduces, or is there just very frequent
> update of Python modules happening upstream ?
>

Indeed, I updated the packages mostly because of the new e-mail feature with the
list of outdated packages.
I guess those many bumps happened since the feature is new and we had
a lot to do,
but I think now we're pretty close to the end, so the stream of
patches is going to reduce :)

> Thanks!
>
> Thomas
> --
> Thomas Petazzoni, CTO, Bootlin
> Embedded Linux and Kernel engineering
> https://bootlin.com

Asaf.
Thomas Petazzoni Oct. 21, 2019, 7:19 p.m. UTC | #3
Hello Asaf,

On Mon, 21 Oct 2019 22:01:27 +0300
Asaf Kahlon <asafka7@gmail.com> wrote:

> Yes, python-entrypoints was sent together with python-keyring.

Together, but mixed with the other patches I supposed ?

> In addition, python-zc-lockfile was sent together with python-cherrypy.
> Moreover, I now noticed that my series of python-snmp-apps with
> snmpclitools earlier
> this month seems to be sent separately too. All the other patches I
> sent are single patches.
> Next time, I'll send the series at the same time.
> Do you need me to resend the existing patches or we'll be fine for that round?

No need to resend.

> > Also, I see you are doing a lot of version bumps for Python packages.
> > Is it related to the fact that you know receive e-mail notifications
> > when Python packages are not up to date ? Are we going to see a point
> > where this stream of patches reduces, or is there just very frequent
> > update of Python modules happening upstream ?
> >  
> 
> Indeed, I updated the packages mostly because of the new e-mail feature with the
> list of outdated packages.
> I guess those many bumps happened since the feature is new and we had
> a lot to do, but I think now we're pretty close to the end, so the
> stream of patches is going to reduce :)

Great :-) In any case, thanks for doing this work!

Best regards,

Thomas
Asaf Kahlon Oct. 21, 2019, 7:31 p.m. UTC | #4
Hello,

On Mon, Oct 21, 2019 at 10:20 PM Thomas Petazzoni
<thomas.petazzoni@bootlin.com> wrote:
>
> Hello Asaf,
>
> On Mon, 21 Oct 2019 22:01:27 +0300
> Asaf Kahlon <asafka7@gmail.com> wrote:
>
> > Yes, python-entrypoints was sent together with python-keyring.
>
> Together, but mixed with the other patches I supposed ?
>

Yes.

> > In addition, python-zc-lockfile was sent together with python-cherrypy.
> > Moreover, I now noticed that my series of python-snmp-apps with
> > snmpclitools earlier
> > this month seems to be sent separately too. All the other patches I
> > sent are single patches.
> > Next time, I'll send the series at the same time.
> > Do you need me to resend the existing patches or we'll be fine for that round?
>
> No need to resend.

OK, thanks :)

>
> > > Also, I see you are doing a lot of version bumps for Python packages.
> > > Is it related to the fact that you know receive e-mail notifications
> > > when Python packages are not up to date ? Are we going to see a point
> > > where this stream of patches reduces, or is there just very frequent
> > > update of Python modules happening upstream ?
> > >
> >
> > Indeed, I updated the packages mostly because of the new e-mail feature with the
> > list of outdated packages.
> > I guess those many bumps happened since the feature is new and we had
> > a lot to do, but I think now we're pretty close to the end, so the
> > stream of patches is going to reduce :)
>
> Great :-) In any case, thanks for doing this work!
>
> Best regards,
>
> Thomas
> --
> Thomas Petazzoni, CTO, Bootlin
> Embedded Linux and Kernel engineering
> https://bootlin.com

Asaf.
Thomas Petazzoni Oct. 21, 2019, 9:17 p.m. UTC | #5
On Mon, 21 Oct 2019 22:31:57 +0300
Asaf Kahlon <asafka7@gmail.com> wrote:

> > > Yes, python-entrypoints was sent together with python-keyring.  
> >
> > Together, but mixed with the other patches I supposed ?
> 
> Yes.

That's the problem I guess. When you send a series, just send the
patches of that series. And then separately send the standalone patches
that are not part of the series.

Thanks!

Thomas

Patch
diff mbox series

diff --git a/package/Config.in b/package/Config.in
index c8ff524e83..bdaa310177 100644
--- a/package/Config.in
+++ b/package/Config.in
@@ -897,6 +897,7 @@  menu "External python modules"
 	source "package/python-dpkt/Config.in"
 	source "package/python-ecdsa/Config.in"
 	source "package/python-engineio/Config.in"
+	source "package/python-entrypoints/Config.in"
 	source "package/python-enum/Config.in"
 	source "package/python-enum34/Config.in"
 	source "package/python-falcon/Config.in"
diff --git a/package/python-entrypoints/Config.in b/package/python-entrypoints/Config.in
new file mode 100644
index 0000000000..8253a04591
--- /dev/null
+++ b/package/python-entrypoints/Config.in
@@ -0,0 +1,6 @@ 
+config BR2_PACKAGE_PYTHON_ENTRYPOINTS
+	bool "python-entrypoints"
+	help
+	  Discover and load entry points from installed packages.
+
+	  https://github.com/takluyver/entrypoints
diff --git a/package/python-entrypoints/python-entrypoints.hash b/package/python-entrypoints/python-entrypoints.hash
new file mode 100644
index 0000000000..c645452109
--- /dev/null
+++ b/package/python-entrypoints/python-entrypoints.hash
@@ -0,0 +1,5 @@ 
+# md5, sha256 from https://pypi.org/pypi/entrypoints/json
+md5	c5c61ea2e46a0c50ea08f4af7955a0b1  entrypoints-0.3.tar.gz
+sha256	c70dd71abe5a8c85e55e12c19bd91ccfeec11a6e99044204511f9ed547d48451  entrypoints-0.3.tar.gz
+# Locally computed sha256 checksums
+sha256	de5fcd7349cdf399b0707a2a024833c4704743650133c72d6f0ff7561a03a848  LICENSE
diff --git a/package/python-entrypoints/python-entrypoints.mk b/package/python-entrypoints/python-entrypoints.mk
new file mode 100644
index 0000000000..7ab1b4d64a
--- /dev/null
+++ b/package/python-entrypoints/python-entrypoints.mk
@@ -0,0 +1,14 @@ 
+################################################################################
+#
+# python-entrypoints
+#
+################################################################################
+
+PYTHON_ENTRYPOINTS_VERSION = 0.3
+PYTHON_ENTRYPOINTS_SOURCE = entrypoints-$(PYTHON_ENTRYPOINTS_VERSION).tar.gz
+PYTHON_ENTRYPOINTS_SITE = https://files.pythonhosted.org/packages/b4/ef/063484f1f9ba3081e920ec9972c96664e2edb9fdc3d8669b0e3b8fc0ad7c
+PYTHON_ENTRYPOINTS_SETUP_TYPE = distutils
+PYTHON_ENTRYPOINTS_LICENSE = MIT
+PYTHON_ENTRYPOINTS_LICENSE_FILES = LICENSE
+
+$(eval $(python-package))