Resolve conflicting target names

  features to conveniently include LAMMPS into `Jupyter

  <https://jupyter.org/>`_ notebooks.

.. _mpi4py: https://mpi4py.readthedocs.io

.. _mpi4py_url: https://mpi4py.readthedocs.io

----------

:doc:`python <python>` command, where a pointer to the already existing

:cpp:class:`LAMMPS <LAMMPS_NS::LAMMPS>` class instance can be passed

to the Python class and used instead of creating a new instance.  The

*comm* argument may be used in combination with the `mpi4py <mpi4py_>`_

*comm* argument may be used in combination with the `mpi4py <mpi4py_url_>`_

module to pass an MPI communicator to LAMMPS and thus it is possible

to run the Python module like the library interface on a subset of the

MPI ranks after splitting the communicator. Here is a simple example:

class lammps(object):

  """Create an instance of the LAMMPS Python class.

  .. _mpi4py: https://mpi4py.readthedocs.io/

  .. _mpi4py_docs: https://mpi4py.readthedocs.io/

  This is a Python wrapper class that exposes the LAMMPS C-library

  interface to Python.  It either requires that LAMMPS has been compiled

  :type  cmdargs: list

  :param ptr: pointer to a LAMMPS C++ class instance when called from an embedded Python interpreter.  None means load symbols from shared library.

  :type  ptr: pointer

  :param comm: MPI communicator (as provided by `mpi4py <mpi4py_>`_). ``None`` means use ``MPI_COMM_WORLD`` implicitly.

  :param comm: MPI communicator (as provided by `mpi4py <mpi4py_docs_>`_). ``None`` means use ``MPI_COMM_WORLD`` implicitly.

  :type  comm: MPI_Comm

  """