[stacklessexamples] r187 committed - Fix up the egg generation finally. MANIFEST appears to only be partia...
stackles...@googlecode.com
Author: richard.m.tew
Date: Mon Dec 19 01:31:21 2011
Log: Fix up the egg generation finally. MANIFEST appears to only be
partially used, and not for Python files in nested directories. You need
to specify all Python packages in setup.py by name, even if the MANIFEST
should include them. Otherwise the egg will be generated from whatever
other files you make when someone uses easy_install, and it won't include
the sub-packages when it does so (exactly like if you generated it
yourself).
http://code.google.com/p/stacklessexamples/source/detail?r=187
Modified:
/trunk/libraries/stacklesslib/MANIFEST.in
/trunk/libraries/stacklesslib/README.txt
/trunk/libraries/stacklesslib/setup.py
=======================================
--- /trunk/libraries/stacklesslib/MANIFEST.in Mon Dec 19 00:10:28 2011
+++ /trunk/libraries/stacklesslib/MANIFEST.in Mon Dec 19 01:31:21 2011
@@ -1,3 +1,2 @@
-recursive-include stacklesslib *
-include COPYING.txt
-include README.txt
+include *.txt
+recursive-include stacklesslib *.py
=======================================
--- /trunk/libraries/stacklesslib/README.txt Mon Dec 19 00:10:28 2011
+++ /trunk/libraries/stacklesslib/README.txt Mon Dec 19 01:31:21 2011
@@ -1,12 +1,37 @@
stacklesslib
============
-This is a simple framework that layers useful functionality around the
-Stackless scheduler. It's sole purpose is to implement the logic that
-an developer needs to implement themselves, to make best use of
-Stackless.
-
- * A sleep function, to allow a tasklet to sleep for a period of time.
- * Monkeypatching to make blocking IO block tasklets not threads.
-
-
+Stackless Python by itself only provides a basic set of functionality,
+allowing either cooperative or preemptive scheduling of microthreads
+within the same operating system thread. This framework provides the
+additional support that anyone developing an application using Stackless
+Python will end up eventually implementing.
+
+The most useful aspect is the monkey-patching support. Much of the
+code in the standard library does blocking operations, or perhaps
+is even written to make use of threads. If the monkey-patching is
+installed, then these blocking operations are converted to be
+"Stackless friendly". Threads will actually be tasklets. Operations
+that block the operating system thread (and therefore the Stackless
+scheduler) will be converted to simply block the tasklet that is
+standing in for the threads that would otherwise be used.
+
+Even if an application developer does not wish to make use of
+monkey-patching, they can still make use the framework provided
+so that they do not need to implement the standard supporting
+functionality themselves.
+
+Useful supporting functionality:
+
+ * Concurrency-related primitives corresponding to those that the
+ standard library threading module provides for real threads.
+ * Ability to put tasklets to sleep for a set amount of time.
+ * Ability to specify timeouts for blocking operations.
+
+Changes
+-------
+
+Version 1.0.3:
+
+ * All previous versions had broken eggs. This was because the manifest
was not
+ correctly configured to recursively include the source directory.
=======================================
--- /trunk/libraries/stacklesslib/setup.py Mon Dec 19 00:10:28 2011
+++ /trunk/libraries/stacklesslib/setup.py Mon Dec 19 01:31:21 2011
@@ -2,12 +2,12 @@
setup(
name = "stacklesslib",
- packages = ["stacklesslib"],
+ packages = ["stacklesslib", "stacklesslib.replacements"],
version = "1.0.3",
description = "Standard Stackless Python supporting functionality",
author = "Richard Tew",
author_email = "richar...@gmail.com",
- url = "http://code.google.com/p/sake/",
+ url = "http://pypi.python.org/pypi/stacklesslib",
keywords =
["microthreads", "coroutines", "stackless", "monkeypatching"],
classifiers = [
"Programming Language :: Python",