Re: [Zope-dev] Where does ISite belong conceptually?
Martijn Faassen wrote: > Thomas Lotze wrote: >> I wonder: should we start requiring that the object passed to setSite() >> implement (or even be adaptable to) IPossibleSite? > > I think the simplest way forward would be not to change the semantics as > part of this step. Agreed. -- Thomas ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] A note on the PyCon Program committee.
I had a "rethinking interfaces" talk accepted. It's about the positives and negatives of zope.interface and zope.component, driven primarily from the perspective and experience of the Launchpad team, and myself in particular; and about changes that might be made or differences we are interested in. It is an advocacy piece only in the sense that we are saying that, by- and-large, we like what the packages give us, but it is more challenging than that. It's an interesting pairing to Jeff Shell's invited talk, which appears to cover some of the same ground from more of an advocacy/tutorial perspective. I was honestly a bit surprised that mine was accepted when Jeff's was already scheduled, but maybe mine is "the dark side" version of his talk. :-) Gary On Nov 3, 2009, at 2:13 PM, Chris McDonough wrote: > So were any Zope talks/tutorials accepted? > > FWIW, Tres had a BFG talk accepted, and Carlos had a BFG talk and a > BFG > tutorial accepted. I proposed a talk about profiling that didn't > make it. > > The TG guys had one talk accepted. > > Not sure about Pylons. > > I assume Django had a bunch, but I don't know for sure. > > - C > > > Martijn Faassen wrote: >> Chris McDonough wrote: >> [snip] >>> Another way to avoid this in the future besides joining the >>> committee would be >>> for notable members of the Zope community to reach out on a >>> regular (daily) >>> basis to other Python-using communities. Offer them well- >>> documented software, >>> visit their sprints and conferences, try their alphas, join their >>> IRC channels, >>> participate in their maillists and so on. It's harder to do >>> intercommunity >>> politics daily in this way as opposed to "facing off" yearly, but >>> it will have >>> a higher, more lasting payoff. >> >> I'm very much in agreement on this. Blogging is another way to reach >> out. Reach out and interact. >> >> It's indeed hard work to do this right. I am sitting on a few >> pieces of >> software that are either interesting to non-Zope people or in fact >> directly usable, but I haven't had the time yet to blog about them. I >> intend to start blogging on a more regular basis again soon. >> >>> It's "who you know", not "what you know" unfortunately, even in >>> open source, as >>> much as we like to believe in meritocracy. >> >> That's true too. I'm a natural noise-maker, and I discovered that >> while >> as a result of this I embarrass myself in public on a regular >> basis, it >> also means a lot of people know who I am. That's a good thing. >> >> Regards, >> >> Martijn >> >> ___ >> Zope-Dev maillist - Zope-Dev@zope.org >> https://mail.zope.org/mailman/listinfo/zope-dev >> ** No cross posts or HTML encoding! ** >> (Related lists - >> https://mail.zope.org/mailman/listinfo/zope-announce >> https://mail.zope.org/mailman/listinfo/zope ) >> > > ___ > Zope-Dev maillist - Zope-Dev@zope.org > https://mail.zope.org/mailman/listinfo/zope-dev > ** No cross posts or HTML encoding! ** > (Related lists - > https://mail.zope.org/mailman/listinfo/zope-announce > https://mail.zope.org/mailman/listinfo/zope ) ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] A note on the PyCon Program committee.
On Nov 3, 2009, at 4:48 PM, Chris McDonough wrote: > Gary Poster wrote: ... >> It is an advocacy piece only in the sense that we are saying that, >> by-and-large, we like what the packages give us, but it is more >> challenging than that. It's an interesting pairing to Jeff Shell's >> invited talk, which appears to cover some of the same ground from >> more of an advocacy/tutorial perspective. I was honestly a bit >> surprised that mine was accepted when Jeff's was already scheduled, >> but maybe mine is "the dark side" version of his talk. :-) > > It's Jeff Rush.. Bah, I knew that. Thanks for the correction. Sorry, Jeffs. Gary ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] A note on the PyCon Program committee.
On Nov 3, 2009, at 3:28 PM, Lennart Regebro wrote: > 2009/11/3 Gary Poster : >> I had a "rethinking interfaces" talk accepted. It's about the >> positives and negatives of zope.interface and zope.component, driven >> primarily from the perspective and experience of the Launchpad team, >> and myself in particular; and about changes that might be made or >> differences we are interested in. >> >> It is an advocacy piece only in the sense that we are saying that, >> by- >> and-large, we like what the packages give us, but it is more >> challenging than that. It's an interesting pairing to Jeff Shell's >> invited talk, which appears to cover some of the same ground from >> more >> of an advocacy/tutorial perspective. I was honestly a bit surprised >> that mine was accepted when Jeff's was already scheduled, but maybe >> mine is "the dark side" version of his talk. :-) > > Well, if you cover the good and bad sides, as your great OSCON talk > did, but then also proposes what can be done about the bad sides, your > talk would be of narrower interest, but also more important. :-) Cool, I'll aim for that. :-) > I'm really sorry I can't go to PyCon this year, the talks are going to > be awesome. Hopefully I can see the talk online at some stage. :) I'm sorry you won't be there too, but thank you! Gary ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] A note on the PyCon Program committee.
Chris McDonough wrote: > So were any Zope talks/tutorials accepted? I have no idea, besides BFG, which is at the very least Zope related. :) Lennart? Regards, Martijn ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] A note on the PyCon Program committee.
So were any Zope talks/tutorials accepted? FWIW, Tres had a BFG talk accepted, and Carlos had a BFG talk and a BFG tutorial accepted. I proposed a talk about profiling that didn't make it. The TG guys had one talk accepted. Not sure about Pylons. I assume Django had a bunch, but I don't know for sure. - C Martijn Faassen wrote: > Chris McDonough wrote: > [snip] >> Another way to avoid this in the future besides joining the committee would >> be >> for notable members of the Zope community to reach out on a regular (daily) >> basis to other Python-using communities. Offer them well-documented >> software, >> visit their sprints and conferences, try their alphas, join their IRC >> channels, >> participate in their maillists and so on. It's harder to do intercommunity >> politics daily in this way as opposed to "facing off" yearly, but it will >> have >> a higher, more lasting payoff. > > I'm very much in agreement on this. Blogging is another way to reach > out. Reach out and interact. > > It's indeed hard work to do this right. I am sitting on a few pieces of > software that are either interesting to non-Zope people or in fact > directly usable, but I haven't had the time yet to blog about them. I > intend to start blogging on a more regular basis again soon. > >> It's "who you know", not "what you know" unfortunately, even in open source, >> as >> much as we like to believe in meritocracy. > > That's true too. I'm a natural noise-maker, and I discovered that while > as a result of this I embarrass myself in public on a regular basis, it > also means a lot of people know who I am. That's a good thing. > > Regards, > > Martijn > > ___ > Zope-Dev maillist - Zope-Dev@zope.org > https://mail.zope.org/mailman/listinfo/zope-dev > ** No cross posts or HTML encoding! ** > (Related lists - > https://mail.zope.org/mailman/listinfo/zope-announce > https://mail.zope.org/mailman/listinfo/zope ) > ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] A note on the PyCon Program committee.
I also proposed a Grok tutorial, but I've had no word about its acceptance or declination. My zope talk where I would discuss Grok, buildout and zope.component was rejected. Carlos de la Guardia On Tue, Nov 3, 2009 at 1:13 PM, Chris McDonough wrote: > So were any Zope talks/tutorials accepted? > > FWIW, Tres had a BFG talk accepted, and Carlos had a BFG talk and a BFG > tutorial accepted. I proposed a talk about profiling that didn't make it. > > The TG guys had one talk accepted. > > Not sure about Pylons. > > I assume Django had a bunch, but I don't know for sure. > > - C > > > Martijn Faassen wrote: >> Chris McDonough wrote: >> [snip] >>> Another way to avoid this in the future besides joining the committee would >>> be >>> for notable members of the Zope community to reach out on a regular (daily) >>> basis to other Python-using communities. Offer them well-documented >>> software, >>> visit their sprints and conferences, try their alphas, join their IRC >>> channels, >>> participate in their maillists and so on. It's harder to do intercommunity >>> politics daily in this way as opposed to "facing off" yearly, but it will >>> have >>> a higher, more lasting payoff. >> >> I'm very much in agreement on this. Blogging is another way to reach >> out. Reach out and interact. >> >> It's indeed hard work to do this right. I am sitting on a few pieces of >> software that are either interesting to non-Zope people or in fact >> directly usable, but I haven't had the time yet to blog about them. I >> intend to start blogging on a more regular basis again soon. >> >>> It's "who you know", not "what you know" unfortunately, even in open >>> source, as >>> much as we like to believe in meritocracy. >> >> That's true too. I'm a natural noise-maker, and I discovered that while >> as a result of this I embarrass myself in public on a regular basis, it >> also means a lot of people know who I am. That's a good thing. >> >> Regards, >> >> Martijn >> >> ___ >> Zope-Dev maillist - zope-...@zope.org >> https://mail.zope.org/mailman/listinfo/zope-dev >> ** No cross posts or HTML encoding! ** >> (Related lists - >> https://mail.zope.org/mailman/listinfo/zope-announce >> https://mail.zope.org/mailman/listinfo/zope ) >> > > ___ > Zope-Dev maillist - zope-...@zope.org > https://mail.zope.org/mailman/listinfo/zope-dev > ** No cross posts or HTML encoding! ** > (Related lists - > https://mail.zope.org/mailman/listinfo/zope-announce > https://mail.zope.org/mailman/listinfo/zope ) > ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] A note on the PyCon Program committee.
2009/11/3 Gary Poster : > I had a "rethinking interfaces" talk accepted. It's about the > positives and negatives of zope.interface and zope.component, driven > primarily from the perspective and experience of the Launchpad team, > and myself in particular; and about changes that might be made or > differences we are interested in. > > It is an advocacy piece only in the sense that we are saying that, by- > and-large, we like what the packages give us, but it is more > challenging than that. It's an interesting pairing to Jeff Shell's > invited talk, which appears to cover some of the same ground from more > of an advocacy/tutorial perspective. I was honestly a bit surprised > that mine was accepted when Jeff's was already scheduled, but maybe > mine is "the dark side" version of his talk. :-) Well, if you cover the good and bad sides, as your great OSCON talk did, but then also proposes what can be done about the bad sides, your talk would be of narrower interest, but also more important. :-) I'm really sorry I can't go to PyCon this year, the talks are going to be awesome. Hopefully I can see the talk online at some stage. :) -- Lennart Regebro: Python, Zope, Plone, Grok http://regebro.wordpress.com/ +33 661 58 14 64 ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Where does ISite belong conceptually?
Thomas Lotze wrote: > Thomas Lotze wrote: > >> While writing tests for the zope.site.hooks module I'm moving to >> zope.component, I notice that the module calls getSiteManager() on an site >> object. Such an object isn't technically required to implement an >> interface that declares that method, but there is one, or rather a pair of >> them: IPossibleSite and ISite. > > I wonder: should we start requiring that the object passed to setSite() > implement (or even be adaptable to) IPossibleSite? I think the simplest way forward would be not to change the semantics as part of this step. Regards, Martijn ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Zope Tests: 6 OK
Summary of messages to the zope-tests list. Period Mon Nov 2 12:00:00 2009 UTC to Tue Nov 3 12:00:00 2009 UTC. There were 6 messages: 6 from Zope Tests. Tests passed OK --- Subject: OK : Zope-2.10 Python-2.4.6 : Linux From: Zope Tests Date: Mon Nov 2 20:39:13 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-November/012944.html Subject: OK : Zope-2.11 Python-2.4.6 : Linux From: Zope Tests Date: Mon Nov 2 20:41:13 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-November/012945.html Subject: OK : Zope-2.12 Python-2.6.2 : Linux From: Zope Tests Date: Mon Nov 2 20:43:13 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-November/012946.html Subject: OK : Zope-2.12-alltests Python-2.6.2 : Linux From: Zope Tests Date: Mon Nov 2 20:45:13 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-November/012947.html Subject: OK : Zope-trunk Python-2.6.2 : Linux From: Zope Tests Date: Mon Nov 2 20:47:13 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-November/012948.html Subject: OK : Zope-trunk-alltests Python-2.6.2 : Linux From: Zope Tests Date: Mon Nov 2 20:49:14 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-November/012949.html ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Testrunner option for running tests in random order?!?
Hello Christian, On Tue, Nov 3, 2009 at 11:07 AM, Christian Theune wrote: > [...] btw: do you log the seed if > you generated one?) Yep, the seed is displayed at the end of tests, so that it can be reused to reproduce a failing test. $ ./bin/test --shuffle -cvvv Running tests at level 1 Running zope.testing.testrunner.layer.UnitTests tests: Set up zope.testing.testrunner.layer.UnitTests in 0.000 seconds. ... Ran 257 tests with 0 failures and 0 errors in 21.908 seconds. Tests were shuffled using seed number 321854366611 I already find it *very* useful ... Cheers, Jonathan ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Testrunner option for running tests in random order?!?
On 10/19/2009 11:57 AM, Jonathan Ballet wrote: > Hello there, > > as I mentioned by Sebastien, the patch has been commited into the > sdouche-shuffle branch. It now has tests and a bit of documentation > too. > > Regarding CLI arguments, I'm not sure this could be changed like > Christian proposed. If you know how to do it, I'm listening, 'cause I > don't know! :) > > I have one more thing I would like to discuss: how should this feature > behave with the --repeat feature? > Currently, the shuffling is done before the repeat feature. This means > that tests will *not* get reordered for each loop (just once, at the > very beginning of tests launching). > I know how to do it, so that for each loop, tests will get a different > order (basically, I would propose to wrap the __iter__() method of the > TestSuite used to launch tests, and to shuffle here): > > class ShuffledTestSuite(unittest.TestSuite): > def __iter__(self): > tests = list(super(Shuffled, self)) > seed = long(time.time() * 256) > shuffler = random.Random() > shuffler.shuffle(tests) > return iter(tests) > > However, using this means we would loose the seed printing (which > seems very convenient to me). I'm not sure if we could get it and > print it for each loop... I'd say leave it as is for now. I think it's more important to be able to seed (for the sake of reproduction, so btw: do you log the seed if you generated one?) externally than to reorder during each repeated run. Also, we can add that later on in case you figure out a way how to do it. ;) Christia -- Christian Theune · c...@gocept.com gocept gmbh & co. kg · forsterstraße 29 · 06112 halle (saale) · germany http://gocept.com · tel +49 345 1229889 0 · fax +49 345 1229889 1 Zope and Plone consulting and development ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Zope Tests: 6 OK, 2 Failed
FWIW, Martijn is correct. Python 2.4 does not like values > 2**31-1 for list indexes, slices, e.a. even on 64 bit systems. I have disabled the respective test runs. Stefan On 01.11.2009, at 14:43, Martijn Pieters wrote: > 2009/10/31 Tres Seaver : >> I can't reproduce this failure when running the Acquisition 2.12.4 >> tests >> with Python 2.4 on my machine. > > This is python 2.4 on 64-bit linux. I bet it's because of: > > typedef int Py_ssize_t; > > and sys.maxint overflows to -1 with that definition. I suspect that > all open-ended slicing ops in Python C extensions are borken in python > 2.4, because it doesn't have Py_ssize_t. -- Stefan H. Holek ste...@epy.co.at ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
