[py-svn] r63539 - in py/trunk: . doc doc/_static doc/_templates doc/img py/doc
hpk at codespeak.net
hpk at codespeak.net
Thu Apr 2 15:24:06 CEST 2009
Author: hpk
Date: Thu Apr 2 15:24:02 2009
New Revision: 63539
Added:
py/trunk/doc/
- copied from r63522, py/trunk/py/doc/
py/trunk/doc/Makefile
- copied unchanged from r63538, py/trunk/py/doc/Makefile
py/trunk/doc/__init__.py
- copied unchanged from r63538, py/trunk/py/doc/__init__.py
py/trunk/doc/_static/
- copied from r63538, py/trunk/py/doc/_static/
py/trunk/doc/_templates/
- copied from r63538, py/trunk/py/doc/_templates/
py/trunk/doc/bin.txt
- copied unchanged from r63538, py/trunk/py/doc/bin.txt
py/trunk/doc/code.txt
- copied unchanged from r63538, py/trunk/py/doc/code.txt
py/trunk/doc/coding-style.txt
- copied unchanged from r63538, py/trunk/py/doc/coding-style.txt
py/trunk/doc/conf.py
- copied unchanged from r63538, py/trunk/py/doc/conf.py
py/trunk/doc/confrest.py
- copied unchanged from r63538, py/trunk/py/doc/confrest.py
py/trunk/doc/contact.txt
- copied unchanged from r63538, py/trunk/py/doc/contact.txt
py/trunk/doc/download.txt
- copied unchanged from r63538, py/trunk/py/doc/download.txt
py/trunk/doc/execnet.txt
- copied unchanged from r63538, py/trunk/py/doc/execnet.txt
py/trunk/doc/img/
- copied from r63538, py/trunk/py/doc/img/
py/trunk/doc/impl-test.txt
- copied unchanged from r63538, py/trunk/py/doc/impl-test.txt
py/trunk/doc/index.txt
- copied unchanged from r63538, py/trunk/py/doc/index.txt
py/trunk/doc/io.txt
- copied unchanged from r63538, py/trunk/py/doc/io.txt
py/trunk/doc/links.txt
- copied unchanged from r63538, py/trunk/py/doc/links.txt
py/trunk/doc/log.txt
- copied unchanged from r63538, py/trunk/py/doc/log.txt
py/trunk/doc/make.bat
- copied unchanged from r63538, py/trunk/py/doc/make.bat
py/trunk/doc/misc.txt
- copied unchanged from r63538, py/trunk/py/doc/misc.txt
py/trunk/doc/path.txt
- copied unchanged from r63538, py/trunk/py/doc/path.txt
py/trunk/doc/release-0.9.0.txt
- copied unchanged from r63538, py/trunk/py/doc/release-0.9.0.txt
py/trunk/doc/release-0.9.2.txt
- copied unchanged from r63538, py/trunk/py/doc/release-0.9.2.txt
py/trunk/doc/release-1.0.0.txt
- copied unchanged from r63538, py/trunk/py/doc/release-1.0.0.txt
py/trunk/doc/releases.txt
- copied unchanged from r63538, py/trunk/py/doc/releases.txt
py/trunk/doc/roles.py
- copied unchanged from r63538, py/trunk/py/doc/roles.py
py/trunk/doc/style.css
- copied unchanged from r63538, py/trunk/py/doc/style.css
py/trunk/doc/test-config.txt
- copied unchanged from r63538, py/trunk/py/doc/test-config.txt
py/trunk/doc/test-dist.txt
- copied unchanged from r63538, py/trunk/py/doc/test-dist.txt
py/trunk/doc/test-examples.txt
- copied unchanged from r63538, py/trunk/py/doc/test-examples.txt
py/trunk/doc/test-ext.txt
- copied unchanged from r63538, py/trunk/py/doc/test-ext.txt
py/trunk/doc/test-features.txt
- copied unchanged from r63538, py/trunk/py/doc/test-features.txt
py/trunk/doc/test-plugins.txt
- copied unchanged from r63538, py/trunk/py/doc/test-plugins.txt
py/trunk/doc/test-quickstart.txt
- copied unchanged from r63538, py/trunk/py/doc/test-quickstart.txt
py/trunk/doc/test-statemanage.txt
- copied unchanged from r63538, py/trunk/py/doc/test-statemanage.txt
py/trunk/doc/test.txt
- copied unchanged from r63538, py/trunk/py/doc/test.txt
py/trunk/doc/xml.txt
- copied unchanged from r63538, py/trunk/py/doc/xml.txt
Removed:
py/trunk/doc/draft_pyfs
py/trunk/doc/future.txt
py/trunk/doc/why_py.txt
py/trunk/py/doc/
Modified:
py/trunk/MANIFEST
py/trunk/setup.py
Log:
moving py/doc to doc/ and removing some more files
Modified: py/trunk/MANIFEST
==============================================================================
--- py/trunk/MANIFEST (original)
+++ py/trunk/MANIFEST Thu Apr 2 15:24:02 2009
@@ -83,25 +83,30 @@
py/compat/testing/test_textwrap.py
py/compat/textwrap.py
py/conftest.py
+py/doc/Makefile
py/doc/__init__.py
py/doc/bin.txt
py/doc/code.txt
py/doc/coding-style.txt
+py/doc/conf.py
py/doc/confrest.py
py/doc/contact.txt
py/doc/download.txt
-py/doc/draft_pyfs
py/doc/execnet.txt
-py/doc/future.txt
+py/doc/img/pylib.png
py/doc/impl-test.txt
py/doc/index.txt
py/doc/io.txt
py/doc/links.txt
py/doc/log.txt
+py/doc/make.bat
py/doc/misc.txt
py/doc/path.txt
py/doc/release-0.9.0.txt
py/doc/release-0.9.2.txt
+py/doc/release-1.0.0.txt
+py/doc/releases.txt
+py/doc/roles.py
py/doc/style.css
py/doc/test-config.txt
py/doc/test-dist.txt
@@ -110,8 +115,8 @@
py/doc/test-features.txt
py/doc/test-plugins.txt
py/doc/test-quickstart.txt
+py/doc/test-statemanage.txt
py/doc/test.txt
-py/doc/why_py.txt
py/doc/xml.txt
py/env.cmd
py/env.py
@@ -300,12 +305,15 @@
py/test/plugin/pytest_doctest.py
py/test/plugin/pytest_eventlog.py
py/test/plugin/pytest_execnetcleanup.py
+py/test/plugin/pytest_figleaf.py
py/test/plugin/pytest_iocapture.py
py/test/plugin/pytest_monkeypatch.py
py/test/plugin/pytest_plugintester.py
py/test/plugin/pytest_pocoo.py
+py/test/plugin/pytest_pylint.py
py/test/plugin/pytest_pytester.py
py/test/plugin/pytest_restdoc.py
+py/test/plugin/pytest_resultdb.py
py/test/plugin/pytest_resultlog.py
py/test/plugin/pytest_terminal.py
py/test/plugin/pytest_tmpdir.py
Deleted: /py/trunk/py/doc/draft_pyfs
==============================================================================
--- /py/trunk/py/doc/draft_pyfs Thu Apr 2 15:24:02 2009
+++ (empty file)
@@ -1,79 +0,0 @@
-
-Let's do a walk through a memory filesystem.
-
-.. >>> import py
-
-
-working with directories
----------------------------------
-
-Let's create some directories and list them from memory::
-
->>> fs = py.fs.MemoryFS()
->>> fs.mkdir("x")
->>> fs.mkdir("y")
->>> fs.listdir()
-['x', 'y']
-
-
-Creating, removing and reading files
----------------------------------------------
-
->>> f = fs.open('x/file', 'w')
->>> f.write("hello world")
->>> f.close()
->>> fs.listdir("x")
-['file']
->>> f = fs.open("x/file", 'r')
->>> f.readlines()
-['hello world']
->>> f.seek(6)
->>> f.read(3)
-"wor"
->>> f.read()
-"ld"
->>> f.close()
->>> fs.remove("y")
->>> fs.listdir()
-['x']
->>> fs.remove("non-existent")
-py.error.ENOENT
-
-stat / checking for meta information
----------------------------------------
-
->>> stat = memory.stat("x")
->>> stat.isdir()
-True
->>> stat.isfile()
-False
->>> stat.exists()
-True
->>> stat.islink()
-False
-
-Linking to other objects
---------------------------------------------------------
-
-First an example how to link internally, i.e. within the
-filesystem.
-
->>> fs.link("newitem", "x")
->>> fs.stat("newitem").islink()
-True
->>> fs.stat("newitem").isfile()
-True
->>> fs.remove("newitem") # only deletes the link itself
->>> fs.stat("x").exists()
-
-cross-filesystem references
----------------------------------
-
->>> otherfs = py.fs.MemoryFS()
-
-XXX
-
->>> fs.setproxy("newitem", otherfs, "otheritem")
->>> fs.stat("newitem").exists()
-False
->>> otherfs.mkdir("otheritem")
Deleted: /py/trunk/py/doc/future.txt
==============================================================================
--- /py/trunk/py/doc/future.txt Thu Apr 2 15:24:02 2009
+++ (empty file)
@@ -1,145 +0,0 @@
-=======================================================
-Visions and ideas for further development of the py lib
-=======================================================
-
-
-This document tries to describe directions and guiding ideas
-for the near-future development of the py lib. *Note that all
-statements within this document - even if they sound factual -
-mostly just express thoughts and ideas. They not always refer to
-real code so read with some caution.*
-
-
-Distribute tests ad-hoc across multiple platforms
-======================================================
-
-After some more refactoring and unification of
-the current testing and distribution support code
-we'd like to be able to run tests on multiple
-platforms simultanously and allow for interaction
-and introspection into the (remote) failures.
-
-
-Make APIGEN useful for more projects
-================================================
-
-The new APIGEN tool offers rich information
-derived from running tests against an application:
-argument types and callsites, i.e. it shows
-the places where a particular API is used.
-In its first incarnation, there are still
-some specialties that likely prevent it
-from documenting APIs for other projects.
-We'd like to evolve to a `py.apigen` tool
-that can make use of information provided
-by a py.test run.
-
-Consider APIGEN and pdb integration
-===================================
-
-The information provided by APIGEN can be used in many
-different ways. An example of this could be to write
-an extension to pdb which makes it available.
-Imagine you could issue a pdb command
-"info <function name>" and get information
-regarding incoming, and outgoing types, possible
-exceptions, field types and call sites.
-
-Distribute channels/programs across networks
-================================================
-
-Apart from stabilizing setup/teardown procedures
-for `py.execnet`_, we'd like to generalize its
-implementation to allow connecting two programs
-across multiple hosts, i.e. we'd like to arbitrarily
-send "channels" across the network. Likely this
-will be done by using the "pipe" model, i.e.
-that each channel is actually a pair of endpoints,
-both of which can be independently transported
-across the network. The programs who "own"
-these endpoints remain connected.
-
-.. _`py.execnet`: execnet.html
-
-Benchmarking and persistent storage
-=========================================
-
-For storing test results, but also benchmarking
-and other information, we need a solid way
-to store all kinds of information from test runs.
-We'd like to generate statistics or html-overview
-out of it, but also use such information to determine when
-a certain test broke, or when its performance
-decreased considerably.
-
-.. _`restructured text`: http://docutils.sourceforge.net/docs/user/rst/quickref.html
-.. _`python standard library`: http://www.python.org/doc/2.3.4/lib/lib.html
-.. _`xpython EuroPython 2004 talk`: http://codespeak.net/svn/user/hpk/talks/xpython-talk.txt
-.. _`under the xpy tree`: http://codespeak.net/svn/user/hpk/xpy/xml.py
-.. _`future book`: future.html
-.. _`PEP-324 subprocess module`: http://www.python.org/peps/pep-0324.html
-.. _`subprocess implementation`: http://www.lysator.liu.se/~astrand/popen5/
-.. _`py.test`: test.html
-
-
-.. _`general-path`:
-.. _`a more general view on path objects`:
-
-Refactor path implementations to use a Filesystem Abstraction
-=============================================================
-
-It seems like a good idea to refactor all `py.path`_ Path implementations to
-use an internal Filesystem abstraction. The current code base
-would be transformed to have Filesystem implementations for e.g.
-local, subversion and subversion "working copy" filesystems. Today
-the according code is scattered through path-handling code.
-
-On a related note, Armin Rigo has hacked `pylufs`_ and more recently has
-written `pyfuse`_ which allow to
-implement kernel-level linux filesystems with pure python. Now
-the idea is that the mentioned filesystem implementations would
-be directly usable for such linux-filesystem glue code.
-
-In other words, implementing a `memoryfs`_ or a `dictfs`_ would
-give you two things for free: a filesystem mountable at kernel level
-as well as a uniform "path" object allowing you to access your
-filesystem in convenient ways.
-
-Also interesting to check out is Will McGugan's work on
-his `fs package`_.
-
-I think the main question is what the very fundamental
-filesystem API should look like. Here are some doctests
-on how a `draft py.fs`_ could look like. There also
-is Matthew Scotts `dictproxy patch`_ which adds
-``py.path.dict`` and ``py.path.proxy``.
-
-
-.. _`dictproxy patch`: http://codespeak.net/pipermail/py-dev/attachments/20050128/d9595512/virtual1-0001.bin
-.. _`draft py.fs`: draft_pyfs
-.. _`py.path`: http://codespeak.net/py/dist/path.html
-.. _`fs package`: http://www.willmcgugan.com/2008/09/21/announcing-fs-010-a-python-file-system/#comment-60276
-.. _`memoryfs`: http://codespeak.net/svn/user/arigo/hack/pyfuse/memoryfs.py
-.. _`dictfs`: http://codespeak.net/pipermail/py-dev/2005-January/000191.html
-.. _`pylufs`: http://codespeak.net/svn/user/arigo/hack/pylufs/
-.. _`pyfuse`: http://codespeak.net/svn/user/arigo/hack/pyfuse/
-
-
-Integrate interactive completion
-==================================
-
-It'd be nice to integrate the bash-like
-rlcompleter2_ python command line completer
-into the py lib, and making it work remotely
-and with pdb.
-
-.. _rlcompleter2: http://codespeak.net/rlcompleter2/
-
-Consider more features
-==================================
-
-There are many more features and useful classes
-that might be nice to integrate. For example, we might put
-Armin's `lazy list`_ implementation into the py lib.
-
-.. _`lazy list`: http://codespeak.net/svn/user/arigo/hack/misc/collect.py
Deleted: /py/trunk/py/doc/why_py.txt
==============================================================================
--- /py/trunk/py/doc/why_py.txt Thu Apr 2 15:24:02 2009
+++ (empty file)
@@ -1,182 +0,0 @@
-==============================================
-Why, who, what and how do you do *the py lib*?
-==============================================
-
-
-Why did we start the py lib?
-============================
-
-Among the main motivation for the py lib and its flagship
-py.test tool were:
-
-- to test applications with a testing tool that provides
- advanced features out of the box, yet allows full customization
- per-project.
-
-- distribute applications in an ad-hoc way both for testing
- and for application integration purposes.
-
-- help with neutralizing platform and python version differences
-
-- offer a uniform way to access local and remote file resources
-
-- offer some unique features like micro-threads (greenlets)
-
-
-What is the py libs current focus?
-==================================
-
-testing testing testing
------------------------
-
-Currently, the main focus of the py lib is to get a decent
-`test environment`_, indeed to produce the best one out there.
-Writing, distributing and deploying tests should become
-a snap ... and fun!
-
-On a side note: automated tests fit very well to the dynamism
-of Python. Automated tests ease development and allow fast
-refactoring cycles. Automated tests are a means of
-communication as well.
-
-
-ad-hoc distribution of programs
-------------------------------------
-
-The py lib through its `py.execnet`_ namespaces offers
-support for ad-hoc distributing programs across
-a network and subprocesses. We'd like to generalize
-this approach further to instantiate and let whole
-ad-hoc networks communicate with each other while
-keeping to a simple programming model.
-
-.. _`py.execnet`: execnet.html
-
-
-allowing maximum refactoring in the future ...
-----------------------------------------------
-
-explicit name export control
-............................
-
-In order to allow a fast development pace across versions of
-the py lib there is **explicit name export control**. You
-should only see names which make sense to use from the outside
-and which the py lib developers want to guarantee across versions.
-However, you don't need to treat the ``py`` lib as
-anything special. You can simply use the usual ``import``
-statement and will not notice much of a difference - except that
-the namespaces you'll see from the ``py`` lib are relatively
-clean and have no clutter.
-
-Release policy & API maintenance
-........................................
-
-We'll talk about major, minor and micro numbers as the three
-numbers in "1.2.3" respectively. These are the
-the rough release policies:
-
-- Micro-releases are bug fix releases and should not introduce
- new names to the public API. They may add tests and thus
- further define the behaviour of the py lib. They may
- completly change the implementation but the public API
- tests should continue to run (unless they needed to
- get fixed themselves).
-
-- No **tested feature** of the exported py API shall vanish
- across minor releases until it is marked deprecated.
-
- For example, pure API tests of a future version 1.0 are to
- continue to fully run on 1.1 and so on. If an API gets
- deprecated with a minor release it goes with the next minor
- release. Thus if you don't use deprecated APIs you should
- be able to use the next two minor releases. However, if
- you relied on some untested implementation behaviour,
- you may still get screwed. Solution: add API tests to the
- py lib :-) It's really the tests that make the difference.
-
-- Pure API tests are not allowed to access any implementation
- level details. For example, accessing names starting with
- a single leading '_' is generally seen as an implementation
- level detail.
-
-- major releases *should*, but are not required to, pass
- all API tests of the previous latest major released
- version.
-
-
-the need to find the right *paths* ...
---------------------------------------
-
-Another focus are well tested so called *path* implementations
-that allow you to seemlessly work with different backends,
-currently a local filesystem, subversion working copies and
-subversion remote URLs.
-
-How does py development work?
-=============================
-
-Communication and coding style
-------------------------------
-
-We are discussing things on our `py-dev mailing list`_
-and collaborate via the codespeak subversion repository.
-
-We follow a `coding style`_ which strongly builds on `PEP 8`_,
-the basic python coding style document.
-
-It's easy to get commit rights especially if you are an
-experienced python developer and share some of the
-frustrations described above.
-
-Licensing
------------------
-
-The Py lib is released under the MIT license and all
-contributors need to release their contributions
-under this license as well.
-
-connections with PyPy_
----------------------------------
-
-A major motivation for writing the py lib stems from needs
-during PyPy_ development, most importantly testing and
-file system access issues. PyPy puts a lot of pressure
-on a testing environment and thus is a good **reality test**.
-
-Who is "we"?
-=============================
-
-Some initial code was written from *Jens-Uwe Mager* and *Holger
-Krekel*, after which Holger continued on a previous
-incarnations of the py.test tool (known first as 'utest', then
-as 'std.utest', now for some 2 years 'py.test').
-
-Helpful discussions took place with *Martijn Faassen*, *Stephan
-Schwarzer*, *Brian Dorsey*, *Grigh Gheorghiu* and then
-*Armin Rigo* who contributed important parts.
-He and Holger came up with a couple of iterations of the
-testing-code that reduced the API to basically nothing: just the
-plain assert statement and a ``py.test.raises`` method to
-check for occuring exceptions within tests.
-
-Currently (as of 2007), there are more people involved
-and also have worked funded through merlinux_ and the
-PyPy EU project, Carl Friedrich Bolz, Guido Wesdorp
-and Maciej Fijalkowski who contributed particularly
-in 2006 and 2007 major parts of the py lib.
-
-.. _`talk at EP2004`: http://codespeak.net/svn/user/hpk/talks/std-talk.txt
-.. _`coding style`: coding-style.html
-.. _`PEP 8`: http://www.python.org/peps/pep-0008.html
-.. _`py-dev mailing list`: http://codespeak.net/mailman/listinfo/py-dev
-.. _`test environment`: test.html
-.. _`PyPy`: http://codespeak.net/pypy
-.. _future: future.html
-.. _`py.test tool and library`: test.html
-.. _merlinux: http://merlinux.de
-
---
-
-.. [#] FOSS is an evolving acronym for Free and Open Source Software
-
Modified: py/trunk/setup.py
==============================================================================
--- py/trunk/setup.py (original)
+++ py/trunk/setup.py Thu Apr 2 15:24:02 2009
@@ -1,7 +1,7 @@
"""
setup file for 'py' package based on:
- https://codespeak.net/svn/py/trunk, revision=63342
+ https://codespeak.net/svn/py/trunk, revision=63519
autogenerated by gensetup.py
"""
@@ -32,7 +32,6 @@
"""
-CEXTENSION = False
def main():
setup(
name='py',
@@ -45,10 +44,6 @@
platforms=['unix', 'linux', 'osx', 'cygwin', 'win32'],
author='holger krekel, Guido Wesdorp, Carl Friedrich Bolz, Armin Rigo, Maciej Fijalkowski & others',
author_email='holger at merlinux.eu, py-dev at codespeak.net',
- ext_modules = CEXTENSION and
- [Extension("py.c-extension.greenlet.greenlet",
- ["py/c-extension/greenlet/greenlet.c"]),]
- or [],
entry_points={'console_scripts': ['py.cleanup = py.cmdline:pycleanup',
'py.countloc = py.cmdline:pycountloc',
@@ -137,23 +132,26 @@
'compat/LICENSE',
'compat/testing/test_doctest.txt',
'compat/testing/test_doctest2.txt',
+ 'doc/Makefile',
'doc/bin.txt',
'doc/code.txt',
'doc/coding-style.txt',
'doc/contact.txt',
'doc/download.txt',
- 'doc/draft_pyfs',
'doc/execnet.txt',
- 'doc/future.txt',
+ 'doc/img/pylib.png',
'doc/impl-test.txt',
'doc/index.txt',
'doc/io.txt',
'doc/links.txt',
'doc/log.txt',
+ 'doc/make.bat',
'doc/misc.txt',
'doc/path.txt',
'doc/release-0.9.0.txt',
'doc/release-0.9.2.txt',
+ 'doc/release-1.0.0.txt',
+ 'doc/releases.txt',
'doc/style.css',
'doc/test-config.txt',
'doc/test-dist.txt',
@@ -162,8 +160,8 @@
'doc/test-features.txt',
'doc/test-plugins.txt',
'doc/test-quickstart.txt',
+ 'doc/test-statemanage.txt',
'doc/test.txt',
- 'doc/why_py.txt',
'doc/xml.txt',
'env.cmd',
'execnet/NOTES',
More information about the pytest-commit
mailing list