Re: [Distutils] Trove classifiers for MicroPython?

2017-02-13 Thread Radomir Dopieralski
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  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
___
Distutils-SIG maillist  -  Distutils-SIG@python.org
https://mail.python.org/mailman/listinfo/distutils-sig


Re: [Distutils] Trove classifiers for MicroPython?

2016-10-30 Thread Radomir Dopieralski
I'm sorry for a delay, but I'm not subscribed to this list, and I didn't
receive the reply to my address.

Thu Oct 20 10:48:29 EDT 2016, Tres Seaver:
>On 10/20/2016 05:43 AM, Radomir Dopieralski wrote:

[...]
>> 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?

There is no wheel format for the MicroPython, at this moment. It is possible
to bytecode-compile modules into .mpy files, but those are compatible across
all platforms, as far as I can tell (but not across all versions).

On the other hand, the platforms themselves are not always perfectly
compatible, even though there is an ongoing effort to bring them closer
together, and to make most libraries work on all of the platforms without
modifications.

The Micro:bit platform is a kind of an outlier, since its default libraries are
considerably different from those on other platforms (presumably to make them
it easier to teach) -- which means that practically all hardware-related
libraries need a separate micro:bit version.

The PyBoard platfrom has as "pyb" module, retained for backwards compatibility,
that is specific to it, side by side by the more general "machine" module, that
is present on all platforms (except for the micro:bit) and which should work
the same everywhere.

In addition, different boards have different capabilities. The WiPy and ESP8266
boards have on-board WiFi and networking libraries, the PyBoard and micro:bit
have an accelerometer, the WiPy lacks support for floating point numbers, etc.

-- 
Radomir Dopieralski
___
Distutils-SIG maillist  -  Distutils-SIG@python.org
https://mail.python.org/mailman/listinfo/distutils-sig


Re: [Distutils] Trove classifiers for MicroPython?

2016-10-20 Thread Tres Seaver
-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  tsea...@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-

___
Distutils-SIG maillist  -  Distutils-SIG@python.org
https://mail.python.org/mailman/listinfo/distutils-sig


[Distutils] Trove classifiers for MicroPython?

2016-10-20 Thread Radomir Dopieralski
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
___
Distutils-SIG maillist  -  Distutils-SIG@python.org
https://mail.python.org/mailman/listinfo/distutils-sig