| Mar | APR | May |
| 24 | ||
| 2021 | 2022 | 2023 |
COLLECTED BY
Collection: Save Page Now
●Getting Started
●Where to Get Help
●Lifecycle of a Pull Request
●Running & Writing Tests
●Increase Test Coverage
●Helping with Documentation
●Documenting Python
●Silence Warnings From the Test Suite
●Fixing “easy” Issues (and Beyond)
●Issue Tracking
Toggle child pages in navigation
●GitHub Labels
●GitHub issues for BPO users
●Triaging an Issue
●Following Python’s Development
●Porting Python to a new platform
●How to Become a Core Developer
●Developer Log
●Accepting Pull Requests
●Development Cycle
●Continuous Integration
●Adding to the Stdlib
●Changing the Python Language
●Experts Index
●gdb Support
●Exploring CPython’s Internals
●Changing CPython’s Grammar
●Guide to CPython’s Parser
●Design of CPython’s Compiler
●Design of CPython’s Garbage Collector
●Updating standard library extension modules
●Changing Python’s C API
●Coverity Scan
●Dynamic Analysis with Clang
●Running a buildbot worker
●Core Developer Motivations and Affiliations
●Git Bootcamp and Cheat Sheet
●Appendix: Topics
v: latest
Versions
latest
Downloads
pdf
html
epub
On Read the Docs
Project Home
Builds
Back to top
Edit this page
Toggle Light / Dark / Auto color theme
Toggle table of contents sidebar
Makefile in the
source distribution, will give you a hint on which files to compile
for Python. Not all source files are relevant: some are platform
specific, others are only used in emergencies (e.g. getopt.c).
It is not recommended to start porting Python without at least medium-level
understanding of your target platform; i.e. how it is generally used, how to
write platform specific apps, etc. Also, some Python knowledge is required, or
you will be unable to verify that your port is working correctly.
You will need a pyconfig.h file tailored for your platform. You can
start with pyconfig.h.in, read the comments, and turn on definitions that
apply to your platform. Also, you will need a config.c file, which lists
the built-in modules you support. Again, starting with
Modules/config.c.in is recommended.
Finally, you will run into some things that are not supported on your
target platform. Forget about the posix module in the beginning. You can
simply comment it out of the config.c file.
Keep working on it until you get a >>> prompt. You may have to disable the
importing of site.py by passing the -S option. When you have a prompt,
bang on it until it executes very simple Python statements.
At some point you will want to use the osmodule; this is the time to start
thinking about what to do with the posix module. It is okay to simply
comment out functions in the posix module that cause problems; the
remaining ones will be quite useful.
Before you are done, it is highly recommended to run the Python regression test
suite, as described in Running & Writing Tests.
Next
How to Become a Core Developer
Previous
Following Python’s Development
Copyright © 2011-2022, Python Software Foundation
Made with Sphinx and @pradyunsg's
Furo
Last updated on Apr 21, 2022