This list is closed, nobody may subscribe to it.
2000 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(149) |
Jun
(174) |
Jul
(41) |
Aug
(118) |
Sep
(72) |
Oct
(111) |
Nov
(69) |
Dec
(147) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2001 |
Jan
(242) |
Feb
(276) |
Mar
(363) |
Apr
(704) |
May
(183) |
Jun
(209) |
Jul
(173) |
Aug
(230) |
Sep
(80) |
Oct
(306) |
Nov
(338) |
Dec
(291) |
2002 |
Jan
(273) |
Feb
(294) |
Mar
(303) |
Apr
(463) |
May
(319) |
Jun
(182) |
Jul
(160) |
Aug
(140) |
Sep
(192) |
Oct
(302) |
Nov
(238) |
Dec
(176) |
2003 |
Jan
(179) |
Feb
(222) |
Mar
(256) |
Apr
(167) |
May
(139) |
Jun
(145) |
Jul
(113) |
Aug
(259) |
Sep
(146) |
Oct
(124) |
Nov
(143) |
Dec
(66) |
2004 |
Jan
(58) |
Feb
(128) |
Mar
(193) |
Apr
(228) |
May
(111) |
Jun
(107) |
Jul
(93) |
Aug
(78) |
Sep
(48) |
Oct
(99) |
Nov
(104) |
Dec
(119) |
2005 |
Jan
(115) |
Feb
(124) |
Mar
(86) |
Apr
(41) |
May
(52) |
Jun
(21) |
Jul
(32) |
Aug
(14) |
Sep
(52) |
Oct
(30) |
Nov
(19) |
Dec
(19) |
2006 |
Jan
(43) |
Feb
(35) |
Mar
(68) |
Apr
(21) |
May
(38) |
Jun
(46) |
Jul
(19) |
Aug
(38) |
Sep
(58) |
Oct
(15) |
Nov
(12) |
Dec
(30) |
2007 |
Jan
(49) |
Feb
(23) |
Mar
(29) |
Apr
(19) |
May
(33) |
Jun
(4) |
Jul
(10) |
Aug
(26) |
Sep
(2) |
Oct
(9) |
Nov
(1) |
Dec
(21) |
2008 |
Jan
(15) |
Feb
(3) |
Mar
(10) |
Apr
(8) |
May
(4) |
Jun
(2) |
Jul
(2) |
Aug
|
Sep
|
Oct
(2) |
Nov
(13) |
Dec
|
2009 |
Jan
(11) |
Feb
(4) |
Mar
|
Apr
(6) |
May
|
Jun
(16) |
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(9) |
2010 |
Jan
(6) |
Feb
(4) |
Mar
(2) |
Apr
(12) |
May
(20) |
Jun
(9) |
Jul
(7) |
Aug
|
Sep
(1) |
Oct
(5) |
Nov
|
Dec
(4) |
2011 |
Jan
|
Feb
|
Mar
(10) |
Apr
|
May
|
Jun
|
Jul
(9) |
Aug
(2) |
Sep
|
Oct
|
Nov
|
Dec
|
2012 |
Jan
(2) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(6) |
Oct
(3) |
Nov
(8) |
Dec
(11) |
2013 |
Jan
(1) |
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2015 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(6) |
Dec
|
2016 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(3) |
Sep
|
Oct
|
Nov
(2) |
Dec
|
2017 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2019 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(1) |
Sep
|
Oct
|
Nov
(3) |
Dec
|
2020 |
Jan
(2) |
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(2) |
Nov
|
Dec
|
2021 |
Jan
(1) |
Feb
|
Mar
|
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
|
2022 |
Jan
|
Feb
|
Mar
(2) |
Apr
|
May
(2) |
Jun
|
Jul
(2) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Christoph Z. <ci...@on...> - 2022-07-16 19:47:25
|
Dear Webware for Python user, since the Webware for Python project is now hosted on GitHub, and we want to streamline our communication channels, the "webware-discuss" mailing list will be closed. If you want to report a bug or suggest a new feature, please open a GitHub issue for that. You can find our GitHub pages here: - https://github.com/WebwareForPython/w4py (Webware for Python 2) - https://github.com/WebwareForPython/w4py3 (Webware for Python 3) The mailing list archive will still be accessible here: https://sourceforge.net/p/webware/mailman/webware-discuss/ Unfortunately, SourceForge does not allow us to automatically unsubscribe you, but you can do it yourself here: https://sourceforge.net/projects/webware/lists/webware-discuss/unsubscribe All the best and see you on GitHub, Christoph |
From: Christoph Z. <ci...@on...> - 2022-07-16 17:25:49
|
Webware for Python 3.0.6 has been released today. GitHub: https://github.com/WebwareForPython/w4py3 PyPI: https://pypi.org/project/Webware-for-Python/ Documentation: https://webwareforpython.github.io/w4py3/ List of changes in version 3: https://webwareforpython.github.io/w4py3/changes.html Changes in this patch release: https://github.com/WebwareForPython/w4py3/releases/tag/3.0.6 -- Christoph |
From: <ci...@on...> - 2022-05-21 20:47:41
|
> Now, I /suspect/ the reason that this hack above to was done because, > given the way this script is “invoked” (via exec), if you didn’t do > this, when you tried to exec the WSGIScript.py content, you’d get: > > NameError: name '__file__' is not defined > > but then why have all that logic in the WSGIScript.py determining > workDir in the first place? Is the WSGIScript.py file used in some > other context?> > And what was the point of adding –wsgi-script as an argument to > WaitressServer.py if it didn’t allow you to specify app location other > than the default? Hi Will, yes, the WSGIScript can be used in different contexts. Keep in mind that Webware can used with any WSGI server. Waitress is just the default development server, which can also be used for production if you do not need very high performance. For instance, with Apache mod_wsgi you could set the path of the WSGI script in the Apache configuration with WSGIScriptAlias. The work dir (project directory) would then be either set to the "workDir" path given in the WSGI script or to the directory two levels higher if no such path is specified, using the logic you mentioned. The WaitressServer script is used for the command line interface (the "webware serve" command). If you use this command, the work dir is always the directory that you run the command in. It is mainly intended to be used during development. The --wsgi-path option can be used to specify a different WSGI file, if you do not want to use the default path (Scripts/WSGIScript.py) inside the working directory. If you want to run the script in the standard location, just cd to your working directory and call WaitressServer or webware serve there. Hope that helps. -- Christoph |
From: Will S. <wsadkin@ParlanceCorp.com> - 2022-05-16 00:42:16
|
To whom it may concern, We are finally porting our old webware application for Windows to w4py3, and I ran into a bit of ugliness that I wanted to report. As a test, I had made the HelloWorld app in a subfolder to our main app, and verified my w4py3 install. I then wanted to just run it initially from the WindowsService wrapper I wrote around webware's WaitressServer.py script as a first step before tackling the port of the rest of our application. Now, webware's default template WSGIScript.py file has the logic: workDir = None if workDir is None: workDir = os.path.dirname(os.path.dirname(__file__)) if workDir: os.chdir(workDir) if '.' in libDirs: sys.path.insert(0, workDir) And the WaitressServer.py, among its many nifty options, has a -wsgi-script argument, so I provided the HelloWorld/Scripts/WSGIScript.py as the -wsgi-script argument to the WaitressServer main() function, expecting this to just work as written above. But the workDir did not change to the subfolder, and I spent hours trying to figure out why. What I finally discovered was the cause was the following unexpected code modification in WaitressServer.py: # do not change working directory in the script script = script.replace('workDir =', "workDir = '' #") scriptVars = {} exec(script, scriptVars) Now, I suspect the reason that this hack above to was done because, given the way this script is "invoked" (via exec), if you didn't do this, when you tried to exec the WSGIScript.py content, you'd get: NameError: name '__file__' is not defined but then why have all that logic in the WSGIScript.py determining workDir in the first place? Is the WSGIScript.py file used in some other context? And what was the point of adding -wsgi-script as an argument to WaitressServer.py if it didn't allow you to specify app location other than the default? For what it's worth, I've hacked around this temporarily, by replacing the above line in WaitressServer.py with slightly different code modification logic, i.e.: Import os [...] fullpath = "r'" + os.path.abspath(args.wsgi_script) + "'" script = script.replace('__file__', fullpath) But I'm not convinced this is the best solution, because I'm not sure what the intent was for the -wsgi-script argument if not to allow you to specify where the app you want to serve lives... Is there a better way to do that? Regards, /Will Sadkin |
From: <ci...@on...> - 2022-03-10 21:59:33
|
Hi John, I can only give you some pointers: It's probably best you look at the source code of XMLRPCServlet and its base class RPCServlet - it's actually very small and easy to understand. Also, have a look at the XMLRPCExample for how to use this, and the Python documentation for xmlrpc.client here: https://docs.python.org/3/library/xmlrpc.client.html Christoph |
From: John B. <joh...@mo...> - 2022-03-10 00:09:10
|
Hi All, Newbie question that I can't seem to find an answer to. On a return from a published XMLRpcServlet method, I need to returns 3 values. I was hoping to return the values in the following manner: pkg = "<response>\n" pkg += "<sn>" + row[14] + "</sn>\n" pkg += "<cl_id>" + str(row[8]) + "</cl_id>\n" pkg += "<reg_expiry>" + str(row[2]) + "</reg_expiry>\n" pkg += "</response>\n" return pkg The result in the client is the following: <params> <param> <value><string><response> <sn>TESTPR 12345 67890 CCCCC</sn> <cl_id>1858</cl_id> <reg_expiry>2023-06-04</reg_expiry> </response> </string></value> </param> </params> I can make this work, but was really hoping the result would be like: <params> <param> <value><string><response> <sn>TESTPR 12345 67890 CCCCC</sn> <cl_id>1858</cl_id> <reg_expiry>2023-06-04</reg_expiry> </response> </string></value> </param> </params> If I do the following for the return value: trans = self.transaction() self.sendOK( 'text/xml', pkg, trans ) return "" Where "pkg" is the xml structure: <?xml version="1.0" ?> <response> <sn>TESTPR 12345 67890 CCCCC</sn> <cl_id>1858</cl_id> <reg_expiry>2023-06-04</reg_expiry> </response> The client receives the following: <?xml version="1.0" \?> <response> <sn>TESTPR 12345 67890 CCCCC</sn> <cl_id>1858</cl_id> <reg_expiry>2023-06-04</regexpiry> </response> <?xml version='1.0'?> <methodResponse> <params> <param> <value><nil/></value></param> </params> </methodResponse> Notice the package I want to return is there, but so is the default return structure from the XMLRpcServlet class. This is useful if I just ignore the second XML segment which is easy enough to do (note: The content length of the header does not match either the total return package length, or, the length of the default return structure or the one I added). I was hoping that the sendOK with the content would replace the default return value, but it still puts the default in there. I was looking for a method(s) to manage the return parameters/values. Is there anything like that? Is there a definition for changes to the input parameters to the method to be returned to the client? Is that where I should be looking? Is there another approach I should be using? John Boehme Software Engineer Description: Mophily_Footer_50 |
From: Christoph Z. <ci...@on...> - 2021-11-26 23:17:48
|
Webware for Python 3.0.4 has been released today. GitHub: https://github.com/WebwareForPython/w4py3 PyPI: https://pypi.org/project/Webware-for-Python/ Documentation: https://webwareforpython.github.io/w4py3/ List of changes in version 3: https://webwareforpython.github.io/w4py3/changes.html Changes in this patch release: https://github.com/WebwareForPython/w4py3/releases/tag/3.0.4 There is also a new version 3.0.0 of DBUtils: https://webwareforpython.github.io/DBUtils/ Stay healthy. Stay happy. -- Christoph |
From: Christoph Z. <ci...@on...> - 2021-04-30 14:54:46
|
Webware for Python 3.0.3 has been released today. GitHub: https://github.com/WebwareForPython/w4py3 PyPI: https://pypi.org/project/Webware-for-Python/ Documentation: https://webwareforpython.github.io/w4py3/ List of changes in version 3: https://webwareforpython.github.io/w4py3/changes.html Changes in this patch release: https://github.com/WebwareForPython/w4py3/releases/tag/3.0.3 Stay healthy. Stay happy. -- Christoph |
From: Christoph Z. <ci...@on...> - 2021-01-21 17:49:05
|
Webware for Python 3.0.2 has been released today. GitHub: https://github.com/WebwareForPython/w4py3 PyPI: https://pypi.org/project/Webware-for-Python/ Documentation: https://webwareforpython.github.io/w4py3/ List of changes in version 3: https://webwareforpython.github.io/w4py3/changes.html Changes in this patch release: https://github.com/WebwareForPython/w4py3/releases/tag/3.0.2 Stay healthy. Stay happy. -- Christoph |
From: Christoph Z. <ci...@on...> - 2020-10-17 20:21:34
|
Correction: The announcement had the wrong subject - this is the final version of Webware for Python 3.0.0, not an alpha version. |
From: Christoph Z. <ci...@on...> - 2020-10-17 20:18:26
|
Hi all, I'm pleased to announce at least one good news in these hard times: After a nearly year-long alpha and beta phase, Webware for Python 3.0.0 has been released today. Here are all the important links: GitHub: https://github.com/WebwareForPython/w4py3 PyPI: https://pypi.org/project/Webware-for-Python/ Documentation: https://webwareforpython.github.io/w4py3/ List of changes: https://webwareforpython.github.io/w4py3/changes.html Mirgration guide: https://webwareforpython.github.io/w4py3/migrate.html The main improvements and changes in Webware for Python 3 are: - Python 3.6 or newer instead of Python 2 - Standard packaging and installation - Entry points for Webware plug-ins - WSGI instead of app server and adapters - Sphinx/ReadTheDocs for documentation - GitHub Actions to run improved test suite The WebKit plug-in has been promoted to the top level and does not exist anymore as a separate plug-in. PSP is still supported. MiddleKit has become an external plug-in now, available at: https://github.com/WebwareForPython/w4py3-middlekit Let me know if there are any pain points, bugs or other problems. You can use GitHub issues, pull requests or the webware mailing list for feedback and sending bug reports or improvements. -- Christoph |
From: Christoph Z. <ci...@on...> - 2020-05-14 16:41:28
|
Hi all, the final ever Python 2 update has been released in April, which also marks the end of the era of Webware for Python 2. But don't despair - Webware for Python 3 has been available as an alpha release since last year, and as a beta release since today. The home page for Webware for Python 3 has been moved here: https://github.com/WebwareForPython/w4py3/ Documentation is available here: https://webwareforpython.github.io/w4py3/ The documentation also lists the changes and explains how to migrate legacy Webware applications. Main improvements and changes: - Use Python 3.6 or newer instead of Python 2 - Use standard packaging and installation - Use entry points for Webware plug-ins - Use WSGI instead of app server and adapters - Use Sphinx/ReadTheDocs for documentation - Use GitHub Actions to run improved test suite The WebKit plug-in has been promoted to the top level and does not exist any more as a separate plug-in. PSP is still built-in. MiddleKit has been removed as a built-in plug-in, but can be installed as an external plug-in available from here: https://github.com/WebwareForPython/w4py3-middlekit Please let me know how you like the beta version, if there are any pain points, bugs or other problems, since I want to release a final version soon. New features and more modernizations will be released in the next minor version. You can use GitHub issues, pull requests or the web...@li... mailing list for feedback and sending bug reports or improvements. Stay healthy and happy! -- Christoph |
From: Mark P. <mar...@mo...> - 2020-01-10 23:24:41
|
Great news! Thanks, Christoph. > On Jan 9, 2020, at 3:25 PM, Christoph Zwerschke <ci...@on...> wrote: > > Happy new year to you all, > > and I am also sharing some happy news: > > > A new version 1.2.3 of Webware for Python 2 has been released. > > Homepage: https://cito.github.io/w4py/ > Project page: https://github.com/Cito/w4py/ > Download from SourceForge: > https://sourceforge.net/projects/webware/files/latest/download > Download from PyPI: > https://pypi.org/project/Webware-for-Python/1.2.3/#files > Release Notes: > http://webware.sourceforge.net/Webware/Docs/RelNotes-1.2.3.html > > > Also, a new apha version 3.0.0a1 of Webware for Python 3 > has been released. > > Homepage: https://cito.github.io/w4py3/ > Project page: https://github.com/Cito/w4py3/ > Download from PyPI: > https://pypi.org/project/Webware-for-Python/3.0.0a1/#files > Latest commits: > https://github.com/Cito/w4py3/commits/master > > > We now also have an alpha version of the MiddleKit Plugin > for Webware for Python 3, which has been made available > as a separate project (not built-in to Webware any more) > https://github.com/PeaceWorksTechnologySolutions/w4py3-middlekit > > > Thanks to Nico Latzer and Jason Hildenbrand for porting MiddleKit > and volunteering to act as its new maintainers. > > Also thanks to everyone who provided feedback and pull requests for the new alpha version of Webware for Python 3. > > Please continue to provide feedback, so that we can move forward and publish a beta version soon. > > > -- Christoph Zwerschke > > > _______________________________________________ > Webware-discuss mailing list > Web...@li... > https://lists.sourceforge.net/lists/listinfo/webware-discuss |
From: Christoph Z. <ci...@on...> - 2020-01-09 23:38:57
|
Happy new year to you all, and I am also sharing some happy news: A new version 1.2.3 of Webware for Python 2 has been released. Homepage: https://cito.github.io/w4py/ Project page: https://github.com/Cito/w4py/ Download from SourceForge: https://sourceforge.net/projects/webware/files/latest/download Download from PyPI: https://pypi.org/project/Webware-for-Python/1.2.3/#files Release Notes: http://webware.sourceforge.net/Webware/Docs/RelNotes-1.2.3.html Also, a new apha version 3.0.0a1 of Webware for Python 3 has been released. Homepage: https://cito.github.io/w4py3/ Project page: https://github.com/Cito/w4py3/ Download from PyPI: https://pypi.org/project/Webware-for-Python/3.0.0a1/#files Latest commits: https://github.com/Cito/w4py3/commits/master We now also have an alpha version of the MiddleKit Plugin for Webware for Python 3, which has been made available as a separate project (not built-in to Webware any more) https://github.com/PeaceWorksTechnologySolutions/w4py3-middlekit Thanks to Nico Latzer and Jason Hildenbrand for porting MiddleKit and volunteering to act as its new maintainers. Also thanks to everyone who provided feedback and pull requests for the new alpha version of Webware for Python 3. Please continue to provide feedback, so that we can move forward and publish a beta version soon. -- Christoph Zwerschke |
From: Christoph Z. <ci...@on...> - 2019-11-17 22:38:01
|
Am 17.11.2019 um 22:23 schrieb Mark Phillips: > I look forward to reviewing the new code base and documents. > > BTW, the paragraph that begins "The most incisive change in Webware for Python 3…” is repeated in the text. The two are run together so it appears to be one paragraph. Thank you for the feedback. I have removed the duplicate paragraph already. You can probably find more issues and typos in the docs - let me know. Next time I set the announcement list as CC only, so that replys will not bounce. -- Christoph |
From: Mark P. <mar...@mo...> - 2019-11-17 21:50:42
|
This is very cool, Christoph. I look forward to reviewing the new code base and documents. BTW, the paragraph that begins "The most incisive change in Webware for Python 3…” is repeated in the text. The two are run together so it appears to be one paragraph. Cheers, - Mark Phillips > On Nov 17, 2019, at 12:23 PM, Christoph Zwerschke <ci...@on...> wrote: > > Hi all, > > sorry for the long radio silence. > > As the end of life for Python 2.7 is coming, I have finally taken some time to create a first public alpha release of the long promised new version of Webware for Python that targets Python 3. > > The home page for Webware for Python 3 is here: > https://github.com/Cito/w4py3 > > Documentation is available here: > https://webware-for-python-3.readthedocs.io/ > > The documentation also lists the changes and explains how to migrate existing Webware apps for legacy Python. > > Main improvements and changes: > - Use Python 3.6 or newer instead of Python 2 > - Use standard packaging and installation > - Use entry points for Webware plug-ins > - Use WSGI instead of app server and adapters > - Use Sphinx/ReadTheDocs for documentation > - Use GitHub Actions to run improved test suite > > The WebKit plug-in has been promoted to the top level and does not exist any more as a separate plug-in. PSP is still supported. > > MiddleKit has been removed as a built-in plug-in and must be installed as a yet-to-be-created external plug-in now. If anybody has interest in creating such a Webware for Python 3 compatible MiddleKit and wants to become a maintainer, please let me know. I will gladly help, but cannot act as a maintainer myself any longer. > > Please let me know how you like the new version, if there are any pain points, bugs or other problems. You can use GitHub issues, pull requests or the web...@li... mailing list for feedback and sending bug reports or improvements. > > I will publish more alpha and beta releases in the next weeks depending on how much feedback and bug reports I will get, and hopefully we can then have the final 3.0 release by 2020. > > -- Christoph > > > > > > > > > > > > > _______________________________________________ > Webware-discuss mailing list > Web...@li... > https://lists.sourceforge.net/lists/listinfo/webware-discuss |
From: Christoph Z. <ci...@on...> - 2019-11-17 20:23:59
|
Hi all, sorry for the long radio silence. As the end of life for Python 2.7 is coming, I have finally taken some time to create a first public alpha release of the long promised new version of Webware for Python that targets Python 3. The home page for Webware for Python 3 is here: https://github.com/Cito/w4py3 Documentation is available here: https://webware-for-python-3.readthedocs.io/ The documentation also lists the changes and explains how to migrate existing Webware apps for legacy Python. Main improvements and changes: - Use Python 3.6 or newer instead of Python 2 - Use standard packaging and installation - Use entry points for Webware plug-ins - Use WSGI instead of app server and adapters - Use Sphinx/ReadTheDocs for documentation - Use GitHub Actions to run improved test suite The WebKit plug-in has been promoted to the top level and does not exist any more as a separate plug-in. PSP is still supported. MiddleKit has been removed as a built-in plug-in and must be installed as a yet-to-be-created external plug-in now. If anybody has interest in creating such a Webware for Python 3 compatible MiddleKit and wants to become a maintainer, please let me know. I will gladly help, but cannot act as a maintainer myself any longer. Please let me know how you like the new version, if there are any pain points, bugs or other problems. You can use GitHub issues, pull requests or the web...@li... mailing list for feedback and sending bug reports or improvements. I will publish more alpha and beta releases in the next weeks depending on how much feedback and bug reports I will get, and hopefully we can then have the final 3.0 release by 2020. -- Christoph |
From: Christoph Z. <ci...@on...> - 2019-08-04 18:31:38
|
Hi all, Webware for Python 1.2.2 is available for download. This is a bugfix and maintenance release. Documentation and download links can be found here: https://cito.github.io/w4py/ Webware for Python 1.x is in maintenance mode now - no new features will be added and only critical bugs or security issues will be fixed. Note that Webware 1.2.x supports Python 2.6 and 2.7 only. I'm planning to create a modernized, but slimmed down version 2.x supporting Python 3 this year - an alpha version will be hopefully available soon. -- Christoph |
From: Christoph Z. <ci...@on...> - 2017-02-05 13:24:51
|
Hi all, new releases of DBUtils are available for download. DBUtils can be used as Webware for Python plugin or with other multi-threaded web environments for Python. Version 1.1.1 supports Python 2.3 to 2.7 Version 1.2 supports Python 2.6, 2.7 and 3.x Documentation and download links can be found on the new homepage: https://cito.github.io/DBUtils/ Let me know if there are any issues with the new releases. -- Christoph |
From: Christoph Z. <ci...@on...> - 2016-11-22 13:14:45
|
Hi all, just got a notice that the new Webware homepage wasn't found on the server. This seems to be some caching problem on GitHub where the homepage is hosted; other pages are affected as well. After re-pushing the branch for the homepage it now works again, hope this lasts. If not, have some patience until GitHub solves the issue. -- Christoph |
From: Christoph Z. <ci...@on...> - 2016-11-21 22:33:41
|
Hi all, a bugfix release of Webware for Python 1.2.1 is available for download. Note that Webware 1.2.x supports Python 2.6 and 2.7 only. For older Python versions, use Webware 1.1.3. Documentation and download links can be found on the new homepage: https://cito.github.io/w4py/ New Features: You can now specify attributes to be set on the root HTML element of the Page servlet. By default, the document language will be set to English using the lang Attribute. Bugfixes: Fixed a race condition in the SessionDynamicStore (thanks to Ben Parker). I'm still experimenting in the background with a more modern release of Webware for Python based on WSGI. A prototype already runs quite fast and can make full use of all the available kernels/cpus, which is not possible with the existing threaded application server that is restricted by the GIL. I have some other plans for the new release as well, particularly support for Python 3. -- Christoph |
From: Christoph Z. <ci...@on...> - 2016-08-16 13:25:54
|
Hi all, a new release of Webware for Python 1.2 is available for download. Note that contrary to 1.1.2 which was released last week, the new 1.2 release now requires Python 2.6 or 2.7. Otherwise the new release is still fully backward compatible. This version features a new Redis based session store. Documentation and download links can be found on the new homepage: https://cito.github.io/w4py/ Webware Release Notes: http://webware.sourceforge.net/Webware/Docs/RelNotes-1.2.html WebKit Release Notes: http://webware.sourceforge.net/Webware/WebKit/Docs/RelNotes-1.2.html I'm planning to continue the modernization efforts in September. This will also require to make some cuts and breaking changes. If you have ideas for future development and additions, or certain parts of Webware are of particular importance for you, please let me know. Happy Webwaring... -- Christoph |
From: Christoph Z. <ci...@on...> - 2016-08-12 22:02:06
|
Hi all, a new release of Webware for Python 1.1.2 is available for download. Documentation and download links can be found on the new homepage: https://cito.github.io/w4py/ This is a backward compatible bugfix release with all fixes and improvements that have accumulated until today. The 1.1.x versions are fully backward compatible, supporting Python 2.4 to 2.7. Next version will be 1.2 and support only Python 2.6 and 2.7. -- Christoph Zwerschke |
From: Christoph Z. <ci...@on...> - 2016-08-01 17:21:19
|
Some news from the Webware for Python project: As announced already last year, I have finally moved the Webware for Python project from the old private server provided by Tummy to GitHub. The homepage is now served by GitHub as well. * The new repository is at: https://github.com/Cito/w4py * The new homepage is at: https://cito.github.io/w4py/ Don’t worry, I will continue to maintain Webware for Python and create new releases with updated and more modern code and documentation. In fact, slimming down the project infrastructure and moving stuff to GitHub is the first step for me to make the project manageable again and restart development on a clean slate. The old repository with the full history and the old documentation has been preserved under https://github.com/Cito/w4py-olde-docs, the old Webware for Python Wiki has been frozen and archived under https://github.com/Cito/w4py-olde-wiki. I want to thank Tummy (https://www.tummy.com/) again for generously providing a server for the Webware project over all these years. -- Christoph |
From: Roger H. <cro...@ya...> - 2015-11-30 14:29:59
|
Agree, seems like many projects are moving to Github. And I add my thanks to you for maintaining the Webware project. On Saturday, November 28, 2015 1:14 PM, Chuck Esterbrook <chu...@gm...> wrote: Sounds good. -Chuck On Sat, Nov 28, 2015 at 11:09 AM, Steve Schwarz <st...@ag...> wrote: Hi Christoph,Sounds like a great idea. Thanks for maintaining this project! Best Regards, Steve Blogs: http://agilitynerd.com/ http://tech.agilitynerd.com/ Dog Agility Search: http://googility.com/ Dog Agility Courses: http://agilitycourses.com/ http://www.facebook.com/AgilityNerd On Sat, Nov 28, 2015 at 12:54 PM, Christoph Zwerschke <ci...@on...> wrote: Btw, is anyone against moving Webware to Github, consolidating all the infrastructure (we still have our own server with web site, Wiki, SVN, plus the SF page with mailing lists and discussion forums)? It makes no sense that we have 3 mailing list plus various discussion forums on SF. I also want to consolidate all of the docs and Wiki content, probably using Sphinx, and then make it available on Readthedocs. (Not immediately, but some time in winter, when I have time and it's cold outside.) -- Christoph ------------------------------------------------------------------------------ _______________________________________________ Webware-discuss mailing list Web...@li... https://lists.sourceforge.net/lists/listinfo/webware-discuss |