Change capitalization Pytensor → PyTensor

Author: michaelosthege

.github/ISSUE_TEMPLATE/bug-report.yml

@@ -52,9 +52,9 @@ body:
 
 - type: textarea
   attributes:
-    label: "Pytensor version information:"
+    label: "PyTensor version information:"
     description: >
-      Pytensor Version:
+      PyTensor Version:
       Python Version:
       Operating system:
       How did you install pytensor: (conda/pip)

.github/ISSUE_TEMPLATE/config.yml

@@ -2,4 +2,4 @@ blank_issues_enabled: false
 contact_links:
   - name: PyMC Discourse
     url: https://discourse.pymc.io/
-    about: Ask usage questions about PyMC or Pytensor
+    about: Ask usage questions about PyMC or PyTensor

.github/ISSUE_TEMPLATE/documentation.yml

@@ -5,7 +5,7 @@
 
 
 name: Documentation
-description: Report an issue related to the Pytensor documentation.
+description: Report an issue related to the PyTensor documentation.
 title: "DOC: <Please write a comprehensive title after the 'DOC: ' prefix>"
 labels: [docs]
 

.github/ISSUE_TEMPLATE/installation.yml

@@ -5,7 +5,7 @@
 
 
 name: Post-install/importing issue
-description: Report an issue if you have trouble importing or using Pytensor after installation.
+description: Report an issue if you have trouble importing or using PyTensor after installation.
 title: "<Please write a comprehensive title here>"
 labels: [installation]
 

.github/SECURITY.md

@@ -1,3 +1,3 @@
-To report a security vulnerability to Pytensor, please go to
+To report a security vulnerability to PyTensor, please go to
 https://tidelift.com/security and see the instructions there.
 

.gitignore

@@ -39,7 +39,7 @@ pytensor/generated_version.py
 pytensor/generated_version.py.out
 distribute-*.egg
 distribute-*.tar.gz
-Pytensor.suo
+PyTensor.suo
 .ipynb_checkpoints
 .pydevproject
 .ropeproject

CODE_OF_CONDUCT.md

@@ -1,6 +1,6 @@
-# Pytensor Code of Conduct
+# PyTensor Code of Conduct
 
-Like the technical community as a whole, the Pytensor team and community is made
+Like the technical community as a whole, the PyTensor team and community is made
 up of a mixture of professionals and volunteers from all over the world, working
 on every aspect of the mission—including mentorship, teaching, and connecting
 people.
@@ -13,8 +13,8 @@ This isn’t an exhaustive list of things that you can’t do. Rather, take it i
 the spirit in which it’s intended—a guide to make it easier to enrich all of
 us and the technical communities in which we participate.
 
-This code of conduct applies to all spaces managed by the Pytensor project. This
-includes Gitter, mailing lists, the issue tracker, Pytensor events, and any other
+This code of conduct applies to all spaces managed by the PyTensor project. This
+includes Gitter, mailing lists, the issue tracker, PyTensor events, and any other
 forums created by the project team that the community uses for communication.
 In addition, violations of this code outside these spaces may affect a person's
 ability to participate within them.
@@ -41,9 +41,9 @@ it by emailing pymc.devs@gmail.com.
   excuse for poor behavior and poor manners. We might all experience some
   frustration now and then, but we cannot allow that frustration to turn into a
   personal attack. It’s important to remember that a community where people feel
-  uncomfortable or threatened is not a productive one. Members of the Pytensor
+  uncomfortable or threatened is not a productive one. Members of the PyTensor
   community should be respectful when dealing with other members as well as with
-  people outside the Pytensor community.
+  people outside the PyTensor community.
 
 - __Be careful in the words that you choose.__ We are a community of professionals,
   and we conduct ourselves professionally. Be kind to others. Do not insult or
@@ -62,9 +62,9 @@ it by emailing pymc.devs@gmail.com.
       then stop.
 
 - __When we disagree, try to understand why.__ Disagreements, both social and
-  technical, happen all the time and Pytensor is no exception. It is important
+  technical, happen all the time and PyTensor is no exception. It is important
   that we resolve disagreements and differing views constructively. Remember
-  that we’re different. Pytensor benefits from its varied community and
+  that we’re different. PyTensor benefits from its varied community and
   people from a wide range of backgrounds. Different people have different
   perspectives on issues. Being unable to understand why someone holds a
   viewpoint doesn’t mean that they’re wrong. Don’t forget that it is human to

