Skip to content
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.

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

Fix building of docs with the lastest numpy and sphinx #709

Merged
merged 14 commits into from
Jul 24, 2023
Prev Previous commit
Fix ref to fitness creation part
  • Loading branch information
fmder committed Jul 24, 2023
commit 3a764d71769dd8c630e7c9c086c1ff25be05f3a1
2 changes: 1 addition & 1 deletion doc/tutorials/basic/part2.rst
Original file line number Diff line number Diff line change
Expand Up @@ -35,7 +35,7 @@ Evaluation
The evaluation is the most personal part of an evolutionary algorithm, it is
the only part of the library that you must write yourself. A typical
evaluation function takes one individual as argument and returns its fitness as
a :class:`tuple`. As shown in the :ref:`core` section, a fitness is a list of floating point values and has a
a :class:`tuple`. As shown in the :ref:`creating-types` section, a fitness is a list of floating point values and has a
property :attr:`~deap.base.Fitness.valid` to know if this individual shall be re-evaluated. The
fitness is set by setting the :attr:`~deap.base.Fitness.values` to the
associated :class:`tuple`. For example, the following evaluates the previously created individual ``ind1`` and assigns its fitness to the corresponding values.
Expand Down