MicroPython Forum (Archive)

mattyt wrote: ↑

Wed Dec 12, 2018 11:33 pm

pythoncoder wrote: ↑

Wed Dec 12, 2018 1:19 pm

In addition to the approach to cross-installing pointed out by Paul, there is also micropip. This avoids the need to install the Unix build of MicroPython: you can download the package to your PC and copy it to the device by any means.

I somehow hadn't come across micropip before; that's really helpful, thanks Peter!

Except that "micropip" is nothing but a "port" of upip as written by me, to CPython, with the licensing and attribution information not provided, or removed. Which construes a violation of the license on whose terms this code is provided, the MIT license.

pfalcon wrote: ↑

Thu Dec 13, 2018 7:43 am

Except that "micropip" is nothing but a "port" of upip as written by me, to CPython, with the licensing and attribution information not provided, or removed. Which construes a violation of the license on whose terms this code is provided, the MIT license.

Apologies for this oversight on my part. Now fixed, I hope to your satisfaction.

pfalcon wrote: ↑

Thu Dec 13, 2018 7:43 am

Except that "micropip" is nothing but a "port" of upip as written by me, to CPython, with the licensing and attribution information not provided, or removed. Which construes a violation of the license on whose terms this code is provided, the MIT license.

Although I must point out that the copyright and attribution was added to upip after I did the port. When porting code I always include any attribution, copyright and licensing present in the original.

That comment also applies to my fork of uasyncio: the details were added after I forked.

pythoncoder wrote: ↑

Thu Dec 13, 2018 8:55 am

Although I must point out that the copyright and attribution was added to upip after I did the port. When porting code I always include any attribution, copyright and licensing present in the original.

The "original" here is the micropython-lib project, which always included the LICENSE file, both providing full text of licenses used, and describing the fact that each module comes under its own licensing and authorship, provided in metadata.txt/setup.py coming alongside each module. LICENSE and metadata.txt/setup.py are thus represent licensing material, and the license is explicit that licensing/attribution data should be explicitly provided with any copy of the licensed content. Complying with the license terms generally lies on the users.

Beyond that, the nature of the project - providing code for low-memory systems, where each byte counts - made it natural to omit additional headers in each file, relying on users' good will and due diligence in complying with the license.

That comment also applies to my fork of uasyncio: the details were added after I forked.

Surely, seeing the nice people's negligence and ignorance of licensing matters and attribution needs in general, bordering on impersonation of authorship, I made steps that any further steps in that direction would be willful removal of licensing terms/copyright, whereas previously it was just a nice, good-intentional omission and imprudence.

If, as author of the original, you are unhappy with my attribution or licensing code comments, a PM with a polite request to adopt a form of words to your liking would have sufficed. If you consider my replacement text unsatisfactory, I will be happy to replace it verbatim with text of your choosing.

I have no desire to claim authorship of what is a routine port.

There is no need for public accusations.