user/sven/micropython.git - The MicroPython project

Age	Commit message (Collapse)	Author
2025-07-23	docs/reference/speed_python: Document schedule/GIL limitation of native.	Damien George
	Signed-off-by: Damien George <damien@micropython.org>
2025-02-25	all: Upgrade codespell to v2.4.1.	Christian Clauss
	This commit upgrades from codespell==2.2.6 to the current codespell==2.4.1, adding emac to the ignore-words-list. Signed-off-by: Christian Clauss <cclauss@me.com>
2025-02-11	docs/reference: Add strings vs bytes to speed optimisation tips.	Angus Gratton
	Also add some additional context links, suggestions for alternative classes, etc. This work was funded through GitHub Sponsors. Signed-off-by: Angus Gratton <angus@redyak.com.au>
2023-05-23	docs/reference/speed_python: Remove 4-arg limit for viper.	Jim Mussared
	This limit was removed in a676b5acf6ee9c17926cf9786370d30a077d99c0. Signed-off-by: Jim Mussared <jim.mussared@gmail.com>
2021-12-15	docs: Remove trailing spaces and convert tabs to spaces.	Damien George
	Signed-off-by: Damien George <damien@micropython.org>
2021-08-30	docs/reference: Mention that slicing a memoryview causes allocation.	Peter Hinch

2021-08-13	docs: Replace ufoo with foo in all docs.	Jim Mussared
	Anywhere a module is mentioned, use its "non-u" name for consistency. The "import module" vs "import umodule" is something of a FAQ, and this commit intends to help clear that up. As a first approximation MicroPython is Python, and so imports should work the same as Python and use the same name, to a first approximation. The u-version of a module is a detail that can be learned later on, when the user wants to understand more and have finer control over importing. Existing Python code should just work, as much as it is possible to do that within the constraints of embedded systems, and the MicroPython documentation should match the idiomatic way to write Python code. With universal weak links for modules (via MICROPY_MODULE_WEAK_LINKS) users can consistently use "import foo" across all ports (with the exception of the minimal ports). And the ability to override/extend via "foo.py" continues to work well. Signed-off-by: Jim Mussared <jim.mussared@gmail.com>
2020-01-06	docs: More consistent capitalization and use of articles in headings.	Jason Neal
	See issue #3188.
2019-10-16	docs: Fix spelling in various parts of the docs.	Mike Causer

2019-08-28	docs/reference/speed_python: Add missing self to var caching example.	Paul m. p. P

2019-08-19	docs/reference/speed_python: Update that read-only buffers are accepted.	Peter Hinch
	As allowed by recent cd35dd9d9a29836906acdce60c931f6352b536d0
2019-03-08	py: Implement a module system for external, user C modules.	Ayke van Laethem
	This system makes it a lot easier to include external libraries as static, native modules in MicroPython. Simply pass USER_C_MODULES (like FROZEN_MPY_DIR) as a make parameter.
2018-03-15	docs: Fix some references and RST markup to eliminate Sphinx warnings.	Damien George

2017-06-26	docs/ref/speed_python: Update and make more hardware-neutral.	Paul Sokolovsky
	Move hardware-specific optimizations to the very end of document, and add visible note that it gives an example for Pyboard. Remove references to specific hardware technologies, so the doc can be more naturally used across ports. Various markup updates to adhere to the latest docs conventions.
2016-11-08	docs/*/quickref.rst: Use new semantics of ticks_diff()	puuu

2016-04-15	docs/speed_python: Add article.	Paul Sokolovsky

2016-04-15	docs/speed_python: Add many more details on memoryviews.	Paul Sokolovsky

2016-04-15	docs/speed_python: Generalize "Floating point" subsection.	Paul Sokolovsky
	Don't describe just single port's peculiarities, note aboute possible array of issues with floating-point.
2016-04-15	docs/speed_python: Clarify/generalize "Buffers" subsection.	Paul Sokolovsky

2016-03-11	docs: Add Python speed optimisation guide, including minimal viper ref.	Peter Hinch