[yt-svn] commit/yt: 2 new changesets
commits-noreply at bitbucket.org
commits-noreply at bitbucket.org
Sun May 7 15:34:36 PDT 2017
2 new commits in yt:
https://bitbucket.org/yt_analysis/yt/commits/9a4dafc1ea65/
Changeset: 9a4dafc1ea65
User: StatMarianne
Date: 2017-05-07 20:25:41+00:00
Summary: Harmonize placeholders.
Affected #: 1 file
diff -r c9add70d3bcf25eb91127e65a00e5d9af0ff3455 -r 9a4dafc1ea65a70d59f249617ba6569908155577 CONTRIBUTING.rst
--- a/CONTRIBUTING.rst
+++ b/CONTRIBUTING.rst
@@ -302,7 +302,7 @@
.. code-block:: bash
- $ cd <REPOSITORY_NAME>
+ $ cd yt
Verify that you are on the master branch of yt by running:
@@ -351,7 +351,7 @@
The root directory of the yt git repository contains a number of
subdirectories with different components of the code. Most of the yt source
-code is contained in the yt subdirectory. This directory its self contains
+code is contained in the yt subdirectory. This directory itself contains
the following subdirectories:
``frontends``
@@ -597,7 +597,7 @@
#. Add your remote repository with a unique name identifier. It can be anything;
your GitHub user name is one possible choice::
- git remote add <YourUniqueIdentifier> https://github.com/YourUsername/yt/
+ git remote add <YourUniqueIdentifier> https://github.com/<USER>/yt
#. Push your changes to your remote fork using the unique identifier you just
created and the command::
@@ -612,8 +612,8 @@
between your machine and GitHub. If you prefer to use SSH - or
perhaps you're behind a proxy that doesn't play well with SSL via
HTTPS - you may want to set up an `SSH key`_ on GitHub. Then, you use
- the syntax ``ssh://git@github.com/YourUsername/yt``, or equivalent, in
- place of ``https://github.com/YourUsername/yt`` in git commands.
+ the syntax ``ssh://git@github.com/<USER>/yt``, or equivalent, in
+ place of ``https://github.com/<USER>/yt`` in git commands.
For consistency, all commands we list in this document will use the HTTPS
protocol.
@@ -670,11 +670,11 @@
$ pip install flake8
And then navigate to the root of the yt repository and run ``flake8`` on the
-``yt`` folder:
+``yt`` subdirectory:
.. code-block:: bash
- $ cd <REPOSITORY_NAME>
+ $ cd yt
$ flake8 ./yt
This will print out any ``flake8`` errors or warnings that your newly added code
@@ -702,7 +702,7 @@
(something_else))`` should be rewritten as
``if something and something_else``. Python is more forgiving than C.
* Avoid copying memory when possible. For example, don't do
- ``a = a.reshape(3,4)`` when ``a.shape = (3,4)`` will do, and ``a = a * 3``
+ ``a = a.reshape(3, 4)`` when ``a.shape = (3, 4)`` will do, and ``a = a * 3``
should be ``np.multiply(a, 3, a)``.
* In general, avoid all double-underscore method names: ``__something`` is
usually unnecessary.
@@ -848,13 +848,13 @@
use the function. Use the variables 'ds' for the dataset, 'pc' for
a plot collection, 'c' for a center, and 'L' for a vector.
- >>> a=[1,2,3]
- >>> print [x + 3 for x in a]
+ >>> a = [1, 2, 3]
+ >>> print([x + 3 for x in a])
[4, 5, 6]
- >>> print "a\n\nb"
+ >>> print("a\n\nb")
a
+
b
-
"""
Variable Names and Enzo-isms
https://bitbucket.org/yt_analysis/yt/commits/58d0040aad81/
Changeset: 58d0040aad81
User: ngoldbaum
Date: 2017-05-07 22:34:26+00:00
Summary: Merge pull request #1377 from mkcor/consistent-notation
Harmonize placeholders and improve style.
Affected #: 1 file
diff -r c9add70d3bcf25eb91127e65a00e5d9af0ff3455 -r 58d0040aad81f45b010a8ac67b41893c7fb6df24 CONTRIBUTING.rst
--- a/CONTRIBUTING.rst
+++ b/CONTRIBUTING.rst
@@ -302,7 +302,7 @@
.. code-block:: bash
- $ cd <REPOSITORY_NAME>
+ $ cd yt
Verify that you are on the master branch of yt by running:
@@ -351,7 +351,7 @@
The root directory of the yt git repository contains a number of
subdirectories with different components of the code. Most of the yt source
-code is contained in the yt subdirectory. This directory its self contains
+code is contained in the yt subdirectory. This directory itself contains
the following subdirectories:
``frontends``
@@ -597,7 +597,7 @@
#. Add your remote repository with a unique name identifier. It can be anything;
your GitHub user name is one possible choice::
- git remote add <YourUniqueIdentifier> https://github.com/YourUsername/yt/
+ git remote add <YourUniqueIdentifier> https://github.com/<USER>/yt
#. Push your changes to your remote fork using the unique identifier you just
created and the command::
@@ -612,8 +612,8 @@
between your machine and GitHub. If you prefer to use SSH - or
perhaps you're behind a proxy that doesn't play well with SSL via
HTTPS - you may want to set up an `SSH key`_ on GitHub. Then, you use
- the syntax ``ssh://git@github.com/YourUsername/yt``, or equivalent, in
- place of ``https://github.com/YourUsername/yt`` in git commands.
+ the syntax ``ssh://git@github.com/<USER>/yt``, or equivalent, in
+ place of ``https://github.com/<USER>/yt`` in git commands.
For consistency, all commands we list in this document will use the HTTPS
protocol.
@@ -670,11 +670,11 @@
$ pip install flake8
And then navigate to the root of the yt repository and run ``flake8`` on the
-``yt`` folder:
+``yt`` subdirectory:
.. code-block:: bash
- $ cd <REPOSITORY_NAME>
+ $ cd yt
$ flake8 ./yt
This will print out any ``flake8`` errors or warnings that your newly added code
@@ -702,7 +702,7 @@
(something_else))`` should be rewritten as
``if something and something_else``. Python is more forgiving than C.
* Avoid copying memory when possible. For example, don't do
- ``a = a.reshape(3,4)`` when ``a.shape = (3,4)`` will do, and ``a = a * 3``
+ ``a = a.reshape(3, 4)`` when ``a.shape = (3, 4)`` will do, and ``a = a * 3``
should be ``np.multiply(a, 3, a)``.
* In general, avoid all double-underscore method names: ``__something`` is
usually unnecessary.
@@ -848,13 +848,13 @@
use the function. Use the variables 'ds' for the dataset, 'pc' for
a plot collection, 'c' for a center, and 'L' for a vector.
- >>> a=[1,2,3]
- >>> print [x + 3 for x in a]
+ >>> a = [1, 2, 3]
+ >>> print([x + 3 for x in a])
[4, 5, 6]
- >>> print "a\n\nb"
+ >>> print("a\n\nb")
a
+
b
-
"""
Variable Names and Enzo-isms
Repository URL: https://bitbucket.org/yt_analysis/yt/
--
This is a commit notification from bitbucket.org. You are receiving
this because you have the service enabled, addressing the recipient of
this email.
More information about the yt-svn
mailing list