In order to discuss FiPy with other users and with the developers, we encourage you to use one of the following modes of communication. We monitor all of these, so there is no need to post to more than one of them.

You may want to read the following resource about asking effective questions:

If you are having trouble, we are able to offer much more effective help if you provide a minimal reproducible example.

GitHub Discussions

Suitable for open-ended conversations, troubleshooting, showing off…

If a discussion highlights a bug or feature request, it’s easy for us to migrate GitHub Discussions to GitHub Issues.

GitHub Issues

Suitable for bug reports, feature requests, and patch submissions.


Suitable for questions that (probably) have definitive answers (“How do I…?”). It doesn’t work so well for back-and-forth conversations, which are better suited to GitHub Discussions. Further, it’s bad at math and they tend to delete answers that link to our existing documentation, meaning that we’d need to expend considerable effort, using an inferior tool, to duplicate things we’ve already written.

Seriously, use GitHub Discussions.

Mailing List


The mailing list is deprecated. Please use GitHub Discussions, instead.

You can sign up for the mailing list by sending a subscription email to <>.

Once you are subscribed, you can post messages to the list simply by addressing email to <>.

To get off the list, send a message to <>.

Send a message to <> to learn other mailing list configurations you can change.

The list is hosted as a Google group. If you are subscribed with a Google account, you can interact with the list, configure your subscription, and see the archives at

List Archive

Copies of messages sent to are stored at The Mail Archive.

Older messages are archived at

(note: we have also historically sent copies to, but the GMANE site now appears to be defunct.)

Last updated on Jun 27, 2023. Created using Sphinx 6.2.1.