CONTRIBUTING.md

@@ -1,4 +1,4 @@
-If you want to contribute to Pytensor, have a look at the instructions here:
+If you want to contribute to PyTensor, have a look at the instructions here:
 https://pytensor.readthedocs.io/en/latest/dev_start_guide.html
 
 ## Contribution Expectations
@@ -7,7 +7,7 @@ This "Contribution Expectations" section is adapted from [Open Source
 Archetypes](https://opentechstrategies.com/archetypes) and released under a
 [CC-BY-SA](https://creativecommons.org/licenses/by-sa/4.0/) license.
 
-The current focus of the Pytensor project is rapid, high quality development of a
+The current focus of the PyTensor project is rapid, high quality development of a
 hackable, pure-Python symbolic tensor library with strong support for graph
 rewrites and transpilation to multiple backends including C,
 [JAX](https://github.com/google/jax>), and
@@ -27,16 +27,16 @@ source archetypes).
 
 ## Issues and Discussions
 
-We expect that Github Issues ("issues") indicate work that should be in Pytensor
+We expect that Github Issues ("issues") indicate work that should be in PyTensor
 and can be picked up immediately by a contributor. This includes bugs, which
 indicate something not working as advertised.
 
 Discussions should be created when the scope or direction of the work, though
-within the stated goals of the Pytensor project, require additional clarification
+within the stated goals of the PyTensor project, require additional clarification
 or consideration before a course of action is chosen.
 
 For issues a minimal working example (MWE) is strongly recommended when relevant
 (fixing a typo in the documentation does not require a MWE). For discussions,
-MWEs are generally required. All MWEs must be implemented using Pytensor. Please
-do not submit MWEs if they are not implemented in Pytensor. In certain cases,
-pseudocode may be acceptable, but an Pytensor implementation is always preferable.
+MWEs are generally required. All MWEs must be implemented using PyTensor. Please
+do not submit MWEs if they are not implemented in PyTensor. In certain cases,
+pseudocode may be acceptable, but an PyTensor implementation is always preferable.

DESCRIPTION.txt

@@ -1,7 +1,7 @@
-Pytensor is a Python library that allows you to define, optimize, and efficiently evaluate mathematical expressions involving multi-dimensional arrays. It is built on top of NumPy_. Pytensor features:
+PyTensor is a Python library that allows you to define, optimize, and efficiently evaluate mathematical expressions involving multi-dimensional arrays. It is built on top of NumPy_. PyTensor features:
 
- * **tight integration with NumPy:** a similar interface to NumPy's. numpy.ndarrays are also used internally in Pytensor-compiled functions.
- * **efficient symbolic differentiation:** Pytensor can compute derivatives for functions of one or many inputs.
+ * **tight integration with NumPy:** a similar interface to NumPy's. numpy.ndarrays are also used internally in PyTensor-compiled functions.
+ * **efficient symbolic differentiation:** PyTensor can compute derivatives for functions of one or many inputs.
  * **speed and stability optimizations:** avoid nasty bugs when computing expressions such as log(1 + exp(x)) for large values of x.
  * **dynamic C code generation:** evaluate expressions faster.
  * **extensive unit-testing and self-verification:** includes tools for detecting and diagnosing bugs and/or potential problems.

README.rst

@@ -81,7 +81,7 @@ Getting started
   #    |v [id K]
   #    |TensorConstant{0.0} [id L]
 
-See `the Pytensor documentation <https://pytensor.readthedocs.io/en/latest/>`__ for in-depth tutorials.
+See `the PyTensor documentation <https://pytensor.readthedocs.io/en/latest/>`__ for in-depth tutorials.
 
 
 Installation
@@ -120,7 +120,7 @@ A good place to start contributing is by looking through the issues
 `here <https://github.com/pymc-devs/pytensor/issues`.
 
 
-.. |Project Name| replace:: Pytensor
+.. |Project Name| replace:: PyTensor
 .. |Tests Status| image:: https://github.com/pymc-devs/pytensor/workflows/Tests/badge.svg
   :target: https://github.com/pymc-devs/pytensor/actions?query=workflow%3ATests
 .. |Coverage| image:: https://codecov.io/gh/pymc-devs/pytensor/branch/main/graph/badge.svg?token=WVwr8nZYmc

doc/LICENSE.txt

@@ -13,9 +13,9 @@ Contains code from NumPy, Copyright (c) 2005-2016, NumPy Developers.
 Contains code from Aesara, Copyright (c) 2021-2022, Aesara Developers.
 All rights reserved.
 
-theano/scan/*.py[c]: Razvan Pascanu, Frederic Bastien, James Bergstra, Pascal Lamblin, Arnaud Bergeron, PyMC Developers, Pytensor Developers, (c) 2010, Universite de Montreal
+theano/scan/*.py[c]: Razvan Pascanu, Frederic Bastien, James Bergstra, Pascal Lamblin, Arnaud Bergeron, PyMC Developers, PyTensor Developers, (c) 2010, Universite de Montreal
 theano/tensor/sharedvar.py: James Bergstra, (c) 2010, Universite de Montreal, 3-clause BSD License
-theano/gradient.py: James Bergstra, Razvan Pascanu, Arnaud Bergeron, Ian Goodfellow, PyMC Developers, Pytensor Developers, (c) 2011, Universite de Montreal, 3-clause BSD License
+theano/gradient.py: James Bergstra, Razvan Pascanu, Arnaud Bergeron, Ian Goodfellow, PyMC Developers, PyTensor Developers, (c) 2011, Universite de Montreal, 3-clause BSD License
 theano/compile/monitormode.py: this code was initially copied from the 'pyutools' package by its original author, and re-licensed under Theano's license.
 
 Contains frozendict code from slezica’s python-frozendict(https://github.com/slezica/python-frozendict/blob/master/frozendict/__init__.py), Copyright (c) 2012 Santiago Lezica. All rights reserved.
@@ -28,7 +28,7 @@ modification, are permitted provided that the following conditions are met:
     * Redistributions in binary form must reproduce the above copyright
       notice, this list of conditions and the following disclaimer in the
       documentation and/or other materials provided with the distribution.
-    * Neither the name of Pytensor, Theano, nor the names of its contributors may be
+    * Neither the name of PyTensor, Theano, nor the names of its contributors may be
       used to endorse or promote products derived from this software without
       specific prior written permission.
 

doc/acknowledgement.rst

@@ -12,7 +12,7 @@ Acknowledgements
 * The developers of `NumPy <http://numpy.scipy.org/>`_. Theano is based on its ndarray object and uses much of its implementation.
 * The developers of `SciPy <http://scipy.org/>`_. Our sparse matrix support uses their sparse matrix objects. We also reuse other parts.
 * The developers of `Theano <https://github.com/Theano/Theano>`_
-* All `Pytensor contributors <https://github.com/pymc-devs/pytensor/graphs/contributors>`_.
+* All `PyTensor contributors <https://github.com/pymc-devs/pytensor/graphs/contributors>`_.
 * All Theano users that have given us feedback.
 * Our random number generator implementation on CPU and GPU uses the MRG31k3p algorithm that is described in:
 

doc/conf.py

@@ -69,8 +69,8 @@
 master_doc = "index"
 
 # General substitutions.
-project = "Pytensor"
-copyright = "Pytensor Developers, 2021; PyMC Developers, 2020-2021; 2008--2019, LISA lab"
+project = "PyTensor"
+copyright = "PyTensor Developers, 2021; PyMC Developers, 2020-2021; 2008--2019, LISA lab"
 
 # The default replacements for |version| and |release|, also used in various
 # other places throughout the built documents.
@@ -255,7 +255,7 @@ def find_source():
 # (source start file, target name, title, author, document class
 # [howto/manual]).
 latex_documents = [
-    ("index", "pytensor.tex", "Pytensor Documentation", "Pytensor Developers", "manual"),
+    ("index", "pytensor.tex", "PyTensor Documentation", "PyTensor Developers", "manual"),
 ]
 
 # The name of an image file (relative to this directory) to place at the top of

doc/core_development_guide.rst

@@ -3,35 +3,35 @@
 Core Development Guide
 =======================
 
-The documentation of the core components of Pytensor is still a work in
+The documentation of the core components of PyTensor is still a work in
 progress. For now this is a list of bits and pieces on the subject,
 some of them might be outdated though:
 
 
-* :ref:`pytensor_type` -- Tutorial for writing a new type in Pytensor. It
-  introduces the basics concerning Pytensor datatypes.
+* :ref:`pytensor_type` -- Tutorial for writing a new type in PyTensor. It
+  introduces the basics concerning PyTensor datatypes.
 
 * :ref:`pytensor_ctype` -- Tutorial on how to make your type C-friendly.
 
-* :ref:`views_and_inplace` -- This is somewhere between extending Pytensor and
-  describing how Pytensor works internally; it talks about views and inplace
+* :ref:`views_and_inplace` -- This is somewhere between extending PyTensor and
+  describing how PyTensor works internally; it talks about views and inplace
   operations.
 
-* :ref:`graph_rewriting` -- Tutorial on how graph rewriting works in Pytensor.
+* :ref:`graph_rewriting` -- Tutorial on how graph rewriting works in PyTensor.
 
-* :ref:`pipeline` -- Describes the steps of compiling an Pytensor Function.
+* :ref:`pipeline` -- Describes the steps of compiling an PyTensor Function.
 
 * :ref:`graphstructures` -- Describes the symbolic graphs generated by
   :mod:`pytensor.scan`.
 
-* :ref:`unittest` -- Tutorial on how to use unittest in testing Pytensor.
+* :ref:`unittest` -- Tutorial on how to use unittest in testing PyTensor.
 
 * :ref:`sandbox_debugging_step_mode` -- How to step through the execution of
-  an Pytensor function and print the inputs and outputs of each op.
+  an PyTensor function and print the inputs and outputs of each op.
 
 * :ref:`sandbox_elemwise` -- Description of element wise operations.
 
-* :ref:`sandbox_randnb` -- Description of how Pytensor deals with random
+* :ref:`sandbox_randnb` -- Description of how PyTensor deals with random
   numbers.
 
-* :ref:`sparse` -- Description of the ``sparse`` type in Pytensor.
+* :ref:`sparse` -- Description of the ``sparse`` type in PyTensor.

doc/dev_start_guide.rst

@@ -16,9 +16,9 @@ This is a good way to make sure that proposed changes will be accepted.
 Resources
 =========
 
-See :ref:`pytensor-community` for a list of Pytensor resources.
+See :ref:`pytensor-community` for a list of PyTensor resources.
 
-The Theano Google group is also relevant to (early) Pytensor versions:
+The Theano Google group is also relevant to (early) PyTensor versions:
 `theano-dev`_.
 
 .. _theano-dev: https://groups.google.com/group/theano-dev
@@ -100,7 +100,7 @@ Here is an example on how to add a docstring to a class.
         See Also
         --------
         `Elemwise`: This functionality is already available; just execute
-        ``x * 2`` with ``x`` being an Pytensor variable.
+        ``x * 2`` with ``x`` being an PyTensor variable.
         """
 
         def make_node(self, x: Variable):
@@ -119,10 +119,10 @@ Installation and configuration
 ==============================
 
 To submit PRs, create an account on `GitHub <http://www.github.com/>`_ and fork
-`Pytensor <http://www.github.com/pymc-devs/pytensor>`_.
+`PyTensor <http://www.github.com/pymc-devs/pytensor>`_.
 
-This will create your own clone of the Pytensor project on GitHub's servers. It is customary
-to assign this Git remote the name "origin", and the official Pytensor repository
+This will create your own clone of the PyTensor project on GitHub's servers. It is customary
+to assign this Git remote the name "origin", and the official PyTensor repository
 the name "upstream".
 
 
@@ -133,14 +133,14 @@ Clone your fork locally with
 
 .. code-block:: bash
 
-    git clone git@github.com:YOUR_GITHUB_LOGIN/Pytensor.git
+    git clone git@github.com:YOUR_GITHUB_LOGIN/PyTensor.git
 
 For this URL to work, you must set your public SSH keys inside your
 `GitHub account setting <https://github.com/settings/ssh>`_.
 
 From your local repository, your fork on GitHub will be called "origin" by default.
 
-Next, create a remote entry for the original (i.e. upstream) Pytensor repository
+Next, create a remote entry for the original (i.e. upstream) PyTensor repository
 with the following:
 
 .. code-block:: bash
@@ -149,7 +149,7 @@ with the following:
 
 .. note::
 
-    You can choose a name other than "upstream" to reference the official Pytensor
+    You can choose a name other than "upstream" to reference the official PyTensor
     repository.
 
 Setting up the your local development environment
@@ -180,7 +180,7 @@ checks are performed before each commit:
 
 
 The virtual environment will need to be activated in any environment
-(e.g. shells, IDEs, etc.) that plans to run the Pytensor tests or add commits to the
+(e.g. shells, IDEs, etc.) that plans to run the PyTensor tests or add commits to the
 project repository.
 
 You can now test your environment/code by running ``pytest`` in the project's root