omething like it) back in the future
> to support chunked streaming output,
IIRC, Christian Theune wrote that he had been using 'response.write'; I
think the note was in the "Twisted Publisher" thread about a week and a
half back.
CC'ing him to ensure he knows to respo
out to the file system where Apache can serve them.
Heh, that would be tramline, or half of it, anyway. ;)
http://faassen.n--tree.net/blog/view/weblog/2005/11/11/0
Tres.
- --
===
Tres Seaver +1 202-558-7113
ths, including zope.file, zope.ucol, zope.locking, and
> zc.catalog. They all are worth a look.
Kudos for releasing these packages -- they all look interesting and
potentially useful.
Tres.
- --
===
Tres Seaver +1 2
der()'s. I note that the
> zope.contentprovider README.txt mentions that this is bad, but the
> TALESProviderExpression implementation seems to suffer from exactly the
> same problem.
>
> - Is this expected behaviour? Is it considered as "known issue"? Are
> there p
dout...
While:
Installing.
Getting section app.
Initializing section app.
Installing recipe zc.zope3recipes>=0.5.3.
Getting distribution for 'zc.zope3recipes==0.6b1'.
Error: Couldn't find a distribution for 'zc.zope3recipes==0.6b1'.
Tres.
- --
=
se multiple PackageIndex objects within a
setuptools-enabled program.
> So it is
> necessary that I make all packages available in that index and this is what I
> produce as download.zope.org/zope3.4. But I have explained this multiple
> times before, so I am not going to repeat the argument an
index
> from these. But currently I think only Tres knows how to make it do
> it. ;-)
One you have a tested set of packages installed (findable on sys.path,
actually), compoze can download the corresponding distributiongs and
make a package index via:
$ bin/compoze fetch --fetch-site
n a released 'zope3", should begin to move their dependencies to
the "meta-egg"-based scheme outlined above: in fact, they are
probably good candidates for defining such a meta-egg.
- Deployments which need non-egg-based packaging will need to figure
out how to use
n a released 'zope3", should begin to move their dependencies to
the "meta-egg"-based scheme outlined above: in fact, they are
probably good candidates for defining such a meta-egg.
- Deployments which need non-egg-based packaging will need to figure
out how to use
