On 23.09.2006, at 06:46, Baiju M wrote:
On 9/22/06, Jim Fulton <[EMAIL PROTECTED]> wrote:
Finally, I'm experimenting with using launchpad for bugs:
https://launchpad.net/products/zc.buildout/+bugs
and feature requests:
https://features.launchpad.net/products/zc.buildout/
So far this
On 9/22/06, Jim Fulton <[EMAIL PROTECTED]> wrote:
Finally, I'm experimenting with using launchpad for bugs:
https://launchpad.net/products/zc.buildout/+bugs
and feature requests:
https://features.launchpad.net/products/zc.buildout/
So far this is working OK. I haven't really stressed i
On 9/22/06, Philipp von Weitershausen <[EMAIL PROTECTED]> wrote:
Actually, I was recently told that one of the advantages of JARs are
that the META-INF data is actually more easily read and written than the
EGG-INFO stuff. Again, I'm pretending not to know much here ;)
Might be; that I don't kn
Fred Drake wrote:
On 9/22/06, Philipp von Weitershausen <[EMAIL PROTECTED]> wrote:
Right. Or in old-skool distutils world, you can use a setup.cfg file:
http://docs.python.org/dist/setup-config.html
Oddly, the setup.cfg file is not used as a source for much of the
metadata passed to the setup(
On 9/22/06, Philipp von Weitershausen <[EMAIL PROTECTED]> wrote:
Right. Or in old-skool distutils world, you can use a setup.cfg file:
http://docs.python.org/dist/setup-config.html
Oddly, the setup.cfg file is not used as a source for much of the
metadata passed to the setup() function, AFAICT.
Jim Fulton wrote:
On Sep 22, 2006, at 1:31 PM, Stephan Richter wrote:
On Friday 22 September 2006 12:52, Martijn Faassen wrote:
I hope we can move to a pattern where projects gain a homepage somewhere
on zope.org, including doctests and some other information, and the
cheeseshop is used for e
Jim Fulton wrote:
Uh, why are we parsing the entries file?
To get the current revision of the Zope 3 checkout...
mkzopeinstance.py fails with;
...
File
"C:\Python24\Lib\site-packages\zope3\src\zope\app\applicationcontrol\zope
version.py", line 68, in __setSVNVersion
doc = parse(entriesf
On Sep 22, 2006, at 1:31 PM, Stephan Richter wrote:
On Friday 22 September 2006 12:52, Martijn Faassen wrote:
I hope we can move to a pattern where projects gain a homepage
somewhere
on zope.org, including doctests and some other information, and the
cheeseshop is used for everything else (p
On Sep 22, 2006, at 12:52 PM, Martijn Faassen wrote:
Jim Fulton wrote:
...
Some things to note:
I knit all of the .txt files, including documentation-oriented
doctest files together in the distutils long description. This
causes the pypi page to be pretty informative:
http://www.pytho
Uh, why are we parsing the entries file?
On Sep 22, 2006, at 2:39 PM, Kent Tenney wrote:
Howdy,
mkzopeinstance.py fails with;
...
File "C:\Python24\Lib\site-packages\zope3\src\zope\app
\applicationcontrol\zope
version.py", line 68, in __setSVNVersion
doc = parse(entriesfile)
File "C:\P
Howdy,
mkzopeinstance.py fails with;
...
File "C:\Python24\Lib\site-packages\zope3\src\zope\app\applicationcontrol\zope
version.py", line 68, in __setSVNVersion
doc = parse(entriesfile)
File "C:\Python24\lib\site-packages\xml\dom\minidom.py", line 1915, in parse
return expatbuilder.parse(
On Friday 22 September 2006 12:52, Martijn Faassen wrote:
> I hope we can move to a pattern where projects gain a homepage somewhere
> on zope.org, including doctests and some other information, and the
> cheeseshop is used for everything else (pointing to the homepage on
> zope.org with the 'url'
Hi there,
Since the advent of the 'Framework :: Zope3' trove classifier, I've
started uploading a bunch of zc.* packages to the cheeseshop. I've only
done minimal work on the setup.py by the way - volunteers are welcome to
do more documentation including after the example of zc.buildout.
To
Gary Poster wrote:
[snip]
Also, for these, we're taking the tack of "We're not ashamed of calling
it 1.0" rather than the 0.x "Oh, when will I reach perfection"
approach.
Good point. I'll be a bit more aggressive with 1.0 in the future.
Regards,
Martijn
Jim Fulton wrote:
On Sep 22, 2006, at 11:47 AM, Martijn Faassen wrote:
I am about to do a new egg release of zc.catalog and will be putting
out other eggs as well (to the cheeseshop as we now have our own
category there).
I notice in the SVN that there have been quite a few changes to
zc.
On Sep 22, 2006, at 11:47 AM, Martijn Faassen wrote:
Hi there,
I am about to do a new egg release of zc.catalog and will be
putting out other eggs as well (to the cheeseshop as we now have
our own category there).
I notice in the SVN that there have been quite a few changes to
zc.catal
Hi there,
I am about to do a new egg release of zc.catalog and will be putting out
other eggs as well (to the cheeseshop as we now have our own category
there).
I notice in the SVN that there have been quite a few changes to
zc.catalog. We do not have any CHANGES.txt or such, so it's very ha
On Sep 22, 2006, at 5:06 AM, Martijn Faassen wrote:
Jim Fulton wrote:
On Sep 21, 2006, at 11:31 AM, Stephan Richter wrote:
[snip]
This has been proposed and approved, but implementation has been
delayed due to missing XPath features.
http://www.zope.org/Wikis/DevSite/Projects/ComponentArc
* Philipp von Weitershausen <[EMAIL PROTECTED]> [2006-09-22 10:49]:
> Wolfgang Schnerring wrote:
> >>>However, when I tried to refactor zope.location.location.LocationProxy
> >>>to use said base classes, it broke the functional tests for
> >>>zope.app.apidoc.introspector -- for reasons I totally do
Jim Fulton wrote:
On Sep 21, 2006, at 11:31 AM, Stephan Richter wrote:
[snip]
This has been proposed and approved, but implementation has been
delayed due to missing XPath features.
http://www.zope.org/Wikis/DevSite/Projects/ComponentArchitecture/ZCMLEnhancements
I have a feeling that xp
Wolfgang Schnerring wrote:
* Philipp von Weitershausen <[EMAIL PROTECTED]> [2006-09-22 10:01]:
However, when I tried to refactor zope.location.location.LocationProxy
to use said base classes, it broke the functional tests for
zope.app.apidoc.introspector -- for reasons I totally don't
understand
* Philipp von Weitershausen <[EMAIL PROTECTED]> [2006-09-22 10:01]:
> >However, when I tried to refactor zope.location.location.LocationProxy
> >to use said base classes, it broke the functional tests for
> >zope.app.apidoc.introspector -- for reasons I totally don't
> >understand.
>
> A traceback
On Friday 22 September 2006 04:00, Wolfgang Schnerring wrote:
> Question: Should the base classes be removed or should the apidoc be
> fixed to cope with them?
Fix APIDOC. APIDOC uses a lot of magic and internal knowledge about the system
to provide the info it does. With changes like that APIDOC
Wolfgang Schnerring wrote:
Hi,
I just refactored zope.decorator into zope.proxy.decorator and
zope.security.decorator as discussed in
http://thread.gmane.org/gmane.comp.web.zope.zope3/18581.
Contrary to that discussion, Theuni and I thought that the
*DecoratorBase classes are actually useful be
Hi,
I just refactored zope.decorator into zope.proxy.decorator and
zope.security.decorator as discussed in
http://thread.gmane.org/gmane.comp.web.zope.zope3/18581.
Contrary to that discussion, Theuni and I thought that the
*DecoratorBase classes are actually useful because they provide an
abstrac
Looks better now. I suggest filing a collector issue and attaching the
patch. Somebody knowledgeable can then look at it.
Simon Hang wrote:
Philipp,
Sorry for being lazy, and thanks for the tips. Here is my update version.
--- httptask.py.origFri Jan 06 02:15:48 2006
+++ httptask.py Fri Se
The Buildbot has detected a failed build of Zope3 trunk 2.4 Windows 2000
zc-bbwin3.
Buildbot URL: http://buildbot.zope.org/
Build Reason: changes
Build Source Stamp: 7812
Blamelist: ctheune,wosc
BUILD FAILED: failed test_2
sincerely,
-The Buildbot
The Buildbot has detected a failed build of Zope3 trunk 2.4 Linux tlotze.
Buildbot URL: http://buildbot.zope.org/
Build Reason: changes
Build Source Stamp: 7812
Blamelist: ctheune,wosc
BUILD FAILED: failed test_2
sincerely,
-The Buildbot
___
Zope3-d
28 matches
Mail list logo
