Trove classifiers for MicroPython?
Hello everyone, I'm not sure this is the right place to write to propose new trove classifiers for PyPi -- if it's not, what would be the right place? If this is it, then please read below. The MicroPython project is quickly growing and becoming more mature, and as that happens, the number of 3rd-party libraries for it grows. Many of those libraries get uploaded to PyPi, as you can check by searching for "micropython". MicroPython has even its own version of "pip", called "upip", that can be used to install those libraries. However, there is as of yet no way to mark that a library is written for that particular flavor of Python, as there are no trove classifiers for it. I would like to propose adding a number of classifiers to amend that situation: For the MicroPython itself: Programming Language :: Python :: Implementation :: MicroPython For the hardware it runs on: Operating System :: Baremetal Environment :: Microcontroller Environment :: Microcontroller :: PyBoard Environment :: Microcontroller :: ESP8266 Environment :: Microcontroller :: Micro:bit Environment :: Microcontroller :: WiPy Environment :: Microcontroller :: LoPy Environment :: Microcontroller :: OpenMV I'm not sure if the latter makes sense, but it would certainly be nice to be able to indicate in a machine-parseable way on which platforms the code works. What do you think? -- Radomir Dopieralski
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 10/20/2016 05:43 AM, Radomir Dopieralski wrote:
I'm not sure this is the right place to write to propose new trove classifiers for PyPi -- if it's not, what would be the right place? If this is it, then please read below.
This is definitely the correct location: the former 'catalog-sig' list is retired.
The MicroPython project is quickly growing and becoming more mature, and as that happens, the number of 3rd-party libraries for it grows. Many of those libraries get uploaded to PyPi, as you can check by searching for "micropython". MicroPython has even its own version of "pip", called "upip", that can be used to install those libraries.
However, there is as of yet no way to mark that a library is written for that particular flavor of Python, as there are no trove classifiers for it. I would like to propose adding a number of classifiers to amend that situation:
For the MicroPython itself:
Programming Language :: Python :: Implementation :: MicroPython
+1 for this one.
For the hardware it runs on:
Operating System :: Baremetal Environment :: Microcontroller Environment :: Microcontroller :: PyBoard Environment :: Microcontroller :: ESP8266 Environment :: Microcontroller :: Micro:bit Environment :: Microcontroller :: WiPy Environment :: Microcontroller :: LoPy Environment :: Microcontroller :: OpenMV
I'm not sure if the latter makes sense, but it would certainly be nice to be able to indicate in a machine-parseable way on which platforms the code works.
Are there actual binary wheels being uploaded which compiled for specific boards? Or is it that the packages depend at runtime on board-specific features? Tres. - -- =================================================================== Tres Seaver +1 540-429-0999 tseaver@palladion.com Palladion Software "Excellence by Design" http://palladion.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBAgAGBQJYCNk3AAoJEPKpaDSJE9HYsl8P/2VBfoIqIE/NU4+zxfjV4pX5 nwnrnjxjfHEGIibmdhM0wh6CouaqqhaWdmgMKu66UoZVmJFiE/WAPYmHhcC0jHSC Mk699B5+fZATywJp/NweaogpcaJiEvJEpcostD4Z15sfmzYCrrOZ4ylDSPq1+D98 ypQRhRjxjrMu9RxIOOJFOKHbvyHZ+NThAgvF7e7sDG5SVWeEPVN9ga8+F9B6JJjw 0Wgo0G/pTrTikVr/HSAbpkiQZRey4rhaN6hg5y0C4O2M/Sf4zrik0BfC8eWt23HY tIT2EFhr5NR/9JaFYWkgZmrVFf23JJezS/1N6zGVKFIaf7AsCGh1LFy8jZNYuA7P 7uNzPM+9otgPp7Vx5w/rLKQXN2MlUKAZmX1FoUz5MBL3m7RaCctYMbxOaxxjXEJy vORr1r7iOm9kw9YXIuVrtI5X9d+518IQ3Ege4JxhIhi+V90j6ht1wAXoGdLCqYNJ OqrMbayhEatzj9dWu+3P5CrzyEfe2frahdBcms+PT/uDNKXA4SJBEibHYfv16yWb Z26mx3sD3R65ceRl7wCgYy4G3rt1DTro2/LGfm2f92HHdmIHNWJI5sPcJSst9n69 1AdLZU6N/PSS3k5LRLia4GnTVfBJBxphTfywIcP81kHNLUvBvnX5bQhLnYAGL4Yj l3sj1cK2n4dhWhvDLYds =nBUj -----END PGP SIGNATURE-----
Is this the right place to ask for this? It has been over four months already, and there is no action on this. Perhaps there is some more official way to request this that I am missing? On Thu, 20 Oct 2016 11:43:16 +0200 Radomir Dopieralski <radomir@dopieralski.pl> wrote:
Hello everyone,
I'm not sure this is the right place to write to propose new trove classifiers for PyPi -- if it's not, what would be the right place? If this is it, then please read below.
The MicroPython project is quickly growing and becoming more mature, and as that happens, the number of 3rd-party libraries for it grows. Many of those libraries get uploaded to PyPi, as you can check by searching for "micropython". MicroPython has even its own version of "pip", called "upip", that can be used to install those libraries.
However, there is as of yet no way to mark that a library is written for that particular flavor of Python, as there are no trove classifiers for it. I would like to propose adding a number of classifiers to amend that situation:
For the MicroPython itself:
Programming Language :: Python :: Implementation :: MicroPython
For the hardware it runs on:
Operating System :: Baremetal Environment :: Microcontroller Environment :: Microcontroller :: PyBoard Environment :: Microcontroller :: ESP8266 Environment :: Microcontroller :: Micro:bit Environment :: Microcontroller :: WiPy Environment :: Microcontroller :: LoPy Environment :: Microcontroller :: OpenMV
I'm not sure if the latter makes sense, but it would certainly be nice to be able to indicate in a machine-parseable way on which platforms the code works.
What do you think?
-- Radomir Dopieralski
participants (2)
-
Radomir Dopieralski -
Tres Seaver