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
The last release was v1.10 on 26 Jan 2019. Since then there were around 350 commits, and big changes to the .mpy file format, so the plan is to make the next release v1.11.
Remaining issues/PRs to resolve before the release are:
Please include correct copyright information about files I created or made substantial contributions to, as well as to the whole project, pull requests #4787 & #4363 .
It would be great to have v1.11 in a condition to facilitate productive development with the new PYBD boards. I saw one PR #4669 related to this. Perhaps there are other issues and PRs that fit into this category? Are there step-by-step docs describing how to make a build?
What do you think? There will be a lot PYBDs coming into developer hands - it would be cool to make it easy for people to get started and contribute.
It would be great to have v1.11 in a condition to facilitate productive development with the new PYBD boards.
The reason PYBD support is not merged yet is because I wanted that to be the focus of the next-next release (v1.12). The upcoming v1.11 already has enough new stuff in it, and merging big changes for PYBD will possibly lead to regressions to existing code which need time to be addressed. So in the interest of cutting a stable release ASAP, I don't want to merge any PYBD related items yet.
Unfortunately this is not possible right now. It's a really difficult thing and needs someone who has the hardware, expertise and time to look into making it work. If you can look into it yourself and make some progress improving it that would be really great.
I'm not sure what kind of timeframe we're looking at but I intend to make a few improvements to the ESP32 docs in the next week. Mostly issues we noticed shortly after the 1.10 release. Shouldn't be a showstopper for 1.11 though.
Please include correct copyright information about files I created or made substantial contributions to, as well as to the whole project, pull requests #4787 & #4363 .
What's the reason for not including this in the release?
Activity
peterhinch commentedon May 14, 2019
upip - Please ensure it can install library modules compatible with official MicroPython (either via an alternative version or a command line arg).
pfalcon commentedon May 14, 2019
Please include correct copyright information about files I created or made substantial contributions to, as well as to the whole project, pull requests #4787 & #4363 .
miketeachman commentedon May 16, 2019
It would be great to have v1.11 in a condition to facilitate productive development with the new PYBD boards. I saw one PR #4669 related to this. Perhaps there are other issues and PRs that fit into this category? Are there step-by-step docs describing how to make a build?
What do you think? There will be a lot PYBDs coming into developer hands - it would be cool to make it easy for people to get started and contribute.
nedoskiv commentedon May 16, 2019
It will be nice to have stable network.PPP module
dpgeorge commentedon May 17, 2019
The reason PYBD support is not merged yet is because I wanted that to be the focus of the next-next release (v1.12). The upcoming v1.11 already has enough new stuff in it, and merging big changes for PYBD will possibly lead to regressions to existing code which need time to be addressed. So in the interest of cutting a stable release ASAP, I don't want to merge any PYBD related items yet.
dpgeorge commentedon May 17, 2019
Unfortunately this is not possible right now. It's a really difficult thing and needs someone who has the hardware, expertise and time to look into making it work. If you can look into it yourself and make some progress improving it that would be really great.
mattytrentini commentedon May 28, 2019
I'm not sure what kind of timeframe we're looking at but I intend to make a few improvements to the ESP32 docs in the next week. Mostly issues we noticed shortly after the 1.10 release. Shouldn't be a showstopper for 1.11 though.
dpgeorge commentedon May 28, 2019
A release is imminent.
dpgeorge commentedon May 29, 2019
Ok... v1.11 was tagged in 6f75c4f
robert-hh commentedon May 29, 2019
When updating the Download pages, please update the Pyboard D binaries too.
dpgeorge commentedon May 29, 2019
Ok, that's now done. Docs are updated (except for a PDF build error, to be fixed) and esp-extra-scripts branch is force pushed.
pfalcon commentedon May 30, 2019
What's the reason for not including this in the release?
bruno963852 commentedon May 31, 2019
Sorry if the question is dumb, but it is not possible to just use the gsm module done by loboris on his fork?
Merge pull request micropython#4784 from weblate/weblate-circuitpytho…