Chris Withers wrote:
> Jim Fulton wrote:
No, it's not a bug. This is in fact a feature (like it or not).
>>> While I respect that this feature may have been chosen carefully, it
>>> nevertheless seems more like a misfeature. Chris' expectation was
>>> reasonable and ought not to be violated w
Jim Fulton wrote:
>>> No, it's not a bug. This is in fact a feature (like it or not).
>> While I respect that this feature may have been chosen carefully, it
>> nevertheless seems more like a misfeature. Chris' expectation was
>> reasonable and ought not to be violated without a good cause.
>
> q
Philipp von Weitershausen wrote:
> No, it's not a bug. This is in fact a feature (like it or not).
Well, assuming enough people *don't* like it, and I think that's the
case here, then it should probably change...
> {query|get}Adapter will always try to look up an adapter, whether or not
> the
On Aug 19, 2008, at 4:24 PM, Shane Hathaway wrote:
> Philipp von Weitershausen wrote:
>> Shane Hathaway wrote:
>>> Looks like a bug to me. If the object passed as the first
>>> argument to
>>> queryAdapter() implements the interface passed as the second
>>> argument, I
>>> believe queryAdapt
Shane Hathaway wrote:
> Philipp von Weitershausen wrote:
>> Shane Hathaway wrote:
>>> Looks like a bug to me. If the object passed as the first argument to
>>> queryAdapter() implements the interface passed as the second argument, I
>>> believe queryAdapter() should return the object, regardless
Philipp von Weitershausen wrote:
> Shane Hathaway wrote:
>> Looks like a bug to me. If the object passed as the first argument to
>> queryAdapter() implements the interface passed as the second argument, I
>> believe queryAdapter() should return the object, regardless of any
>> component regist
Shane Hathaway wrote:
> Chris Withers wrote:
>> From a user's perspective, this makes no sense:
>>
>> >>> from zope.interface import implements,Interface
>> >>> from zope.component import queryAdapter
>> >>> class ISomething(Interface): pass
>> ...
>> >>> class MyClass: implements(ISomething)
Chris Withers wrote:
> From a user's perspective, this makes no sense:
>
> >>> from zope.interface import implements,Interface
> >>> from zope.component import queryAdapter
> >>> class ISomething(Interface): pass
> ...
> >>> class MyClass: implements(ISomething)
> ...
> >>> m = MyClass()
>
Chris Withers a écrit :
> Philipp von Weitershausen wrote:
>>> and why does buildout pick it over a stable release?
>> Because buildout, like easy_install, will pick the newest available
>> version for a distribution. Fortunately, buildout has a prefer-stable
>> option so that you can tell it to
From a user's perspective, this makes no sense:
>>> from zope.interface import implements,Interface
>>> from zope.component import queryAdapter
>>> class ISomething(Interface): pass
...
>>> class MyClass: implements(ISomething)
...
>>> m = MyClass()
Right, so this does make sense:
>>> ISo
On Aug 19, 2008, at 1:05 PM, Andreas Jung wrote:
>
>
> --On 19. August 2008 12:56:43 -0400 Tres Seaver
> <[EMAIL PROTECTED]> wrote:
>
>
>>
and why does buildout pick it over a stable release?
>>>
>>> Because buildout, like easy_install, will pick the newest available
>>> version for a dist
--On 19. August 2008 12:56:43 -0400 Tres Seaver <[EMAIL PROTECTED]>
wrote:
and why does buildout pick it over a stable release?
Because buildout, like easy_install, will pick the newest available
version for a distribution. Fortunately, buildout has a prefer-stable
option so that you ca
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Philipp von Weitershausen wrote:
> Chris Withers wrote:
>> Why does the egg in the subject line exist
>
> Because somebody made it and uploaded it to download.zope.org. It
> probably happened during the initial eggification period when we didn't
> h
On Aug 19, 2008, at 5:30 AM, Chris Withers wrote:
> Hi All,
>
> Why does the egg in the subject line exist
Because someone saw fit to release it. It's on download.zope.org/
distribution. It''s not in PyPI.
> and why does buildout pick it
> over a stable release?
Because, like setuptools, it
Summary of messages to the zope-tests list.
Period Mon Aug 18 11:00:00 2008 UTC to Tue Aug 19 11:00:00 2008 UTC.
There were 5 messages: 5 from Zope Tests.
Unknown
---
Subject: UNKNOWN : Zope-2.8 Python-2.3.6 : Linux
From: Zope Tests
Date: Mon Aug 18 20:42:37 EDT 2008
URL: http://mail.zope.or
Wichert Akkerman wrote:
> You are missing a line here:
>
> versions = versions
Good catch! Seems to be working now...
cheers,
Chris
--
Simplistix - Content Management, Zope & Python Consulting
- http://www.simplistix.co.uk
___
Zope-Dev
El 19 Aug 2008, a las 12:05 , Chris Withers escribió:
> Philipp von Weitershausen wrote:
>>> and why does buildout pick it over a stable release?
>> Because buildout, like easy_install, will pick the newest available
>> version for a distribution. Fortunately, buildout has a prefer-
>> stable op
Chris Withers wrote:
> Okay,
>
> So I bumped into the ZODB3 3.9.0-dev-r77011 problem while trying to get
> going with zopeproject.
>
> zopeproject created a buildout.cfg in my test project, so I thought I'd
> lock ZODB to 3.8.0 to prevent problems:
>
> [buildout]
> develop = .
> parts = app te
Philipp von Weitershausen wrote:
>> and why does buildout pick it over a stable release?
>
> Because buildout, like easy_install, will pick the newest available
> version for a distribution. Fortunately, buildout has a prefer-stable
> option so that you can tell it to prefer stable over alpha/be
Previously Chris Withers wrote:
> Okay,
>
> So I bumped into the ZODB3 3.9.0-dev-r77011 problem while trying to get
> going with zopeproject.
>
> zopeproject created a buildout.cfg in my test project, so I thought I'd
> lock ZODB to 3.8.0 to prevent problems:
>
> [buildout]
> develop = .
> par
Chris Withers wrote:
> Why does the egg in the subject line exist
Because somebody made it and uploaded it to download.zope.org. It
probably happened during the initial eggification period when we didn't
have a solid release process [1].
> and why does buildout pick it over a stable release?
B
Okay,
So I bumped into the ZODB3 3.9.0-dev-r77011 problem while trying to get
going with zopeproject.
zopeproject created a buildout.cfg in my test project, so I thought I'd
lock ZODB to 3.8.0 to prevent problems:
[buildout]
develop = .
parts = app test
find-links = http://download.zope.org/di
Hi All,
Why does the egg in the subject line exist and why does buildout pick it
over a stable release?
cheers,
Chris
--
Simplistix - Content Management, Zope & Python Consulting
- http://www.simplistix.co.uk
___
Zope-Dev maillist - Zo
Hello,
Seems that zope\app\container\_zope_proxy_proxy.c cannot be compiled
with MS compilers. With python 2.4.5, 2.4.4 and 2.4.3 on winXP.
eek, fails on linux too (debian etch+python 2.4.4)...
I'm not a C guru, with a help from a friend we figured that the
problem is the Py_ssize_t, which i
Roger Ineichen wrote:
> Since this is a miss behavior and I agree that this should get fixed. We
> probably should think about a solution which supports the old behavior by
> default.
>
> Note, this whould probably also break other packages like
> z3c.csvvocabulary.
We've thought about this some
25 matches
Mail list logo
