[yt-svn] commit/yt: 3 new changesets
commits-noreply at bitbucket.org
commits-noreply at bitbucket.org
Mon Apr 17 12:50:30 PDT 2017
3 new commits in yt:
https://bitbucket.org/yt_analysis/yt/commits/a860a1392239/
Changeset: a860a1392239
Branch: yt
User: StatMarianne
Date: 2017-04-17 18:14:26+00:00
Summary: Capitalize Mercurial (consistency).
Affected #: 1 file
diff -r 9e188aa057c91b6ff79c5c7e0b9680af6de17517 -r a860a139223929f40727aab638b54f7271aec7d7 CONTRIBUTING.rst
--- a/CONTRIBUTING.rst
+++ b/CONTRIBUTING.rst
@@ -54,7 +54,7 @@
help out.
The easiest way to help out is to fork the main yt repository (where the
-documentation lives in the ``doc`` directory in the root of the yt mercurial
+documentation lives in the ``doc`` directory in the root of the yt Mercurial
repository) and then make your changes in your own fork. When you are done,
issue a pull request through the website for your new fork, and we can comment
back and forth and eventually accept your changes. See :ref:`sharing-changes` for
@@ -210,14 +210,14 @@
yt is a community project!
We are very happy to accept patches, features, and bugfixes from any member of
-the community! yt is developed using mercurial, primarily because it enables
+the community! yt is developed using Mercurial, primarily because it enables
very easy and straightforward submission of changesets. We're eager to hear
from you, and if you are developing yt, we encourage you to subscribe to the
`developer mailing list
<http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org>`_. Please feel
free to hack around, commit changes, and send them upstream.
-.. note:: If you already know how to use the `mercurial version control system
+.. note:: If you already know how to use the `Mercurial version control system
<http://mercurial-scm.org>`_ and are comfortable with handling it yourself,
the quickest way to contribute to yt is to `fork us on BitBucket
<http://bitbucket.org/yt_analysis/yt/fork>`_, make your changes, push the
@@ -258,7 +258,7 @@
We provide a brief introduction to submitting changes here. yt thrives on the
strength of its communities (http://arxiv.org/abs/1301.7064 has further
discussion) and we encourage contributions from any user. While we do not
-discuss version control, mercurial or the advanced usage of BitBucket in detail
+discuss version control, Mercurial or the advanced usage of BitBucket in detail
here, we do provide an outline of how to submit changes and we are happy to
provide further assistance or guidance.
@@ -350,7 +350,7 @@
to obtain the yt source code if you did not build yt using the install
script.
-The root directory of the yt mercurial repository contains a number of
+The root directory of the yt Mercurial 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
the following subdirectories:
@@ -526,15 +526,15 @@
* http://mercurial-scm.org/
* http://mercurial-scm.org/wiki
-The commands that are essential for using mercurial include:
+The commands that are essential for using Mercurial include:
-* ``hg help`` which provides help for any mercurial command. For example, you
+* ``hg help`` which provides help for any Mercurial command. For example, you
can learn more about the ``log`` command by doing ``hg help log``. Other useful
topics to use with ``hg help`` are ``hg help glossary``, ``hg help config``,
``hg help extensions``, and ``hg help revsets``.
* ``hg commit`` which commits changes in the working directory to the
repository, creating a new "changeset object."
-* ``hg add`` which adds a new file to be tracked by mercurial. This does
+* ``hg add`` which adds a new file to be tracked by Mercurial. This does
not change the working directory.
* ``hg pull`` which pulls (from an optional path specifier) changeset
objects from a remote source. The working directory is not modified.
@@ -549,13 +549,13 @@
* ``hg merge`` which combines two changesets to make a union of their lines
of development. This updates the working directory.
-We are happy to asnswers questions about mercurial use on our IRC, slack
+We are happy to asnswers questions about Mercurial use on our IRC, slack
chat or on the mailing list to walk you through any troubles you might have.
-Here are some general suggestions for using mercurial with yt:
+Here are some general suggestions for using Mercurial with yt:
* Named branches are to be avoided. Try using bookmarks (``see hg help
bookmark``) to track work. (`More info about bookmarks is available on the
- mercurial wiki <http://mercurial-scm.org/wiki/Bookmarks>`_)
+ Mercurial wiki <http://mercurial-scm.org/wiki/Bookmarks>`_)
* Make sure you set a username in your ``~/.hgrc`` before you commit any
changes! All of the tutorials above will describe how to do this as one of
the very first steps.
@@ -583,7 +583,7 @@
The simplest way to submit changes to yt is to do the following:
-* Build yt from the mercurial repository
+* Build yt from the Mercurial repository
* Navigate to the root of the yt repository
* Make some changes and commit them
* Fork the `yt repository on BitBucket <https://bitbucket.org/yt_analysis/yt>`_
@@ -595,7 +595,7 @@
#. If you have used the installation script, the source code for yt can be
found in ``$YT_DEST/src/yt-hg``. Alternatively see
:ref:`source-installation` for instructions on how to build yt from the
- mercurial repository. (Below, in :ref:`reading-source`, we describe how to
+ Mercurial repository. (Below, in :ref:`reading-source`, we describe how to
find items of interest.)
#. Edit the source file you are interested in and
test your changes. (See :ref:`testing` for more information.)
https://bitbucket.org/yt_analysis/yt/commits/622f9dede6f5/
Changeset: 622f9dede6f5
Branch: yt
User: StatMarianne
Date: 2017-04-17 18:20:47+00:00
Summary: Refer to local repository as <REPOSITORY_NAME>
Affected #: 1 file
diff -r a860a139223929f40727aab638b54f7271aec7d7 -r 622f9dede6f5bd7f01ed56668dd101da4fb9f697 CONTRIBUTING.rst
--- a/CONTRIBUTING.rst
+++ b/CONTRIBUTING.rst
@@ -301,7 +301,13 @@
This downloads that new forked repository to your local machine, so that you
can access it, read it, make modifications, etc. It will put the repository in
a local directory of the same name as the repository in the current working
-directory. You should also run the following command, to make sure you are at
+directory.
+
+.. code-block:: bash
+
+ $ cd <REPOSITORY_NAME>
+
+You should also run the following command, to make sure you are at
the "yt" branch, and not other ones like "stable" (this will be important
later when you want to submit your pull requests):
@@ -315,7 +321,6 @@
.. code-block:: bash
- $ cd <REPOSITORY_NAME>
$ hg log -l 5
Using the revision specifier (the number or hash identifier next to each
@@ -334,7 +339,6 @@
.. code-block:: bash
- $ cd <REPOSITORY_NAME>
$ python2.7 setup.py develop
This will rebuild all C modules as well.
@@ -767,7 +771,7 @@
.. code-block:: bash
- $ cd $YT_HG
+ $ cd <REPOSITORY_NAME>
$ flake8 ./yt
This will print out any ``flake8`` errors or warnings that your newly added code
https://bitbucket.org/yt_analysis/yt/commits/a5836030bd53/
Changeset: a5836030bd53
Branch: yt
User: StatMarianne
Date: 2017-04-17 18:56:54+00:00
Summary: Update mentions of python2.7 to just be python
Affected #: 1 file
diff -r 622f9dede6f5bd7f01ed56668dd101da4fb9f697 -r a5836030bd53a53f9873e433566b6b691939752e CONTRIBUTING.rst
--- a/CONTRIBUTING.rst
+++ b/CONTRIBUTING.rst
@@ -339,7 +339,7 @@
.. code-block:: bash
- $ python2.7 setup.py develop
+ $ python setup.py develop
This will rebuild all C modules as well.
@@ -441,14 +441,14 @@
.. code-block:: bash
- $ python2.7 setup.py develop
+ $ python setup.py develop
If you have previously "installed" via ``setup.py install`` you have to
re-install:
.. code-block:: bash
- $ python2.7 setup.py install
+ $ python setup.py install
Only one of these two options is needed.
@@ -470,13 +470,13 @@
.. code-block:: bash
- $ python2.7 setup.py build --compiler=mingw32 develop
+ $ python setup.py build --compiler=mingw32 develop
or
.. code-block:: bash
- $ python2.7 setup.py build --compiler=mingw32 install
+ $ python setup.py build --compiler=mingw32 install
.. _requirements-for-code-submission:
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