Modifications

{{traduction}}

{{traduction}}

Part of what makes CircuitPython so awesome is its ability to store code separately from the firmware itself. Storing code separately from the firmware makes it easier to update both the code you write and the libraries you depend. So, instead of compiling libraries in, you simply place them into your <code class="prettyprint">lib</code> directory on the <code class="prettyprint">CIRCUITPY</code> drive.

Part of what makes CircuitPython so awesome is its ability to store code separately from the firmware itself. Storing code separately from the firmware makes it easier to update both the code you write and the libraries you depend. So, instead of compiling libraries in, you simply place them into your {{fname|lib}} directory on the {{fname|CIRCUITPY}} drive.

Your board may ship with a <code class="prettyprint">lib</code> folder already, its in the base directory of the drive. If not, simply create the folder yourself.

Your board may ship with a {{fname|lib}} folder already, its in the base directory of the drive. If not, simply create the folder yourself.

{{ADFImage|FEATHER-M0-MicroPython-bibliotheque-01.png|640px}}

{{ADFImage|FEATHER-M0-MicroPython-bibliotheque-01.png|480px}}

CircuitPython libraries work in the same was as regular Python modules so the <a href="https://docs.python.org/3/tutorial/modules.html">Python docs</a> are a great reference for how it all should work. In Python terms, we can place our library files in the <code class="prettyprint">lib</code> directory because its part of the Python path by default.

CircuitPython libraries work in the same was as regular Python modules so the [https://docs.python.org/3/tutorial/modules.html Python docs] are a great reference for how it all should work. In Python terms, we can place our library files in the {{fname|lib}} directory because its part of the Python path by default.

One downside of this approach of separate libraries is that they are not built in. To use them, one needs to copy them to the <code class="prettyprint">CIRCUITPY</code> drive before they can be used. Fortunately, we provide a bundle full of our libraries.

One downside of this approach of separate libraries is that they are not built in. To use them, one needs to copy them to the {{fname|CIRCUITPY}} drive before they can be used. Fortunately, we provide a bundle full of our libraries.

Our bundle and releases also feature optimized versions of the libraries with the <code class="prettyprint">.mpy</code> file extension. These files take less space on the drive and have a smaller memory footprint as they are loaded.

Our bundle and releases also feature optimized versions of the libraries with the {{fname|.mpy}} file extension. These files take less space on the drive and have a smaller memory footprint as they are loaded.

== Installing the bundle ==

== Installing the bundle ==