to keep the source tree pristine, you can change the build directory with the
:option:`--build-base` option. For example::
- python setup.py build --build-base=/tmp/pybuild/foo-1.0
+ python setup.py build --build-base=/path/to/pybuild/foo-1.0
(Or you could do this permanently with a directive in your system or personal
Distutils configuration file; see section :ref:`inst-config-files`.) Normally, this
making an explicit call into this module at termination. ::
try:
- _count = int(open("/tmp/counter").read())
+ _count = int(open("counter").read())
except IOError:
_count = 0
_count = _count + n
def savecounter():
- open("/tmp/counter", "w").write("%d" % _count)
+ open("counter", "w").write("%d" % _count)
import atexit
atexit.register(savecounter)
instead, with code like this::
import cgitb
- cgitb.enable(display=0, logdir="/tmp")
+ cgitb.enable(display=0, logdir="/path/to/logdir")
It's very helpful to use this feature during script development. The reports
produced by :mod:`cgitb` provide information that can save you a lot of time in
Example::
>>> import imghdr
- >>> imghdr.what('/tmp/bass.gif')
+ >>> imghdr.what('bass.gif')
'gif'
>>> import mailcap
>>> d=mailcap.getcaps()
- >>> mailcap.findmatch(d, 'video/mpeg', filename='/tmp/tmp1223')
- ('xmpeg /tmp/tmp1223', {'view': 'xmpeg %s'})
+ >>> mailcap.findmatch(d, 'video/mpeg', filename='tmp1223')
+ ('xmpeg tmp1223', {'view': 'xmpeg %s'})
headers, and that you have right to post on the particular newsgroup)::
>>> s = nntplib.NNTP('news.gmane.org')
- >>> f = open('/tmp/article.txt', 'rb')
+ >>> f = open('article.txt', 'rb')
>>> s.post(f)
'240 Article posted successfully.'
>>> s.quit()
For example, consider this hypothetical command-line::
- prog -v --report /tmp/report.txt foo bar
+ prog -v --report report.txt foo bar
``-v`` and ``--report`` are both options. Assuming that ``--report``
-takes one argument, ``/tmp/report.txt`` is an option argument. ``foo`` and
+takes one argument, ``report.txt`` is an option argument. ``foo`` and
``bar`` are positional arguments.
Example::
>>> import pipes
- >>> t=pipes.Template()
+ >>> t = pipes.Template()
>>> t.append('tr a-z A-Z', '--')
- >>> f=t.open('/tmp/1', 'w')
+ >>> f = t.open('pipefile', 'w')
>>> f.write('hello world')
>>> f.close()
- >>> open('/tmp/1').read()
+ >>> open('pipefile').read()
'HELLO WORLD'
To use the module, you must first create a :class:`Connection` object that
represents the database. Here the data will be stored in the
-:file:`/tmp/example` file::
+:file:`example.db` file::
import sqlite3
- conn = sqlite3.connect('/tmp/example')
+ conn = sqlite3.connect('example.db')
You can also supply the special name ``:memory:`` to create a database in RAM.
# run the new command using the given tracer
tracer.run('main()')
- # make a report, placing output in /tmp
+ # make a report, placing output in the current directory
r = tracer.results()
- r.write_results(show_missing=True, coverdir="/tmp")
+ r.write_results(show_missing=True, coverdir=".")
also allows an item of :data:`sys.path` to be a string naming a ZIP file archive.
The ZIP archive can contain a subdirectory structure to support package imports,
and a path within the archive can be specified to only import from a
-subdirectory. For example, the path :file:`/tmp/example.zip/lib/` would only
+subdirectory. For example, the path :file:`example.zip/lib/` would only
import from the :file:`lib/` subdirectory within the archive.
Any files may be present in the ZIP archive, but only files :file:`.py` and
Here is an example that imports a module from a ZIP archive - note that the
:mod:`zipimport` module is not explicitly used. ::
- $ unzip -l /tmp/example.zip
- Archive: /tmp/example.zip
+ $ unzip -l example.zip
+ Archive: example.zip
Length Date Time Name
-------- ---- ---- ----
8467 11-26-02 22:30 jwzthreading.py
$ ./python
Python 2.3 (#1, Aug 1 2003, 19:54:32)
>>> import sys
- >>> sys.path.insert(0, '/tmp/example.zip') # Add .zip file to front of path
+ >>> sys.path.insert(0, 'example.zip') # Add .zip file to front of path
>>> import jwzthreading
>>> jwzthreading.__file__
- '/tmp/example.zip/jwzthreading.py'
+ 'example.zip/jwzthreading.py'
::
- >>> f = open('/tmp/workfile', 'w')
+ >>> f = open('workfile', 'w')
.. XXX str(f) is <io.TextIOWrapper object at 0x82e8dc4>
>>> print(f)
- <open file '/tmp/workfile', mode 'w' at 80a0960>
+ <open file 'workfile', mode 'w' at 80a0960>
The first argument is a string containing the filename. The second argument is
another string containing a few characters describing the way in which the file
the reference point. *from_what* can be omitted and defaults to 0, using the
beginning of the file as the reference point. ::
- >>> f = open('/tmp/workfile', 'rb+')
+ >>> f = open('workfile', 'rb+')
>>> f.write(b'0123456789abcdef')
16
>>> f.seek(5) # Go to the 6th byte in the file
suite finishes, even if an exception is raised on the way. It is also much
shorter than writing equivalent :keyword:`try`\ -\ :keyword:`finally` blocks::
- >>> with open('/tmp/workfile', 'r') as f:
+ >>> with open('workfile', 'r') as f:
... read_data = f.read()
>>> f.closed
True
Gerald S. Williams
Steven Willis
Frank Willison
+Geoff Wilson
Greg V. Wilson
J Derek Wilson
Paul Winkler
Documentation
-------------
+- Issue #8890: Stop advertising an insecure practice by replacing uses
+ of the /tmp directory with better alternatives in the documentation.
+ Patch by Geoff Wilson.
+
- Issue #17203: add long option names to unittest discovery docs.
- Issue #13094: add "Why do lambdas defined in a loop with different values
projects / python / commitdiff