Locking down python source.

[Lars R.]

But the explanations make me believe that reason for the question is a more about locking down a pyboard and protect intellectual property.

Regarding the pyboard in particular: Not really.
Regarding protect intellectual property: Yes.

[bmarkus]

@kfricke:
Python is popular amongst people that don't know much about computers or programming.

Right, including peopla at Google, Ericsson, Microsoft, etc...

@kfricke:
it could be a reason to choose micropython instead of a raspberry.

Joking?

[Lars R.]

@kfricke:
Python is popular amongst people that don't know much about computers or programming.

Right, including peopla at Google, Ericsson, Microsoft, etc...

Big companies are not interested in techniques that enable small companies (with little IT knowledge) to sell copy-protected products. They are interested in people using their "Apps"-platforms over which they have 100% control.

@kfricke:
it could be a reason to choose micropython instead of a raspberry.

Joking?

No.

[pfalcon]

@kfricke:
As I wrote before, this is IMHO not about closing micropython. On the contrary its about driving its development.

The most secure things about locking stuff down are open source: Truecrypt, encryption algorithms. Also, those are the ones most feared by bigger companies.
Think about how much commercial stuff is done with the linux kernel and who is contributing and paying. Even the linux distributions.

[]

I (FPGA developer) just don't want to spend time on STM32 details.

Ok, so let me be as straightforward as you: if you want that feature, but don't want to spend time on it, contract the MicroPython maintainer to implement it. That will be exactly things you want: open-source, and driving MicroPython development (i.e. making sure that MicroPython maintainer doesn't stop project because his bank statement shows that Kickstarter money ran out, and he needs to be back to working on something else.)

[Lars R.]

Feature already existed and was kindly provided on the previous page. It seems to be hidden on purpose which is why I added some arguments with good intent. The other option is to just not have micropython in the repository of acceptable options. It seems, majority here prefers micropython not to be used at all for the use cases discussed. So I will not use it until this changes. Other options available and no point in acting against community wishes.

[pfalcon]

Feature already existed and was kindly provided on the previous page. It seems to be hidden on purpose

I love conspiracy theories. The guy who wrote it didn't deliver it on a plate at your doorstep, so it must be hidden. And random link on a forum is the answer to the question of life and stuff, and certainly gives indulgence to not read a datasheet. Nevermind the questions like "What exactly is protected and how?" and "What do I do if I locked something which I didn't want to lock and don't know how to unlock?" - they're for pussies. The mail villain? STMicro! They hid truth from people in the datasheets - they knew that's something which nobody will read!

I guess we got to the bottom of it in this thread, and now can archive it.