You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It's not that missing as spread around, which is common problem. Then, there's vicious cycle - I don't want to make initial hacky ways to do it kind of "official docs" before there will be enough testing, but then people can't find any docs at all.
Ok, I added basic instructions to README. They surely expect some familiarity with standard Python package installation process.
Should I install every package individually ?
You can use it the same way as you use pip. This includes installing packages individually, or several at once, or using requirements file. Please refer to pip documentation.
Activity
pfalcon commentedon Jun 9, 2014
It's not that missing as spread around, which is common problem. Then, there's vicious cycle - I don't want to make initial hacky ways to do it kind of "official docs" before there will be enough testing, but then people can't find any docs at all.
So, please start here:
and I'll look into adding something to README after all.
oksome commentedon Jun 10, 2014
Updating the README with a warning about how hacky it is should probably be enough, but at the moment it is very unclear.
From what I understood, I should use
pip-micropythonfrommicropython/tools. Should I install every package individually ?pfalcon commentedon Jun 14, 2014
Ok, I added basic instructions to README. They surely expect some familiarity with standard Python package installation process.
You can use it the same way as you use pip. This includes installing packages individually, or several at once, or using requirements file. Please refer to pip documentation.
oksome commentedon Jun 15, 2014
Thank you !