deploy: cb756ea

Author: Cito

.buildinfo

@@ -0,0 +1,4 @@
+# Sphinx build info version 1
+# This file records the configuration used when building these files. When it is not found, a full rebuild will be done.
+config: 8e7d921e2efd941987123d2978238cfc
+tags: 645f666f9bcd5a90fca523b33c5a78b7

.nojekyll

@@ -0,0 +1,40 @@
+.. _list-of-changes:
+
+List of Changes
+===============
+
+What's new in Webware for Python 3.0
+------------------------------------
+
+This is the full list of changes in Webware for Python 3 (first version 3.0.0) compared with Webware for Python 2 (last version 1.2.3):
+
+* Webware for Python 3.0 now requires Python 3.6 or newer, and makes internal use of newer Python features where applicable. Webware applications must now be migrated to or written for Python 3.
+* The "Application" instance is now callable and usable as a WSGI application.
+* The application server ("AppServer" class and subclasses including the "ThreadedAppServer") and the various adapters and start scripts and other related scripts for the application server are not supported anymore. Instead, Webware applications are now supposed to be served as WSGI applications using a WSGI server such as waitress, which is now used as the development server.
+* The "ASSStreamOut" class has been replaced by a "WSGIStreamOut" class. The "Message" class has been removed, since it was not really used for anything, simplifying the class hierarchy a bit.
+* The Application now has a development flag that can be checked to modify the application and its configuration depending on whether it is running in development or production mode.
+* The custom "install" script has been replaced by a standard "setup" script, Webware for Python 3 is now distributed as a normal Python package that can be installed in the usual way. The "ReleaseHelper" and "setversion" scripts are not used anymore.
+* The "MakeAppWorkDir" script has been moved to a new "Scripts" directory, which now also contains a "WSGIScript" and a "WaitressServer" script which serve as replacements for the old "AppServer" and "Launch" start scripts. These scripts can now be started as subcommands of a new webware console script, which serves as a new common Webware CLI.
+* Instead of the "AutoReloadingAppServer", you can use the "reload" option of the WaitressServer script which uses hupper to monitor the application files and reload the waitress server if necessary. The "ImportSpy" has been removed.
+* The classes of the core "WebKit" component are now available at the root level of Webware for Python 3, and the WebKit component ceased to exist as a separate plug-in.
+* Some built-in plug-ins are not supported anymore: "CGIWrapper", "ComKit" and "KidKit".
+* "MiddleKit" is not a built-in plug-in anymore, but is provided as a separate project on GitHub now (WebwareForPython/w4py3-middlekit).
+* Webware now uses entry points for discovering plug-ins instead of the old plug-in system, and the plug-in API has slightly changed. Existing plug-ins must be adapted to Python 3 and the new plug-in API.
+* The documentation has been moved to a separate directory and is built using Sphinx, instead providing a "Docs" context for Webware and every plug-in, and using custom documentation builders in the install script. The existing content has been reformatted for Sphinx, adapted and supplemented.
+* The various examples have been slightly improved and updated. Demo servlets showing the use of Dominate and Yattag for creating HTML in a Pythonic way have been added.
+* The side bar page layout now uses divs instead of tables.
+* The test suite has been expanded and fully automated using the unit testing framework in the Python standard library. We also use tox to automate various checks and running the test suite with different Python versions.
+* In particular, end-to-end tests using Twill have been replaced by more efficient unit tests using WebTest.
+* Internal assert statements have been removed or replaced with checks raising real errors.
+* The style guide has been slightly revised. We now rely on flake8 and pylint instead of using the custom "checksrc" script.
+
+See also the list of `releases`_ on GitHub for all changes in newer releases of Webware for Python 3 since the first alpha release 3.0.0a0.
+
+.. _releases: https://github.com/WebwareForPython/w4py3/releases
+
+What's new in Webware for Python 3.1
+------------------------------------
+
+Webware for Python 3.1 is a minor update making the following changes:
+
+* Webware for Python 3.1 now requires Python 3.10 and supports versions up to Python 3.14.

_sources/appdev.rst.txt

@@ -0,0 +1,28 @@
+.. _copyright:
+
+Copyright and License
+=====================
+
+The Gist
+--------
+
+Webware for Python is open source, but there is no requirement that products developed with or derivative to Webware become open source.
+
+Webware for Python is copyrighted, but you can freely use and copy it as long as you don't change or remove this copyright notice. The license is a clone of the MIT license.
+
+There is no warranty of any kind. Use at your own risk.
+
+Read this entire document for complete, legal details.
+
+Copyright
+---------
+
+Copyright © 1999 Chuck Esterbrook (Webware for Python)
+
+Copyright © 2019 Christoph Zwerschke (Webware for Python 3)
+
+Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.