About mod_wsgi

Home: https://modwsgi.readthedocs.io/en/developi/

Package license: Apache-2.0

Feedstock license: BSD-3-Clause

Summary: Apache module that implements a WSGI compliant interface for hosting Python based web applications

Development: https://github.com/GrahamDumpleton/mod_wsgi

Documentation: https://modwsgi.readthedocs.io/en/develop/

mod_wsgi is a module for the Apache HTTP server that allows the web server to execute Python programs. WSGI (Web Server Gateway Interface) is a general interface between the Web server and Python applications.

Current build status

Azure

Variant Status linux_64_python3.10.____cpython linux_64_python3.11.____cpython linux_64_python3.8.____cpython linux_64_python3.9.____cpython osx_64_python3.10.____cpython osx_64_python3.11.____cpython osx_64_python3.8.____cpython osx_64_python3.9.____cpython

Current release info

Name	Downloads	Version	Platforms

Installing mod_wsgi

Installing mod_wsgi from the conda-forge channel can be achieved by adding conda-forge to your channels with:

conda config --add channels conda-forge
conda config --set channel_priority strict

Once the conda-forge channel has been enabled, mod_wsgi can be installed with conda:

conda install mod_wsgi

or with mamba:

mamba install mod_wsgi

It is possible to list all of the versions of mod_wsgi available on your platform with conda:

conda search mod_wsgi --channel conda-forge

or with mamba:

mamba search mod_wsgi --channel conda-forge

Alternatively, mamba repoquery may provide more information:

# Search all versions available on your platform:
mamba repoquery search mod_wsgi --channel conda-forge

# List packages depending on `mod_wsgi`:
mamba repoquery whoneeds mod_wsgi --channel conda-forge

# List dependencies of `mod_wsgi`:
mamba repoquery depends mod_wsgi --channel conda-forge

About conda-forge

conda-forge is a community-led conda channel of installable packages.
In order to provide high-quality builds, the process has been automated into the
conda-forge GitHub organization. The conda-forge organization contains one repository
for each of the installable packages. Such a repository is known as a feedstock.

A feedstock is made up of a conda recipe (the instructions on what and how to build
the package) and the necessary configurations for automatic building using freely
available continuous integration services. Thanks to the awesome service provided by
Azure, GitHub,
CircleCI, AppVeyor,
Drone, and TravisCI
it is possible to build and upload installable packages to the
conda-forge Anaconda-Cloud
channel for Linux, Windows and OSX respectively.

To manage the continuous integration and simplify feedstock maintenance
conda-smithy has been developed.
Using the conda-forge.yml within this repository, it is possible to re-render all of
this feedstock's supporting files (e.g. the CI configuration files) with conda smithy rerender.

For more information please check the conda-forge documentation.

Terminology

feedstock - the conda recipe (raw material), supporting scripts and CI configuration.

conda-smithy - the tool which helps orchestrate the feedstock.
Its primary use is in the construction of the CI .yml files
and simplify the management of many feedstocks.

conda-forge - the place where the feedstock and smithy live and work to
produce the finished article (built conda distributions)

Updating mod_wsgi-feedstock

If you would like to improve the mod_wsgi recipe or build a new
package version, please fork this repository and submit a PR. Upon submission,
your changes will be run on the appropriate platforms to give the reviewer an
opportunity to confirm that the changes result in a successful build. Once
merged, the recipe will be re-built and uploaded automatically to the
conda-forge channel, whereupon the built conda packages will be available for
everybody to install and use from the conda-forge channel.
Note that all branches in the conda-forge/mod_wsgi-feedstock are
immediately built and any created packages are uploaded, so PRs should be based
on branches in forks and branches in the main repository should only be used to
build distinct package versions.

In order to produce a uniquely identifiable distribution:

• If the version of a package is not being increased, please add or increase
  the build/number.
• If the version of a package is being increased, please remember to return
  the build/number
  back to 0.

Feedstock Maintainers

• @ReimarBauer