Welcome to mirror list, hosted at ThFree Co, Russian Federation.

git.blender.org/blender.git - Unnamed repository; edit this file 'description' to name the repository.
summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorCampbell Barton <ideasman42@gmail.com>2012-12-05 07:38:01 +0400
committerCampbell Barton <ideasman42@gmail.com>2012-12-05 07:38:01 +0400
commit57d7c1f226811d5f6f5d73d8bd498e2b72a603c2 (patch)
tree353e2b329c65f125509a8837b7e39156ae2a965d /doc
parentaf51827dda90e5402d9e4a476a8ada3f422dda13 (diff)
pydna experimental ctypes DNA api was broken with more recent python versions, and some minor doc edits.
Diffstat (limited to 'doc')
-rw-r--r--doc/python_api/rst/info_gotcha.rst12
1 files changed, 6 insertions, 6 deletions
diff --git a/doc/python_api/rst/info_gotcha.rst b/doc/python_api/rst/info_gotcha.rst
index 08548ea73e5..a48cb8fc15e 100644
--- a/doc/python_api/rst/info_gotcha.rst
+++ b/doc/python_api/rst/info_gotcha.rst
@@ -494,7 +494,7 @@ Heres an example of threading supported by Blender:
t.join()
-This an example of a timer which runs many times a second and moves the default cube continuously while Blender runs (Unsupported).
+This an example of a timer which runs many times a second and moves the default cube continuously while Blender runs **(Unsupported)**.
.. code-block:: python
@@ -517,7 +517,7 @@ So far, no work has gone into making Blender's python integration thread safe, s
.. note::
- Pythons threads only allow co-currency and won't speed up your scripts on multi-processor systems, the ``subprocess`` and ``multiprocess`` modules can be used with blender and make use of multiple CPU's too.
+ Pythons threads only allow co-currency and won't speed up your scripts on multi-processor systems, the ``subprocess`` and ``multiprocess`` modules can be used with Blender and make use of multiple CPU's too.
Help! My script crashes Blender
@@ -540,7 +540,7 @@ Here are some general hints to avoid running into these problems.
.. note::
To find the line of your script that crashes you can use the ``faulthandler`` module.
- See `faulthandler docs<http://docs.python.org/dev/library/faulthandler.html>`_.
+ See `faulthandler docs <http://docs.python.org/dev/library/faulthandler.html>`_.
While the crash may be in Blenders C/C++ code, this can help a lot to track down the area of the script that causes the crash.
@@ -548,7 +548,7 @@ Here are some general hints to avoid running into these problems.
Undo/Redo
---------
-Undo invalidates all :class:`bpy.types.ID` instances (Object, Scene, Mesh etc).
+Undo invalidates all :class:`bpy.types.ID` instances (Object, Scene, Mesh, Lamp... etc).
This example shows how you can tell undo changes the memory locations.
@@ -666,9 +666,9 @@ But take care because this is limited to scripts accessing the variable which is
sys.exit
========
-Some python modules will call sys.exit() themselves when an error occurs, while not common behavior this is something to watch out for because it may seem as if blender is crashing since sys.exit() will quit blender immediately.
+Some python modules will call ``sys.exit()`` themselves when an error occurs, while not common behavior this is something to watch out for because it may seem as if blender is crashing since ``sys.exit()`` will quit blender immediately.
For example, the ``optparse`` module will print an error and exit if the arguments are invalid.
-An ugly way of troubleshooting this is to set ``sys.exit = None`` and see what line of python code is quitting, you could of course replace ``sys.exit``/ with your own function but manipulating python in this way is bad practice.
+An ugly way of troubleshooting this is to set ``sys.exit = None`` and see what line of python code is quitting, you could of course replace ``sys.exit`` with your own function but manipulating python in this way is bad practice.