Hi.
I have a patch for Zope that sets expiry dates far into the future for
certain cookies. However, I would like to know something about where the
user is, or what the user is doing.
Is there a way to get the REQUEST from within a RESPONSE method?
TIA,
Morten
Hi,
If anybody can give some pointers, it would be greatly appreciated.
Thanks Regards,
Sanjay Rao
___
Zope-Dev maillist - Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
On Sun, 2012-01-29 at 16:17 +0100, Charlie Clark wrote:
snip
From the zope.schema 4.0.0 release notes:
Port to Python 3. This adds a dependency on six and removes support for
Python 2.5
Shouldn't that also mean a preference of
for key in _dict over for key in _dict.keys() ?
Though
On Mon, Jan 30, 2012 at 6:26 AM, Sanjay Rao
s...@noida.interrasystems.com wrote:
...
If anybody can give some pointers, it would be greatly appreciated.
I recommend using an established SOAP server. You should be able to
use application code that works with Zope3/ZTK/whatever with any server
On Fri, 2012-01-27 at 11:50 +0100, Souheil CHELFOUH wrote:
Yes, Marius got exactly what I meant, this is how I usually make the
not-so-pluggable stuff pluggable :)
About the fact to release it out of zope.schema, it's also to be able
to make it live a bit and prove itself.
Then, including it
Hiya,
Am 30.01.2012, 14:33 Uhr, schrieb Jan-Carel Brand li...@opkode.com:
... lots cut ...
Yes, the values must be unique, because we do value lookups.
The title attr doesn't have to be unique though. You could have a
Forestry department for two different regions. The title will be the
same,
Snip snip
Marius and Souheil, what do you think about this? I think it probably
still makes sense to have a dict_factory as Souheil suggested, but then
we make the default type OrderedDict and not dict.
This sounds perfectly reasonnable.
Any objections?
Not really
This is the summary for test reports received on the
zope-tests list between 2012-01-29 00:00:00 UTC and 2012-01-30 00:00:00 UTC:
See the footnotes for test reports of unsuccessful builds.
An up-to date view of the builders is also available in our
buildbot documentation:
Hello,
I think we need to automate sdist upload, the .mo files are missing
from the release.
Any ideas other than patching setup.py to create the .mo files
automatically?
On Mon, 30 Jan 2012 23:03:08 -0500 (EST) you wrote:
Log message for revision 124260:
Get ready for 2.6.1 release.
On 1/30/12 11:15 PM, Adam GROSZER wrote:
Hello,
I think we need to automate sdist upload, the .mo files are missing
from the release.
Any ideas other than patching setup.py to create the .mo files
automatically?
See zest.releaser [1] and its plugin zest.pocompile [2]
[1]
10 matches
Mail list logo
