Skip to content

docs: add Pixi setup instructions for macOS #1931

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
kurupashwin482-web wants to merge 1 commit into from
Closed

docs: add Pixi setup instructions for macOS #1931

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
49 changes: 48 additions & 1 deletion getting-started/setup-building.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -903,7 +903,54 @@ some of CPython's modules (for example, ``zlib``).
./configure --config-cache \
--with-pydebug

And finally, run ``make``::
.. tab:: Pixi

@willingc willingc Oct 22, 2026 •
edited
Loading

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the PR @kurupashwin482-web. I don't believe the devguide (or this section of the devguide) is the best place to provide build instructions using pixi. While I am a frequent user of Pixi and uv, I'm not sure it is necessary to support each tool here.

Thoughts from other core devs?

My recommendation would be to close this PR. @kurupashwin482-web, perhaps you would like to create your own blog post with this information instead or a Gist on GitHub.


For **Pixi**, install Pixi by following the
`installation instructions <https://pixi.sh/latest/installation/>`__.
Create a :file:`pixi.toml` file in the CPython source directory

@StanFromIreland StanFromIreland Oct 22, 2026 •
edited
Loading

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What about the existing pixi files we bundle?

with the following contents:

.. code-block:: toml

[workspace]
name = "cpython-dev"
channels = ["conda-forge"]
platforms = ["osx-arm64", "osx-64"]

[dependencies]
gdbm = "*"
libmpdec-devel = "*"
openssl = "3.*"
pkg-config = "*"
tk = "*"
xz = "*"
zstd = "*"
zlib = "*"

[tasks.configure]
cmd = "./configure --config-cache --with-pydebug --with-openssl=$CONDA_PREFIX"

[tasks.configure.env]
PKG_CONFIG_PATH = "$CONDA_PREFIX/lib/pkgconfig"
GDBM_CFLAGS = "-I$CONDA_PREFIX/include"
GDBM_LIBS = "-L$CONDA_PREFIX/lib -lgdbm"
TCLTK_CFLAGS = "$(pkg-config --cflags tcl tk)"
TCLTK_LIBS = "$(pkg-config --libs tcl tk | sed 's/-l[^ ]*stub[^ ]*//g')"
LDFLAGS = "-Wl,-rpath,$CONDA_PREFIX/lib"

[tasks.build]
cmd = "make -s -j8"

Then install the dependencies and configure CPython::

$ pixi install
$ pixi run configure

Build CPython using the configured environment::

$ pixi run build

For **Homebrew** and **MacPorts**, build CPython by running::

$ make -s -j8

Expand Down