antons wrote:Hello Team MicroPython
I started with the micro python library, but it was not clear to me how to use the library on the micropython board itself.
Well, the basic idea is the same as for (any) Python: you make a requirements file with a list of dependency modules, then you run a package manager to deploy the dependencies. For Python this package manager is called "pip", for MicroPython - "pip-micropython". It is installed when you do "make install" for micropython on a host (and that's a prerequisite for comfortable development).
Specific example how that works is given in this thread:
http://forum.micropython.org/viewtopic.php?f=5&t=221 (that example targets small embedded Linux systems, but there's very little difference from PyBoard or any other hardware capable of running MicroPython).
So I started to copy and paste parts of the library to an SD card, fixing some __init__.py stuff and writing for each lib a small test.
My lib is not meant as a replacement, but to get some stuff working for me, and maybe for somebody else.
Sounds good,
https://github.com/micropython/micropython-lib has the same aim
.
What do you think of the idea to have a git repository which one can check out directly on the micro-python board, without a make step?
Taken literally, that's not possible - you cannot run git on pyboard. Just the same as you cannot run pip-micropython on a pyboard currently, so have to run it on a host, make it prepare a deployable directory image, and then copy it to pyboard.
If you mean "connect pyboard, change to its disk, and run git clone there", there're number of caveats to that approach. First, git clone contains hidden .git dir - it's not needed to run Python code, but takes space on a tiny filesystem. The more changes you make to the repository, the bigger .git dir, so soon you have very little space for source code and data, and then none at all. So, you can't just "git clone", you at least will need to do "rm -rf .git", and not forget about. The easiest way to not forget is to automate it with a script or a makefile.
It doesn't end there so. You might be caring about a single project now, but soon you (or somebody else) will work on another project, need more modules, then more, and more. Again, if you keep adding more and more modules to a monolithic repository, you will get less and less space on pyboard, until none at all. micropython-lib already contains many more modules than pyboard can fit.
And about reinventing wheels: one can only re-invent a wheel after carefully studying the original...
For me, embedded development with Python is really the way to go. So please go one with development.
Anton
That's cool, and sounds good. There's one caveat though - if you spend too much time reinventing the wheel, you leave yourself less time to do something really new and exciting, so it's easier to get disappointed in a project and drop it...
.