gmane.comp.python.web archive

417 archived articles, newest first (page 1 of 5). Latest articles →

Call for Papers. SCENE 2024: Paper Submission date extended
Mon, 4 Mar 2024 15:29:28 +0000
Mattia Occhipinti <[email protected]> • #5244
Call for Papers: 2nd International workshop on Safeguarding CybersEcurity iN hEalthcare (SCENE 2024), May 6-9, 2024
Mon, 5 Feb 2024 13:24:29 +0000
Mattia Occhipinti <[email protected]> • #5243
CfP:IEEE MetroXRAINE 2023 - Special Session on: "EXTENDED REALITY AS A GATEWAY TO THE METAVERSE: PRACTICES, THEORIES, TECHNOLOGIES AND APPLICATIONS"
Mon, 06 Mar 2023 10:57:44 +0100
Mattia Occhipinti <[email protected]> • #5242
CfP: ISSA track of the 16th IEEE SITIS 2022 conference. Submission deadline: August 19, 2022
Mon, 25 Jul 2022 11:35:04 +0200
Mattia Occhipinti <[email protected]> • #5241
why function throws an error?
Tue, 28 Jun 2022 10:57:59 +0300
נתי שטרן <[email protected]> • #5240
REMINDER CFP:ISSA: INTELLIGENT SYSTEMS, SERVICES AND APPLICATIONS 16th IEEE SITIS 2022 conference
Sun, 19 Jun 2022 18:29:23 +0200
Mattia Occhipinti <[email protected]> • #5239
CfP - CoopIS 2022: The 28th International Conference on Cooperative Information Systems - deadline extended
Tue, 24 May 2022 15:55:19 +0200
Mattia Occhipinti <[email protected]> • #5238
ERRATA CORRIGE: CfP 1ST ITALIAN CONFERENCE ON BIG DATA AND DATA SCIENCE (ITADATA 2022)
Fri, 15 Apr 2022 10:32:50 +0200
Mattia Occhipinti <[email protected]> • #5237
CFP: CoopIS 2022: The 28th International Conference on Cooperative Information Systems
Tue, 15 Mar 2022 16:24:25 +0100
Mattia Occhipinti <[email protected]> • #5236
Flask Blueprints and Shared Configuration Settings
Mon, 15 Jun 2020 14:45:39 +0000
"Doran, Harold C." <[email protected]> • #5235
TENTH INTERNATIONAL SYMPOSIUM ON DATA-DRIVEN PROCESS DISCOVERY AND ANALYSIS - SIMPDA 2020
Fri, 27 Mar 2020 11:41:13 +0100
Paolo Ceravolo <[email protected]> • #5234
Re: Research Topics for Grad School
Tue, 12 Nov 2019 07:13:14 +0100
Stéfane Fermigier <[email protected]> • #5233
Re: Research Topics for Grad School
Mon, 11 Nov 2019 18:08:27 -0500
Jack Bortone <tkadm30-zJpx2rpV7r/[email protected]> • #5232
Re: Research Topics for Grad School
Mon, 11 Nov 2019 17:13:20 +0100
Amirouche Boubekki <[email protected]> • #5231
Re: Research Topics for Grad School
Mon, 11 Nov 2019 13:20:16 +0100
Amirouche Boubekki <[email protected]> • #5230
Re: Research Topics for Grad School
Mon, 11 Nov 2019 09:44:57 +0100
Stéfane Fermigier <[email protected]> • #5229
Re: Research Topics for Grad School
Mon, 11 Nov 2019 02:01:27 -0500
Jack Bortone <tkadm30-zJpx2rpV7r/[email protected]> • #5228
Re: Research Topics for Grad School
Mon, 11 Nov 2019 14:36:56 +1100
Mike Dewhirst <miked-bJ2UlT/JPi00n/[email protected]> • #5227
Research Topics for Grad School
Sun, 10 Nov 2019 19:14:44 -0800
yun bao <[email protected]> • #5226
Re: Wsgiref x Form ?
Sat, 9 Nov 2019 02:02:45 -0500
Jack Bortone <[email protected]> • #5225
Wsgiref x Form ?
Fri, 8 Nov 2019 17:29:54 -0300
João Aguiar <[email protected]> • #5224
(no subject)
Wed, 27 Dec 2017 23:06:49 -0900
gedope1981 <[email protected]> • #5223
New django-hotsauce development group
Mon, 16 Oct 2017 05:56:39 -0400
Etienne Robillard <tkadm30-zJpx2rpV7r/[email protected]> • #5222
Django-hotsauce 0.7.8 release
Fri, 11 Aug 2017 09:53:55 -0400
Etienne Robillard <tkadm30-zJpx2rpV7r/[email protected]> • #5221
Re: How to make REMOTE_USER variable private across WSGI middlewares?
Fri, 11 Aug 2017 06:43:11 -0400
Etienne Robillard <tkadm30-zJpx2rpV7r/[email protected]> • #5220
Re: How to make REMOTE_USER variable private across WSGI middlewares?
Thu, 10 Aug 2017 06:25:00 -0400
Etienne Robillard <tkadm30-zJpx2rpV7r/[email protected]> • #5219
Re: How to make REMOTE_USER variable private across WSGI middlewares?
Wed, 12 Oct 2016 05:42:15 -0400
Etienne Robillard <tkadm30-zJpx2rpV7r/[email protected]> • #5218
Re: How to make REMOTE_USER variable private across WSGI middlewares?
Tue, 11 Oct 2016 19:44:56 -0400
Randy Syring <randy-+PLZm/s06Zpa7S/[email protected]> • #5217
Re: How to make REMOTE_USER variable private across WSGI middlewares?
Tue, 11 Oct 2016 18:47:32 -0400
Etienne Robillard <tkadm30-zJpx2rpV7r/[email protected]> • #5216
How to make REMOTE_USER variable private across WSGI middlewares?
Mon, 10 Oct 2016 10:30:27 -0400
Etienne Robillard <tkadm30-zJpx2rpV7r/[email protected]> • #5215
Re: ANN: General availability of the WebCore WSGI nanoframework v2.0.
Thu, 21 Apr 2016 18:52:00 +0300
Alex Grönholm <alex.gronholm-S2Gd0AnZGk/[email protected]> • #5214
Re: ANN: General availability of the WebCore WSGI nanoframework v2.0.
Tue, 19 Apr 2016 09:00:35 -0400
Alice Bevan–McGregor <alice-h+KYGxXtFYrqlBn2x/[email protected]> • #5213
Re: ANN: General availability of the WebCore WSGI nanoframework v2.0.
Tue, 19 Apr 2016 07:56:26 -0500
Ian Cordasco <[email protected]> • #5212
Re: ANN: General availability of the WebCore WSGI nanoframework v2.0.
Tue, 19 Apr 2016 08:37:44 -0400
Alice Bevan–McGregor <alice-h+KYGxXtFYrqlBn2x/[email protected]> • #5211
Re: ANN: General availability of the WebCore WSGI nanoframework v2.0.
Tue, 19 Apr 2016 10:03:39 +0200
Marcel Hellkamp <marc-W1HR/[email protected]> • #5210
ANN: General availability of the WebCore WSGI nanoframework v2.0.
Mon, 18 Apr 2016 18:17:02 -0400
Alice Bevan–McGregor <alice-h+KYGxXtFYrqlBn2x/[email protected]> • #5209
Re: Any practical reason type(environ) must be dict (not subclass)?
Fri, 25 Mar 2016 17:23:35 +0000
Cory Benfield <[email protected]> • #5208
Re: Any practical reason type(environ) must be dict (not subclass)?
Fri, 25 Mar 2016 10:04:24 -0500
Jason Madden <[email protected]> • #5207
Re: Any practical reason type(environ) must be dict (not subclass)?
Fri, 25 Mar 2016 10:01:51 +0000
Cory Benfield <[email protected]> • #5206
Re: Any practical reason type(environ) must be dict (not subclass)?
Thu, 24 Mar 2016 11:29:05 -0500
Jason Madden <[email protected]> • #5205
Re: Any practical reason type(environ) must be dict (not subclass)?
Thu, 24 Mar 2016 16:09:20 +0000
Alan Kennedy <[email protected]> • #5204
Any practical reason type(environ) must be dict (not subclass)?
Thu, 24 Mar 2016 10:18:04 -0500
Jason Madden <[email protected]> • #5203
Re: Inviting feedback on my proposed "ASGI" spec
Fri, 11 Mar 2016 10:05:07 -0800
Andrew Godwin <[email protected]> • #5202
Re: Inviting feedback on my proposed "ASGI" spec
Fri, 11 Mar 2016 13:03:35 -0500
Collin Anderson <[email protected]> • #5201
Re: Inviting feedback on my proposed "ASGI" spec
Fri, 11 Mar 2016 09:59:59 -0800
Andrew Godwin <[email protected]> • #5200
Re: Inviting feedback on my proposed "ASGI" spec
Fri, 11 Mar 2016 09:56:22 -0800
Andrew Godwin <[email protected]> • #5199
Re: Inviting feedback on my proposed "ASGI" spec
Fri, 11 Mar 2016 10:45:05 -0500
Collin Anderson <[email protected]> • #5198
Re: Inviting feedback on my proposed "ASGI" spec
Fri, 11 Mar 2016 10:28:36 +0000
Cory Benfield <[email protected]> • #5197
Re: Inviting feedback on my proposed "ASGI" spec
Fri, 11 Mar 2016 10:28:35 +0000
Cory Benfield <[email protected]> • #5196
Re: Inviting feedback on my proposed "ASGI" spec
Thu, 10 Mar 2016 15:56:00 -0800
Andrew Godwin <[email protected]> • #5195
Re: Inviting feedback on my proposed "ASGI" spec
Fri, 11 Mar 2016 11:07:48 +1300
Robert Collins <[email protected]> • #5194
Re: Inviting feedback on my proposed "ASGI" spec
Thu, 10 Mar 2016 13:34:29 -0800
Andrew Godwin <[email protected]> • #5193
Re: Inviting feedback on my proposed "ASGI" spec
Fri, 11 Mar 2016 10:30:01 +1300
Robert Collins <[email protected]> • #5192
Re: Inviting feedback on my proposed "ASGI" spec
Fri, 11 Mar 2016 10:27:19 +1300
Robert Collins <[email protected]> • #5191
Re: Inviting feedback on my proposed "ASGI" spec
Thu, 10 Mar 2016 11:32:46 -0800
Andrew Godwin <[email protected]> • #5190
Re: Inviting feedback on my proposed "ASGI" spec
Thu, 10 Mar 2016 18:57:14 +0000 (GMT)
[email protected] • #5189
Re: Inviting feedback on my proposed "ASGI" spec
Thu, 10 Mar 2016 10:36:54 -0800
Andrew Godwin <[email protected]> • #5188
Re: Inviting feedback on my proposed "ASGI" spec
Thu, 10 Mar 2016 16:46:39 +0200
Ionel Maries Cristian <[email protected]> • #5187
Re: Inviting feedback on my proposed "ASGI" spec
Thu, 10 Mar 2016 09:59:15 +0000
Cory Benfield <[email protected]> • #5186
Inviting feedback on my proposed "ASGI" spec
Wed, 9 Mar 2016 16:34:40 -0800
Andrew Godwin <[email protected]> • #5185
Re: Changes for WSGI 1.1
Thu, 18 Feb 2016 08:05:41 +0000
Cory Benfield <[email protected]> • #5184
Re: Changes for WSGI 1.1
Wed, 17 Feb 2016 13:55:34 +0100
Dirkjan Ochtman <[email protected]> • #5183
Changes for WSGI 1.1
Wed, 17 Feb 2016 11:51:18 +0000
Cory Benfield <[email protected]> • #5182
Re: Fwd: Collating follow-up on the future of WSGI
Mon, 1 Feb 2016 20:44:27 -0500
PJ Eby <pje-Wh6+Hckhi6HFNGf7iClzIwC/[email protected]> • #5181
Re: Fwd: Collating follow-up on the future of WSGI
Sun, 31 Jan 2016 17:57:11 -0800
Andrew Godwin <[email protected]> • #5180
Re: Fwd: Collating follow-up on the future of WSGI
Sun, 31 Jan 2016 19:42:20 -0500
PJ Eby <pje-Wh6+Hckhi6HFNGf7iClzIwC/[email protected]> • #5179
Re: Collating follow-up on the future of WSGI
Thu, 21 Jan 2016 08:10:09 +0000
Cory Benfield <[email protected]> • #5178
Re: Collating follow-up on the future of WSGI
Thu, 21 Jan 2016 06:39:51 +0000
Benoit Chesneau <[email protected]> • #5177
Re: Collating follow-up on the future of WSGI
Thu, 21 Jan 2016 17:24:25 +1100
Graham Dumpleton <[email protected]> • #5176
Re: Collating follow-up on the future of WSGI
Thu, 21 Jan 2016 05:13:51 +0000
Benoit Chesneau <[email protected]> • #5175
Fwd: Collating follow-up on the future of WSGI
Thu, 21 Jan 2016 05:12:51 +0000
Benoit Chesneau <[email protected]> • #5174
Re: Collating follow-up on the future of WSGI
Thu, 21 Jan 2016 09:37:19 +1100
Graham Dumpleton <[email protected]> • #5173
Re: Collating follow-up on the future of WSGI
Thu, 21 Jan 2016 11:36:50 +1300
Robert Collins <[email protected]> • #5172
Re: Collating follow-up on the future of WSGI
Wed, 20 Jan 2016 22:27:57 +0000
Benoit Chesneau <[email protected]> • #5171
Re: Collating follow-up on the future of WSGI
Thu, 21 Jan 2016 07:28:01 +1100
Graham Dumpleton <[email protected]> • #5170
Re: Collating follow-up on the future of WSGI
Wed, 20 Jan 2016 15:48:41 +0000
Benoit Chesneau <[email protected]> • #5169
Re: Collating follow-up on the future of WSGI
Wed, 20 Jan 2016 15:33:25 +0000
Robert Brewer <[email protected]> • #5168
Re: Collating follow-up on the future of WSGI
Wed, 20 Jan 2016 13:03:57 +0000
Cory Benfield <[email protected]> • #5167
Re: Collating follow-up on the future of WSGI
Wed, 20 Jan 2016 23:37:41 +1100
Graham Dumpleton <[email protected]> • #5166
Re: Collating follow-up on the future of WSGI
Wed, 20 Jan 2016 13:24:14 +0100
André Malo <nd-qeD/[email protected]> • #5165
Re: Collating follow-up on the future of WSGI
Wed, 20 Jan 2016 23:03:19 +1100
Graham Dumpleton <[email protected]> • #5164
Re: Collating follow-up on the future of WSGI
Wed, 20 Jan 2016 12:25:40 +0100
André Malo <nd-qeD/[email protected]> • #5163
Re: Collating follow-up on the future of WSGI
Wed, 20 Jan 2016 10:53:01 +0000
Cory Benfield <[email protected]> • #5162
Re: Collating follow-up on the future of WSGI
Wed, 20 Jan 2016 16:21:45 +1000
Graham Dumpleton <[email protected]> • #5161
Re: Collating follow-up on the future of WSGI
Wed, 20 Jan 2016 16:09:38 +1000
Graham Dumpleton <[email protected]> • #5160
Re: Collating follow-up on the future of WSGI
Wed, 20 Jan 2016 16:04:48 +1000
Graham Dumpleton <[email protected]> • #5159
Re: Collating follow-up on the future of WSGI
Wed, 20 Jan 2016 13:57:56 +1300
Robert Collins <[email protected]> • #5158
Re: Collating follow-up on the future of WSGI
Tue, 19 Jan 2016 23:04:49 +0000
Benoit Chesneau <[email protected]> • #5157
Re: Collating follow-up on the future of WSGI
Wed, 20 Jan 2016 11:56:25 +1300
Robert Collins <[email protected]> • #5156
Re: Collating follow-up on the future of WSGI
Tue, 19 Jan 2016 22:40:46 +0000
Benoit Chesneau <[email protected]> • #5155
Re: Collating follow-up on the future of WSGI
Wed, 20 Jan 2016 08:34:12 +1000
Graham Dumpleton <[email protected]> • #5154
Re: Collating follow-up on the future of WSGI
Tue, 19 Jan 2016 22:29:04 +0000
Benoit Chesneau <[email protected]> • #5153
Re: Collating follow-up on the future of WSGI
Wed, 20 Jan 2016 07:49:13 +1000
Graham Dumpleton <[email protected]> • #5152
Re: Collating follow-up on the future of WSGI
Tue, 19 Jan 2016 21:43:02 +0000
Benoit Chesneau <[email protected]> • #5151
Re: Collating follow-up on the future of WSGI
Wed, 20 Jan 2016 07:24:58 +1000
Graham Dumpleton <[email protected]> • #5150
Collating follow-up on the future of WSGI
Tue, 19 Jan 2016 16:55:14 +0000
Cory Benfield <[email protected]> • #5149
Re: WSGI 2.0 Round 2: requirements and call for interest
Thu, 7 Jan 2016 10:58:51 +0000
Cory Benfield <[email protected]> • #5148
Re: WSGI 2.0 Round 2: requirements and call for interest
Thu, 7 Jan 2016 03:03:00 +0100
Damjan Georgievski <[email protected]> • #5147
Re: WSGI 2.0 Round 2: requirements and call for interest
Thu, 7 Jan 2016 07:06:44 +1100
Graham Dumpleton <[email protected]> • #5146
Re: WSGI 2.0 Round 2: requirements and call for interest
Wed, 6 Jan 2016 19:41:55 +0100
André Malo <nd-qeD/[email protected]> • #5145
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.