Re: [Zope-dev] zope-tests - FAILED: 4, OK: 8
On Thursday, September 12, 2013 11:38:16 AM Marius Gedminas wrote:
> m trying to merge the py3 branch to master now. There's one issue:
> the test for https://github.com/zopefoundation/zope.testbrowser/pull/4
> uses the internal .mech_browser attribute.
>
> I think what is actually wanted here is a new API:
>
>browser.handleRedirects = False
>browser.open(...) # or browser.submit()
>assert browser.getHeaders('Status') == '302 Found'
>
> Comments?
+1 That looks good.
Regards,
Stephan
--
Entrepreneur and Software Geek
Google me. "Zope Stephan Richter"
___
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] five.grok -> svn
On Wednesday, April 10, 2013 04:43:17 PM Leonardo Rochael Almeida wrote: > Can anyone please migrate five.grok to GitHub? Done. Regards, Stephan -- Entrepreneur and Software Geek Google me. "Zope Stephan Richter" ___ 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] request for more package migrations to github
On Friday, March 22, 2013 10:23:21 AM Jan-Wijbrand Kolman wrote: > zopetoolkit Is everyone ok with me moving this? Hanno mentioned that several external tools depend on the SVN location and the move was delayed because of that. I think this package also does not have the traditional tags, branches, trunk structure. JW, I'll convert all other packages. Regards, Stephan -- Entrepreneur and Software Geek Google me. "Zope Stephan Richter" ___ 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] [Checkins] [zopefoundation/zope.container] 9100fc: Tagging 3.11.2
On Tuesday, March 19, 2013 08:38:23 AM GitHub wrote: > Commit: b2ae9a9bd5e3dc214f13c6ae77fa06ad55102aba > https://github.com/zopefoundation/zope.container/commit/b2ae9a9bd5e3dc > 214f13c6ae77fa06ad55102aba Author: Matthew Wilkes > Date: 2013-03-19 (Tue, 19 Mar 2013) > > Changed paths: > M setup.py > M src/zope/container/_zope_container_contained.c > M src/zope/container/_zope_proxy_proxy.c > > Log Message: > --- > Comment out the C extension. This should build conditionally, but this is > just for testing I have actually some pypy attempts in a local version as well. The big problem is that the ContainedProxy must inherit from zope.security.proxy.ProxyPy and zope.persistent.persistence.Persistent. Both of those classes define __slots__ so they cannot both be base classes. The only way to fix this, I think, is to change the Python implementation of the security proxy or Persistent to not have slots and only define the slots in a derived class. Regards, Stephan -- Entrepreneur and Software Geek Google me. "Zope Stephan Richter" ___ 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] Problems writing ContainedProxy Python version
Hi everyone,
in an effort to bring zope.container to PyPy, I was trying to port
zope.container. Unfortunately, it defines a ContainedProxy, which inherits from
zope.security's PyProxyBase and persistent's ProxyPy.
Since both of those proxies have slots defined, they cannot both be base
classes for the ContainedProxy. So what should I do? I could split the
existing classes like so, but it seems ugly:
class BaseProxyPy(object):
...
class ProxyPy(BaseProxyPy)
__slots__ = ('_wrapped',)
Jim, Tres, any ideas/comments?
Regards,
Stephan
--
Entrepreneur and Software Geek
Google me. "Zope Stephan Richter"
___
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] Switching zope.testbrowser to webtest instead of mechanize
On Monday, March 04, 2013 08:40:23 PM Andrey Lebedev wrote: > Unfortunately, mechanize package, that zope.testbrowser depends on has > no py3 support. There is an unfinished effort at [1], however, after > closer examination of the codebase and state of the port, it seems more > practical to switch internal implementation of zope.testbrowser to webtest. > > So far, it seems webtest has all the features needed to do the switch. I > started a branch at github ([2]) to track work in progress. The goal is > to make most (say 80%) of existing tests to work without modifications > under new implementation. An update here: The large zope.testbrowser README.txt file is now passing with WebTest in Python 2.7. There are a few more failures to fix, but Andrey is confident he can get those resolved quickly. Regards, Stephan -- Entrepreneur and Software Geek Google me. "Zope Stephan Richter" ___ 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 - FAILED: 6, OK: 12
On Thursday, March 14, 2013 09:59:51 AM Marius Gedminas wrote: > > [2]winbot / z3c.contents_py_265_32 > > [3]winbot / zope.app.applicationcontrol_py_265_32 > > [4]winbot / zope.app.content_py_265_32 > > [5]winbot / zope.app.pagetemplate_py_265_32 > > lxml BTW, Adam has created the binaries[1] now and we are waiting for Stefan Behnel to give our bot PyPI user maintainer access to lxml. .. [1]: Note that Py3.3 is still missing from the list, since we still do not have the Rackspace credentials Regards, Stephan -- Entrepreneur and Software Geek Google me. "Zope Stephan Richter" ___ 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] Version Numbering for Ported Packages
On Wednesday, March 13, 2013 12:03:44 PM Tres Seaver wrote: > > We only moved packages that are still checked by winbot and the pnes > > that we ported because we use them in our project. > > 250+ of them? OK, I retract my concern then, if you are actually using > them. The rough split is like that: - 100+ packages ported to Python 3 (mostly ZTK) - 30+ packages converted for Zope 2 - 25+ packages converted for grok - 50 packages converted for wineggbuilder We have not converted anything without purpose and just because we could. Regards, Stephan -- Entrepreneur and Software Geek Google me. "Zope Stephan Richter" ___ 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] Version Numbering for Ported Packages
On Wednesday, March 13, 2013 11:31:10 AM Tres Seaver wrote: > > FWIW whenever I get a failure notification from Travis about a > > package that doesn't have a .travis.yml, I uncheck the Active checkbox > > in Github repo settings. > > Unless the project already passes all its tests when run manually from a > checkout, please do not turn on any automated reporting. Having > seventy or so of those messages show up directly in my inbox on a > travel-to-Pycon day was major suckage. Please note that I always turn off E-mail notification for Travis in the config file. Marius mentioned to me this morning that the messages were due to having turned on Travis but the package not having a .travis.yml file. I have worked all morning to rectify that and add a .travis.yml to all ZF GitHub packages. > The set of packages now migrated to Github (including zope.app.*, z3c.*) > is far larger than the set which is actually being cared for. I didn't > expect to see most of those packages migrate at all, because they are de > facto abandoned (not used by Zope2, Grok, or any other active project). We only moved packages that are still checked by winbot and the pnes that we ported because we use them in our project. Regards, Stephan -- Entrepreneur and Software Geek Google me. "Zope Stephan Richter" ___ 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] Version Numbering for Ported Packages
On Tuesday, March 12, 2013 04:41:23 PM Marius Gedminas wrote:
> > Note: I think most packages pass fine under Travis, but some are failing
> > for some obscure reasons.
>
> An overview would be good.
>
> I could add a Travis column to http://zope3.pov.lt/py3/, I suppose. The
> image URLs are trivial to generate, assuming Travis knows about every ZF
> repo on Github:
>
> https://api.travis-ci.org/zopefoundation/${reponame}.png?branch=master
I did another overview script here:
https://github.com/zopefoundation/zope.winbot/blob/master/README.rst
It lists all packages that winbot cares about. As we are adding Python
versions to winbot, we can easily extend that table.
Regards,
Stephan
--
Entrepreneur and Software Geek
Google me. "Zope Stephan Richter"
___
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] [zopefoundation/zope.security] 82fd54: Changed strategy to hide wrapped to not use the se...
On Tuesday, March 12, 2013 09:14:26 AM Jim Fulton wrote: > Sorry, why do you want to adapt proxies? The "lying about class", > which is arguably not lying, is intentional and facilitates adapting proxied > objects. No, we really want to adapt the wrapped object, but that is currently not working correctly with the Python proxy implementation, i.e. this is always the result: >>> tuple(providedBy(ProxyPy(orig, checker))) () So I need to figure out why that is. I have *not* looked at the code to see whether zope.interface tries and fails to strip proxies or whether ProxyPy does a security check for __providedBy__ and fails. My bet is on the latter. Regards, Stephan -- Entrepreneur and Software Geek Google me. "Zope Stephan Richter" ___ 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] Version Numbering for Ported Packages
On Monday, March 11, 2013 10:09:51 PM Tres Seaver wrote: > > Of course, the alpha releases are really stable, all the tests pass > > under Python 2.6 and 2.7. > > I'm agreed for the most part. Can we make it a priority to fix the > failing nightly tests? I have asked Adam to create lxml 3.1 binary eggs for Windows. He is waiting for someone to give him the Rackspace credentials, so he can backup the Windows box before installed the latest MSVC version. After that, at least half of the failures should be dealt with. > Also, is somebody running / reporting tests via > Travis? Where are those results going? They should be running for all packages. I have turned off any notifications pending an agreement of where we want the reports to go. The easiest thing right now would be a Wiki page that shows the status icon for each package. Note: I think most packages pass fine under Travis, but some are failing for some obscure reasons. Regards, Stephan -- Entrepreneur and Software Geek Google me. "Zope Stephan Richter" ___ 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] [zopefoundation/zope.security] 82fd54: Changed strategy to hide wrapped to not use the se...
On Monday, March 11, 2013 10:33:30 PM Tres Seaver wrote:
> > Yep, saw that. There are some uncovered lines for which I have to add
> > tests left. Also, I just noticed while prorting zope.publisher to PyPy
> > that proxies cannot be adapted, which is a big issue for any view
> > libraries.
>
> Ouch. That "lying about my type" bit is hard to get over.
I was thinking about dynamically creating proxy classes. Something along the
lines of:
class PyProxy(object):
def __new__(cls, orig):
ProxyForOrig = type('ProxyForOrig', (cls, orig.__class__))
return ProxyForOrig(orig)
That should also help us with our 3-arg pow() call
What do you think?
Regards,
Stephan
--
Entrepreneur and Software Geek
Google me. "Zope Stephan Richter"
___
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] [zopefoundation/zope.security] 82fd54: Changed strategy to hide wrapped to not use the se...
On Monday, March 11, 2013 02:00:55 PM Tres Seaver wrote: > BTW, I merged the branch to the trunk and made a zope.security 4.0.0b1 > release just now. Yep, saw that. There are some uncovered lines for which I have to add tests left. Also, I just noticed while prorting zope.publisher to PyPy that proxies cannot be adapted, which is a big issue for any view libraries. Regards, Stephan -- Entrepreneur and Software Geek Google me. "Zope Stephan Richter" ___ 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] Version Numbering for Ported Packages
Hi everyone, Fred asked about the reasoning behind recent version numbers as we ported packages to Python 3. We decided that any package that depends on an alpha or unreleased package should itself be an alpha release. There are 2 packages that started the avalanche: * zope.security: Tres wanted 4.0.0 to also have PyPy support, so he only did an alpha release to unblock the porting effort. Today, I finished the PyPy support and he released 4.0.0b1. * ZODB: We currently do not have a release for a ported ZODB. For any package requiring the ZODB directly or indirectly, we added a snapshot sdist of the py3 branch into the package to demonstrate the tests passing. (See the zodb- dev mailing list for the current status.) Of course, the alpha releases are really stable, all the tests pass under Python 2.6 and 2.7. Regards, Stephan -- Entrepreneur and Software Geek Google me. "Zope Stephan Richter" ___ 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] [zopefoundation/zope.security] 82fd54: Changed strategy to hide wrapped to not use the se...
On Monday, March 11, 2013 11:56:10 AM Tres Seaver wrote: > > Oh yeah, all tests pass now on py26, py27, py32, py33, and pypy! > > Woohoo! Nice work. BTW, how did you break the import cycle due to the > zope.location monkeypatch? I moved the patch to __init__.py. I know, not zope.location.LocationProxy gets fixed up all the time instead of waiting for decorator to be imported. But it did break the cycle. Regards, Stephan -- Entrepreneur and Software Geek Google me. "Zope Stephan Richter" ___ 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.security with Py3
On Thursday, February 14, 2013 03:42:06 PM Tres Seaver wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On 02/14/2013 03:15 PM, Tres Seaver wrote: > > The work to create a compatible pure-Python proxy is partly done (I > > added tests for all the features of the C version I could discover). > > The version I have in my sandbox doesn't pass all those tests, so I > > haven't pushed it. > > I put that work on a branch: > > https://github.com/zopefoundation/zope.security/tree/pure_python_proxy > > Likely I won't get back to it this week. Hi Tres, do you see yourself working on this again soon? I was going to port some packages to PyPy, but got quickly blocked by zope.security. Regards, Stephan -- Entrepreneur and Software Geek Google me. "Zope Stephan Richter" ___ 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 - FAILED: 11, OK: 12
On Thursday, March 07, 2013 10:42:59 AM Patrick Gerken wrote: > > > [2]winbot / z3c.contents_py_265_32 > > > [3]winbot / z3c.formui_py_265_32 > > > [6]winbot / z3c.pagelet_py_265_32 > > > [5]winbot / z3c.layer.ready2go_py_265_32 > > > > lxml BTW, Adam is waiting for the Rackspace credentials, so he can make a backup of the Windows VM. Then he will install the latest MSVC version and compile eggs for the latest lxml releases. Of course, we are then pending access to PyPI. Regards, Stephan -- Entrepreneur and Software Geek Google me. "Zope Stephan Richter" ___ 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 - FAILED: 11, OK: 12
On Thursday, March 07, 2013 05:46:48 PM Marius Gedminas wrote: > I'm not sure that's the right thing to do. Perhaps page templates, when > given a file on disk with \r\n, should normalize the line endings to \n? > > Opinions? I think we should retain EOL characters as long as clients (i.e. browsers) understand them, which they do. Regards, Stephan -- Entrepreneur and Software Geek Google me. "Zope Stephan Richter" ___ 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] FYI2: Output Checker
Hi everyone, when we ported TAL to Python 3, we had to fix the attribute order and I think Marius sorted them alphabetically. This would break a lot of existing tests. Luckily lxml provides and output checker that verifies the XML structure rather than the string representation. This will solve your HTML/XML output comparison issues. But often you also need your standard RE normalizers as well, but the 2 do not mix. For z3c.form I had developed an output checker that does both. I just released it as a separate package: https://pypi.python.org/pypi/zope.outputchecker Happy porting. :-) Regards, Stephan -- Entrepreneur and Software Geek Google me. "Zope Stephan Richter" ___ 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] FYI: random2
Hi everyone, one of the issues while porting apps to Python 3 is that Python 3 uses a new algorithm for randrange(), which produces different output for Python 2 and 3. I just released random2, which is a port of Python 2.7's `random` module to Python 2.6, 3.2 and 3.3. This way your random output will not change while porting. Note: This is of course most useful to the ones among you that use sampledata generation heavily. Regards, Stephan -- Entrepreneur and Software Geek Google me. "Zope Stephan Richter" ___ 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] GitHub and Travis CI
On Tuesday, March 05, 2013 10:27:24 AM Albertas Agejevas wrote: > > So my question is: What do we want to do? I would suggest E-mails on > > status change should be sufficient. > > It would be cool to have a single page with such status icons for all > packages we care about. So once "zopetoolkit" is on github, we could change its REAdME to contain the status of each package. Regards, Stephan -- Entrepreneur and Software Geek Google me. "Zope Stephan Richter" ___ 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] GitHub and Travis CI
Hi everyone, I have invested some time today to implement the Travis CI hook setup for GitHub. I can now turn on and update Travis CI for any package. Right now, there is no reporting setup. But Travis CI can be configured to send out E-mails and give IRC notifications. In addition, Marius added this to his sample project: https://github.com/zopefoundation/zope.dottedname See the ``README.rst`` file. So my question is: What do we want to do? I would suggest E-mails on status change should be sufficient. Regards, Stephan -- Entrepreneur and Software Geek Google me. "Zope Stephan Richter" ___ 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] SVN to Git Conversion
On Saturday, March 02, 2013 07:56:31 AM Roger wrote: > Is there any information about what this means for zope contributers? Well, we switched all packages to using tox to run tests in all supported Python versions. So running the tests in one Python is not sufficient anymore. In terms of GitHub, if you used Git before, then there is nothing new. GitHub has a lot of nice collaboration and integration features that we can and will use: Checkin commenting, Pull Requests, Travis CI integration, etc. > What are the restrictions or any other relevant parts where we have > to know additional to the git basics? The only restriction that I can think of right now is that an a committer cannot create a repository right now. But we are working on that. For the time being just ask Jim, me, Marius, or Tres to create one for you. As for conversions from SVN to Git, most people will be probably best of asking me to convert a package for them. But the other repository committee members also know how. Regards, Stephan -- Entrepreneur and Software Geek Google me. "Zope Stephan Richter" ___ 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 - FAILED: 15, OK: 12
On Sunday, March 03, 2013 11:48:01 AM Marius Gedminas wrote: > > [2]winbot / z3c.contents_py_265_32 > > [3]winbot / z3c.form_py_265_32 > > [4]winbot / z3c.formui_py_265_32 > > [7]winbot / z3c.pagelet_py_265_32 > > No lxml Can we set up our windows box to build lxml binaries and upload them to PyPI? Regards, Stephan -- Entrepreneur and Software Geek Google me. "Zope Stephan Richter" signature.asc Description: This is a digitally signed message part. ___ 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] Porting Zope to Python 3 Update
Hi everyone, as the week ends, I thought I might give a brief update on the Python 3 porting effort. According to the "Unofficial Zope on Python 3 status page"[1], about 110 packages are ported to Python 3.3. Hanno and I worked this week on updating the ZTK configuration files and I am happy to announce that the ZTK passes all tests on Python 3.3! So once the ZODB is ported, we can start on finalizing all releases, which would pave the way for a ZTK 2.0 release. Marius has made great efforts on finishing the port of ZODB. All the tests pass now on the py3 branch for Python 2.6, 2.7 and 3.3. He has also removed all resource warnings (he started at 400+). The final task will be to integrate zodbpickle. zodbpickle needs some changes to properly enable the "noload()" method. Luckily this work will entail rewriting the dump/load of persistent ids to be more efficient and compatible with cPickle 2.7 pickles. (We are working hard on making Python 2 pickles load on Python 3!) On Wednesday, I was able to run a first Zope 3 (or should I say Bluebream?) app on Python 3.3. Thanks to Andrey and Albertas for porting some of the complex application packages. The sample application can be found in ``zope.paste``[2]. Note the short ZCML[3] and Paster[4] files. Thanks goes to everyone who helped breaking unnecessary and circular dependencies to make this work so well! In the process of all of the above, we have also started moving all packages that we are ported to Python 3 over to GitHub. I have also ported the core packages for Zope 2/4 and Grok already. So what's next? I am in the process of trying to port a rather large demo application[5] to Python 3. We are about 20 packages (that we control) away from that goal. Andrey is currently working on porting zope.testbrowser to Python 3 by changing its internal implementation from mechanize to WebTest (since it is too hard to deal with mechanize). Also, we will have a serious look at ZEO. I hope I got some of you interested in thinking about porting applications to Python 3. [1] http://zope3.pov.lt/py3/ [2] https://github.com/zopefoundation/zope.paste [3] https://github.com/zopefoundation/zope.paste/blob/master/src/zope/paste/test_app/app.zcml [4] https://github.com/zopefoundation/zope.paste/blob/master/src/zope/paste/test_app/app.ini [5] https://github.com/CipherHealth/cipher.uibuilderdemo Regards, Stephan -- Entrepreneur and Software Geek Google me. "Zope Stephan Richter" ___ 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] SVN to Git Conversion
Hi everyone, I am now feeling comfortable with my script to run conversions of many packages at once. Thus, if you want packages moved from SVN to GitHub just let me know and I will convert them for you. Regards, Stephan -- Entrepreneur and Software Geek Google me. "Zope Stephan Richter" ___ 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] "procedures" for moving package to github and porting to Python 3
On Friday, March 01, 2013 02:37:34 PM Jan-Wijbrand Kolman wrote: > megrok.menu It's done now, but it lost its 0.1 tag due to a conversion issue. Regards, Stephan -- Entrepreneur and Software Geek Google me. "Zope Stephan Richter" ___ 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] "procedures" for moving package to github and porting to Python 3
Everything but megrok.menu is now converted. GitHub did not like the fact that I tried to create 26 repos at once, so I had some startup issues. Regards, Stephan On Friday, March 01, 2013 02:37:34 PM Jan-Wijbrand Kolman wrote: > grok > grokcore.annotation > grokcore.catalog > grokcore.chameleon > grokcore.component > grokcore.content > grokcore.formlib > grokcore.json > grokcore.layout > grokcore.message > grokcore.rest > grokcore.security > grokcore.site > grokcore.startup > grokcore.traverser > grokcore.view > grokcore.viewlet > grokcore.xmlrpc > grokproject > grokui.admin > grokui.base > martian > megrok.menu > zope.errorview > zope.fanstatic > z3c.autoinclude > z3c.evalexception > z3c.flashmessage > zc.catalog -- Entrepreneur and Software Geek Google me. "Zope Stephan Richter" ___ 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] "procedures" for moving package to github and porting to Python 3
On Friday, March 01, 2013 02:40:38 PM Jan-Wijbrand Kolman wrote: > > Jim will announce a secret location for the authors.txt file in the next > > days on the ZF mailing list. > > You mean the ZF mailinglist that only ZF members can join? Yeah, but if you are a committer, you are a member. :-) Regards, Stephan -- Entrepreneur and Software Geek Google me. "Zope Stephan Richter" ___ 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] "procedures" for moving package to github and porting to Python 3
On Friday, March 01, 2013 02:37:34 PM Jan-Wijbrand Kolman wrote: > I do see someone just created an empty grokcore.component repository on > github (thanks whoever did that! :-) ) It is actually fully converted. :-) I am going to adjust my script to allow mutliple conversions at once. I will take care of your list. Regards, Stephan -- Entrepreneur and Software Geek Google me. "Zope Stephan Richter" ___ 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] "procedures" for moving package to github and porting to Python 3
On Friday, March 01, 2013 11:17:44 AM Marius Gedminas wrote: > > Could someone perhaps tell me if there's a guideline document, some > > kind of recipe, or perhaps a "conclusive" posting on the mailinglist > > on how to proceed on this topic? > > My attempt at this: https://gist.github.com/mgedmin/4944724 > > AFAIK Stephan migrated most of the zope.* packages using this process. Yes, I have, except that I use a one does it all script published here: https://github.com/zopefoundation/zope.githubsupport All you need to do is to create a zope.cfg that works for you. I can quickly create repositories for you if you send me a list of (pkg_name, pkg_title) tuples. Jim will announce a secret location for the authors.txt file in the next days on the ZF mailing list. Regards, Stephan -- Entrepreneur and Software Geek Google me. "Zope Stephan Richter" ___ 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] ZTK 2.0: Deprecate zope.sequencesort
On Thursday, February 28, 2013 11:32:26 AM Tres Seaver wrote: > > Thoughts? > > I'm generally in favor of shrinking the ZTK, but just for discussion's > sake: emulating 'cmp' for objects which have rich comparison semantics > isn't that difficult:: > > def _faux_cmp(lhs, rhs): > return int(rhs < lhs) - int(lhs < rhs) Well, that is the obvious implementation of cmp(), but that's not the point of the package. The package provides a callable class that represents a cmp() function. The problem is that it is not just creating some keys and calls cmp() on it. I could not find out a way to create a single key. I guess the right way to port the package is to implement a sort API. Regards, Stephan -- Entrepreneur and Software Geek Google me. "Zope Stephan Richter" ___ 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] ZTK Porting Status
Hi all, I went through the ztk-versions.cfg file and verified availability of a Python 3 port. I commented the ztk-versions.cfg file. Below are the relevant sections. If we remove all deprecated pacakges and packages that should not be in use anymore, only the following dependencies/toolchain packages require a Python 3 port: z3c.checkversions z3c.recipe.compattest zope.kgs zc.resourcelibrary zope.mkzeoinstance ZODB (awaiting merge of py3 branch) Luckily we control all these packages. These packages should just be removed from the file: # Deprecating # zope.broken was only needed for ZODB3. zope.broken = 3.6.0 # zope.server has been forked and ported to Py3 under the name "waitress". zope.server = 3.8.6 # RestrictedPython and thus zope.untrustedpython are hard to port to Py3. zope.untrustedpython = 4.0.0 # No package should depend on ZODB3 anymore. ZODB3 = 3.11.0a2 # mechanize should only be needed for testbrowser. mechanize = 0.2.5 Dependencies missing a Python 3 port: # XXX: Where do we need that? Paste = 1.7.5.1 # PasteScript should not be needed anymore, since zope.paste supports serving # directly now. PasteScript = 1.7.5 # Fix by removing it from the ZTK? RestrictedPython = 3.6.0 # XXX: Where is this needed? unittest2 = 0.5.1 # Should just be ported. zc.resourcelibrary = 1.3.4 zope.mkzeoinstance = 3.9.5 # Needs merge of py3 branch. ZODB = 4.0.0a4 # toolchain # Missing py3 port z3c.checkversions = 0.4.1 # Missing py3 port z3c.recipe.compattest = 0.13.1 # Should not be needed anymore: z3c.recipe.scripts = 1.0.1 # Missing py3 port zope.kgs = 1.2.0 Regards, Stephan -- Entrepreneur and Software Geek Google me. "Zope Stephan Richter" ___ 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] ZTK 2.0: Deprecate zope.sequencesort
On Thursday, February 28, 2013 02:59:33 PM Hanno Schlichting wrote: > In the same way, I think we should remove RestrictedPython and > zope.untrustedpython from the ZTK. Since those are also very much > dependencies of Zope alone and porting is going to be a very > challenging task. Well, it is useful for any project allowing end-users to code Python code. I know we do in our project's UI. So I would feel more comfortable in keeping it, but I would not stop a port of my project to Python 3 because of its absence. So maybe ZTK should not either. ;-) I personally do not feel comfortable enough to tackle this package myself though. Regards, Stephan -- Entrepreneur and Software Geek Google me. "Zope Stephan Richter" ___ 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] ZTK 2.0: Deprecate zope.sequencesort
Hi everyone, I would like to deprecate zope.sequencesort in ZTK 2.0, since it cannot properly ported to Python 3, since it depends heavily on the cmp() way of sorting. I am also not a user of the package and I only tried to port the package for completeness sake. Thoughts? Regards, Stephan -- Entrepreneur and Software Geek Google me. "Zope Stephan Richter" ___ 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 - FAILED: 22, OK: 12, UNKNOWN: 2
On Thursday, February 28, 2013 09:00:30 AM Marius Gedminas wrote: > > [9]winbot / z3c.form_py_265_32 > > [10] winbot / z3c.formui_py_265_32 > > No lxml on winbot So we have to solve this issue. I cannot declare lxml=2.3 anymore, because only lxml 3.0+ supports Python 3. If we want to keep supporting Windows, someone must sign up to create Windows binaries. Regards, Stephan -- Entrepreneur and Software Geek Google me. "Zope Stephan Richter" ___ 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 - FAILED: 21, OK: 15, UNKNOWN: 1
On Wednesday, February 27, 2013 08:55:21 AM Marius Gedminas wrote: > > [6]winbot / z3c.form_py_265_32 > > [7]winbot / z3c.form_py_265_32 > > [8]winbot / z3c.formui_py_265_32 > > Same: failure to build lxml. z3c.form used to pin lxml 2.3, which I did not even see on PyPI anymore. Unfortuantely the bot building Windows binaries is not running anymore. Regards, Stephan -- Entrepreneur and Software Geek Google me. "Zope Stephan Richter" ___ 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 - FAILED: 21, OK: 19
On Tuesday, February 26, 2013 01:00:39 PM Tres Seaver wrote: > > * ZODB 4.0.0 (I am currently using an sdist of the py3 branch.) > > AFAIK, the remaining test failures on Py33 are largely spurious (doctest > repr issues, or else are pending the fork to use 'zodbpickle'. So the state here is: - We need to include zodbpickle in order to make pickle loading backward- compatible with Python 2. Without this you cannot take you Python 2 ZODB and open it in Python 3. (zodbpickle's docs provide details.) - Make "noload()" work in zodbpickle. I ported the code from cPickle, but it does not work. This prohibits GC without the ability to load the objects. "noload()" also needs a Python implementation and tests. I only know that "noload()" is not working because of a failure in the ZODB tests. - Python 2 and 3 pickles have different sizes due to some added padding and some other reasons Marius has reported. Using zodbpickle will not fix that, since it is a fork of _pickle.c from Python 3.3. We simply should fix the tests to live with that fact. That's pretty much it. Regards, Stephan -- Entrepreneur and Software Geek Google me. "Zope Stephan Richter" ___ 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] ZTK 2.0 process
On Tuesday, February 26, 2013 05:04:26 PM Hanno Schlichting wrote:
> Contrary to wait I said before I'd be willing to work on a ZTK 2.0
> release (knowing the tools and procedure).
Could you outline what the first step would be to create an alpha release list
for 2.0? We could manually include an sdist of the ZODB 4 py3 branch to make
the tests pass under Python 3.
Is anyone here willing to start a buildbot using Python 3.3 to test the ZTK?
> My goals for a 2.0 release would be (comparing to
> http://docs.zope.org/zopetoolkit/releases/overview-1.1.html):
Great!
> - Drop support for Python 2.5 (ZTK 1.1 still supports that)
Yeah, none of the 4.0 packages do.
> - Add support for Python 3.x (either 3.3 or 3.2 and 3.3)
Since I was unwilling to change all u'...' to u('...'), most packages
currently only have Python 3.3 support. By the time ZTK 2.0 will be released,
I think most people will have switched to Python 3.3.
> - Drop all zope.app packages from the KGS (most were deprecated in ZTK 1.1)
Some of the zope.app packages (the ones not deprecated) should stay or simply
be renamed to not being called zope.app.*.
> - Update to buildout 2
Yep, already done for all 4.0 packages.
> - Update to ZODB 4
This will be a requirement for Py3 support or is anyone willing to backport
all the changes to ZODB3? :-)
We will also need to add a few packages, such as BTrees, persistent,
transaction, etc. and deprecate/remove some others like zope.broken,
zope.untrustedpython, zope.fixers, and zope.apidoc.
Regards,
Stephan
--
Entrepreneur and Software Geek
Google me. "Zope Stephan Richter"
___
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 - FAILED: 21, OK: 19
On Tuesday, February 26, 2013 02:41:02 PM Marius Gedminas wrote: > This error is caused by zope.publisher 4.0.0a1: > > bin/buildout -n buildout:prefer-final=false buildout:versions=versions \ >versions:zope.publisher='<4.0.0a1' \ >versions:zope.session='<4.0.0a1' && bin/test -pvc > > makes the test pass, while > > bin/buildout -n buildout:prefer-final=false buildout:versions=versions \ >versions:zope.publisher='4.0.0a1' \ >versions:zope.session='<4.0.0a1' && bin/test -pvc This brings up a bigger question: Even though, most ported packages are fully Python 3 compatible, they might depend on packages that are not ready to get a final release. Those two are: * zope.security 4.0.0 (pending PyPy support from Tres) * ZODB 4.0.0 (I am currently using an sdist of the py3 branch.) Any package that depends directly or indirectly on those two packages has an alpha release right now. Strictly speaking this is not necessary for any package not depending on ZODB (ZODB is special because the dep changes from ZODB3 to ZODB). If it is okay with everyone, we could change the releases to their final version numbers with the understanding that Python 3 support will not be available until all dependencies have their final release. Python 2 should work just fine once we get the trunk builds back to green. Regards, Stephan -- Entrepreneur and Software Geek Google me. "Zope Stephan Richter" ___ 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] ZTK 2.0 process
Hi everyone, what is the process to start working on ZTK 2.0? We are about 5-6 packages away from porting ZTK to Python 3 and I would like to start working on a new release. Regards, Stephan -- Entrepreneur and Software Geek Google me. "Zope Stephan Richter" ___ 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.security on github?
On Monday, February 11, 2013 03:37:17 PM Jim Fulton wrote: > > It seems to be readonly already, so I cannot remove the files. > > Sorry. Fixed. Can you try again please? All done. Regards, Stephan -- Entrepreneur and Software Geek Google me. "Zope Stephan Richter" ___ 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.security on github?
On Monday, February 11, 2013 03:19:54 PM Jim Fulton wrote: > > 1. Can we delete the contents of zope.security on svn.zope.org? > > Please remove the contents of trunk and add a MOVED_TO_GITHUB file in > trunk and in the project root with the git repo url. > > When that's done, I'll make the project read only. It seems to be readonly already, so I cannot remove the files. Regards, Stephan -- Entrepreneur and Software Geek Google me. "Zope Stephan Richter" ___ 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.security on github?
Hi everyone, I was just about to start porting zope.security using the SVN version, when I noticed it is already on Github and Tres has even worked on it today. So 2 things: 1. Can we delete the contents of zope.security on svn.zope.org? 2. Can we enable checkin messages for all moved projects? (I have not seen any checkin messages from Tres, for example.) Regards, Stephan -- Entrepreneur and Software Geek Google me. "Zope Stephan Richter" ___ 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] z3c.datagenerator Github repos needed
Hi everyone, could I have a Github repository for z3c.datagenerator please? I will also need the secret authors.txt file. Also, could I receive the ability to create repositories? Regards, Stephan -- Entrepreneur and Software Geek Google me. "Zope Stephan Richter" ___ 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] Building/Testing persistent package with tox
On Friday, January 11, 2013 11:00:47 AM Jim Fulton wrote: > The project needs to be updated with a manifest that causes .txt files > to be included in builds. (Look at zc.buildout for an example.) I > planned to do this, but hadn't gotten to it yet. I can probably do > that this weekend. Okay, that makes sense. I was wondering about the manifest already, but I was not sure whether another mechanism was involved. BTW, the current bootstrap.py file does not work with Python 3. Are we not going to support buildout with Python 3 or what's the goal/story here? Regards, Stephan -- Entrepreneur and Software Geek Google me. "Zope Stephan Richter" ___ 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] Becoming a "zopefoundation" member on GitHub
Hi everyone, what are the necessary steps to become a Zope Foundation organization member on GitHub? I would like to try moving a small product there to test the migration. Regards, Stephan -- Entrepreneur and Software Geek Google me. "Zope Stephan Richter" ___ 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] Building/Testing persistent package with tox
Hi guys, I have just tried to build/test persistent with tox and it fails with the following error message:: IOError: [Errno 2] No such file or directory: '/tmp/pip-u7jE1n- build/CHANGES.txt' Complete output from command python setup.py egg_info: Traceback (most recent call last): File "", line 16, in File "/tmp/pip-u7jE1n-build/setup.py", line 29, in open(os.path.join(here, 'CHANGES.txt')).read()) IOError: [Errno 2] No such file or directory: '/tmp/pip-u7jE1n- build/CHANGES.txt This is indeed correct, since the ZIP package archive created by tox in ./.tox/dist does not include any txt files. I use the following command to run tox: $ tox -e py27,py32 How do others run tox? Regards, Stephan -- Entrepreneur and Software Geek Google me. "Zope Stephan Richter" ___ 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 SVN Authorization issue
Hi everyone, for some strange reason I cannot check in any changes to the cipher.configstore package. However, I was able to check out the code. I am also able to commit to z3c.form. So it does not seem to be an SSH key issue. Any ideas? Regards, Stephan -- Entrepreneur and Software Geek Google me. "Zope Stephan Richter" ___ 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] transaction pkg py3 / doctests
On Sunday, September 25, 2011, Chris McDonough wrote: > Anyway, it all seems to work given those limitations, but I'm having > trouble making the doctests pass on Python 3. Are there any doctest > ninjas willing to have a look? Looks like you want renormalizers. Unfortunately, they are a zope.testing feature. :-( Any thoughts on how renormalizers and a few other features could be released separately? Regards, Stephan -- Entrepreneur and Software Geek Google me. "Zope Stephan Richter" ___ 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.interface versions, ZTK 1.0 and later
On Friday, August 12, 2011, Tres Seaver wrote: > Thoughts? +1. Sounds like a good plan. Regards, Stephan -- Entrepreneur and Software Geek Google me. "Zope Stephan Richter" ___ 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] Anyone want to do Google Summer of code mentoring for PSF?
On Tuesday, April 05, 2011, Lennart Regebro wrote: > On Tue, Apr 5, 2011 at 11:57, Lennart Regebro wrote: > > On Tue, Apr 5, 2011 at 07:56, Chris McDonough wrote: > >> Did this particular effort get to the place where there are students and > >> mentors lined up to do ZTK porting? > > > > No, it got to the pace where I'm supposed to set up a team page on a > > Wiki. > > Done: http://wiki.zope.org/gsoc/SummerOfCode2011 I added myself to the wiki, registered at the GSoC page and requested being a mentor for the PSF. Regards, Stephan -- Entrepreneur and Software Geek Google me. "Zope Stephan Richter" ___ 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] CSRF protection for z3c.form
On Monday, April 04, 2011, Laurence Rowe wrote: > The authenticator is described on > http://pypi.python.org/pypi/plone.protect, but basically it adds an > HMAC-SHA signed token into the form submission. By validating this you > know that the submission came from a form that your site rendered, > rather than an opportunistic 'drive-by' attack from another site. So why don't we make this a built-in feature then? The token manager (I think you call it the authenticator) needs to be smart, since it needs to deal with stale tokens and similar issues, but otherwise we could just add an authentication mechanism into z3c.form. Mmh, if the token gets stored in the session variable, then we do not even have to worry about token management, since the session container has already that logic. I have a feeling I am missing a level of complexity here... > I'm happy to go with (3). I assume it is not common for z3c.form users > to have non-button actions or customize the ButtonActionHandler? Not in my experience. Regards, Stephan -- Entrepreneur and Software Geek Google me. "Zope Stephan Richter" ___ 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] CSRF protection for z3c.form
On Monday, April 04, 2011, Laurence Rowe wrote: > I'd be interested to know how other z3c.form users approach CSRF protection > and what approach they would recommend. Hi Lawrence, I am okay with (1), but find (3) ore attractive. Since I am not familiar with the token solution to avoid CSRF attacks, can you briefly describe the sequence that is used to avoid those requests? Maybe we can some up with a tightly integrated solution. I have no problem with modifying z3c.form to support such a feature. Regards, Stephan -- Entrepreneur and Software Geek Google me. "Zope Stephan Richter" ___ 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] Test fixture concepts
On Tuesday, March 29, 2011, Jim Fulton wrote: > > so I may forgo them. > > Which is a mistake. You should create separate tests. I typically put > large tests, dealing with main use cases where there is a definite > flow of activity in '.test' files. I do these in separate files > because they're easier to write that way. I use a '.test' suffix to > avoid the pretense that these are documentation. I put edge-case > tests in small docstrings in testing modules. I'm not really > religious about using doctests for this, but I find small edge-case > doctests easier to read than traditional unit tests. It's possible > that I'd like py.test tests as much. Yeah, Marius led me recently to that path too. Write a narrative in text files and use doc strings of functions to do edge cases (or when you don't have time for the narrative). I am getting used to it. I still much prefer the sort of output comparison that doctests/manuel gives me over the assertion language that unittest.TestCase requires. Regards, Stephan -- Entrepreneur and Software Geek Google me. "Zope Stephan Richter" ___ 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: 73 OK, 12 Failed, 4 Unknown
On Friday, March 25, 2011, Hanno Schlichting wrote: > May I suggest you just switch to using to coverage by Ned Batchelder > instead [1]? I like the new coverage package too, but the HTML output is not as nice, so I always find myself going back to the old version. I already prodded Marius about making z3c.coverage work with Ned's latest version. :-) Regards, Stephan -- Entrepreneur and Software Geek Google me. "Zope Stephan Richter" ___ 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] Non-ZCML config for ZCA. (Was: Anyone want to do Google Summer of code mentoring for PSF?)
On Monday, March 21, 2011, Tres Seaver wrote: > FWIW, I just added 'queryAdapterFactory' and 'queryMultiAdapterFactory' > APIs to zope.component on a branch: > > http://svn.zope.org/zope.component/branches/tseaver-queryAdapterFactory/ Looks good to me. Incidentally, I was just needing this today and implemented it using sm.adapters.lookup1. Regards, Stephan -- Entrepreneur and Software Geek Google me. "Zope Stephan Richter" ___ 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] Anyone want to do Google Summer of code mentoring for PSF?
On Monday, March 21, 2011, Lennart Regebro wrote: > > So I'll sign up as a Zope team member. > > Cool. But it turns out we need three to make a team (see > https://spreadsheets.google.com/viewform?formkey=dHh3WFNGYzkyWWE0ZjM1eFFoUU > VGWmc6MQ), and we only really have one. :-) I guess I could take a bullet > for the team too, but that still makes only two. Maybe next year. :-) Jim said he would be willing to mentor someone for the right project. That would make us three. Regards, Stephan -- Entrepreneur and Software Geek Google me. "Zope Stephan Richter" ___ 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] Anyone want to do Google Summer of code mentoring for PSF?
On Saturday, March 19, 2011, Lennart Regebro wrote: > Getting ZCA/ZTK to run on PyPy is probably easier, and actually more > useful. Maybe someone would want to mentor that? While I would mentor someone wanting to do such a project, I would be much more interested in seeing a working WebOb to zope.publisher bridge. I know Jim(?) has done some initial work on that. I think it would make an interesting PSF project, since it encourages more reusability across the Python Web dev community. So I'll sign up as a Zope team member. Regards, Stephan -- Entrepreneur and Software Geek Google me. "Zope Stephan Richter" ___ 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: 71 OK, 16 Failed
On Monday, February 28, 2011, Tres Seaver wrote: > I also suggest dropping the test reports for the z3c.* packages: they > have been broken since the day they were added, AFAICT, which is a > strong signal that they are not being maintained. The problem is merely that lxml cannot be installed. This is more a winbot setup problem than a package one. And the reason lxml cannot be built is because libxml is missing. This is really strange, since there are binaries available for lxml-2.3 for Python 2.6. http://pypi.python.org/pypi/lxml/2.3 Does anyone with Windows Foo have any idea? Regards, Stephan -- Entrepreneur and Software Geek Google me. "Zope Stephan Richter" ___ 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] z3c.formjs widgetselector customization
On Tuesday, February 15, 2011, Simon Elbaz wrote: > If it is a good idea, how could I apply it to svn repository ? You can become a committer and check it into the Zope SVN repository. (I can be your reference.) Feel free to make any changes to z3c.formjs you like. I can also aid you at making a release later. Regards, Stephan -- Entrepreneur and Software Geek Google me. "Zope Stephan Richter" ___ 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.testbrowser and WebTest (round 2)
On Tuesday, February 01, 2011, Wolfgang Schnerring wrote: > But I feel the important point about this regarding compatibility is not > the underlying technology, but the API, i. e. that > - zope.testbrowser.wsgi.Browser is a Testbrowser > - zope.testbrowser.wsgi.Layer with a method make_wsgi_app is there to > facilitate the test setup. > > I think as long as we preserve this API (which seems sound to me, but of > course I'm biased ;-), we're free to change stuff under the hood. +1 Regards, Stephan -- Entrepreneur and Software Geek Google me. "Zope Stephan Richter" ___ 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: 40 OK, 4 Failed
On Tuesday, December 21, 2010, Wichert Akkerman wrote: > I added three tickets on launchpad in October :). A big problem for me > appears to be that z3c.rml implements an older version of RML, so a lot > of the directives in the RML documentation fail (at least of the few I > wanted to use). And since z3c.rml silently ignores unsupported tags it > took me quite some time to determine that the problem was not in my RML. Oh yeah, I remember those reports. Let me see whether I can find some time to update to the latest ReportLab and throw errors on wrong tags. BTW. I do have a generated DTD that you could use for validation in the mean time. Regards, Stephan -- Entrepreneur and Software Geek Google me. "Zope Stephan Richter" ___ 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: 40 OK, 4 Failed
On Tuesday, December 21, 2010, Wichert Akkerman wrote: > > I am frequently getting bug reports from users. And it had 742 downloads > > since July. That is not a huge number, but more than other packages that > > are not part of the standard Plone/Zope 2/Bluebream dependency tree. > > If only those bugreports would get some response :) You having an outstanding one to me? :-) I have addressed all the ones in my inbox in July. :-) I could find some time in the next days to do another round of bug fixing. Regards, Stephan -- Entrepreneur and Software Geek Google me. "Zope Stephan Richter" ___ 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] One z3c.rml test failure on Linux -- bug in ReportLab?
On Tuesday, December 21, 2010, Marius Gedminas wrote: > So you're saying this is a bug in z3c.rml after all? It ends up not > using separate subprocesses for each test? It runs all tests twice, once with and once without the subprocess version. Regards, Stephan -- Entrepreneur and Software Geek Google me. "Zope Stephan Richter" ___ 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: 40 OK, 4 Failed
On Tuesday, December 21, 2010, Tres Seaver wrote: > I didn't look at the RML failures. I'm not even sure we should be > running them, at least not every night, as I doubt the package is at all > widely used (but I'm willing to be shouted down ;). I am frequently getting bug reports from users. And it had 742 downloads since July. That is not a huge number, but more than other packages that are not part of the standard Plone/Zope 2/Bluebream dependency tree. Regards, Stephan -- Entrepreneur and Software Geek Google me. "Zope Stephan Richter" ___ 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] One z3c.rml test failure on Linux -- bug in ReportLab?
On Monday, December 20, 2010, Marius Gedminas wrote: > ve poked at this test failure a bit, and I suspect a bug in ReportLab. > It appears that creating two documents that use PDF forms will clobber > over a global object's -- reportlab.pdfbase.pdfform.GLOBALRESOURCES -- > __InternalName__ attribute during the creation of the first document, > and that will prevent anyone from using AcroForm.format() on any other > document in that process. > > The next step would be to make a smaller reproducible example and submit > it to the ReportLab folks for consideration. > > I'm not familiar with z3c.rml nor with ReportLab's form code, so I'd > appreciate if people who wrote the test could help with the smaller > reproducible example. That's not a bug, but a well-known issue with ReportLab. Once you generated one document with ReportLab, you are not guaranteed a clean state, since ReportLab uses module-global variables to keep track of state. This is the reason, Roger implemented running the renderer in a sub-process and all the tests are run twice. Regards, Stephan -- Entrepreneur and Software Geek Google me. "Zope Stephan Richter" ___ 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] Context priority as an alternative to configuration directive overrides
On Thursday, December 02, 2010, Malthe Borch wrote: > As far as I understand, for a ZCML include override to work properly, > you need to carefully make sure that your includes are in the exact > right order and on the same level. In a system where two packages are > trying to override the same component (should arguably never be the > csae, but it is frequently), it can be difficult to get it right. This explanation helped me to understand where you come from. I think I would be okay with the priority feature, but could we maybe limit it to the element? Since you can use this element anywhere and it can be nested, it should work well. Regards, Stephan -- Entrepreneur and Software Geek Google me. "Zope Stephan Richter" ___ 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] Fwd: [Checkins] SVN: zope.component/branches/adamg-fix-getSiteManager/ - Fix _api.getSiteManager in the way that it returns now
On Wednesday, October 27, 2010, Adam GROSZER wrote: > This change is needed because z3c.baseregistry does not work > otherwise. It registers everything in the global registry. > This is a blocker for us to move to ZTK 1.0. > > Raise your hands until 28th October midnight UTC. > If noone objects until then, I'll merge to trunk and make a new > release. I am going to need z3c.baseregistry in the next few days as well and we are on Bluebream 1.0b5, so I am all for getting this in ASAP. :-) Regards, Stephan -- Entrepreneur and Software Geek Google me. "Zope Stephan Richter" ___ 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] Python 2.4 Support
On Friday, September 17, 2010, Tres Seaver wrote: > > i have a little question. > > Is there a chance to not drop Python2.4 Support for ZTK1.1? > > I ask because Redhat Enterprise Linux 5 is shipped with Python2.4, > > and should have been supported for some years from now. > > At this point, the burden of keeping 2.4 compatibility is too high for > ongoing development. I agree. We have to support Python 2.5, 2.6 and 2.7 already. There is also a desire to use newer releases, since they get us closer to Python 3. Regards, Stephan -- Entrepreneur and Software Geek Google me. "Zope Stephan Richter" ___ 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] buidout 1.5
On Friday, September 17, 2010, Hanno Schlichting wrote: > Right now I just want to get a stable ZTK 1.0 out and not add any new > features to it. We have the trunk open for development. +1 zc.buildout 1.5 caused great pain here at work! I have worked with Gary to rectify the problems, but I would still prefer no feature release changes in the ZTK now. Regards, Stephan -- Entrepreneur and Software Geek Google me. "Zope Stephan Richter" ___ 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.app.appsetup and RootErrorReportingUtility
On Monday, August 30, 2010, Adam GROSZER wrote: > Anyone objects a change to "copy_to_zlog=True" as default? +1 Regards, Stephan -- Entrepreneur and Software Geek Google me. "Zope Stephan Richter" ___ 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] RFC: ETag support for zope.browserresource
On Monday, August 09, 2010, Marius Gedminas wrote: > Does anybody have any comments/objections? If not, I'd like to merge > this to trunk and release zope.browserresource 3.11.0. Looks good to me. Regards, Stephan -- Entrepreneur and Software Geek Google me. "Zope Stephan Richter" ___ 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] Retire zope3-checkins list
On Monday, August 09, 2010, Jens Vagelpohl wrote: > - Zope3 > - zope.testing > - zope.formlib > - ldapauth > - messageboard > - zdaemon > > I can remove those hooks if so desired. No mail gets lost, all checkins > also send email to the general checkins list[1]. +1 Regards, Stephan -- Entrepreneur and Software Geek Google me. "Zope Stephan Richter" ___ 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] docs.zope.org automation
On Tuesday, August 03, 2010, Jens Vagelpohl wrote: > This is now implemented as fallback, take another look at the package > listing, like the ZTK list[1]. I had to resort to executing "setup.py > --long-description" in a subprocess, unfortunately. Never found out how > to do that programmatically. Yeah, this looks good. Regards, Stephan -- Entrepreneur and Software Geek Google me. "Zope Stephan Richter" ___ 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] docs.zope.org automation
On Monday, August 02, 2010, Jens Vagelpohl wrote: > OK, I'll see what I can do with that. I'll probably end up using the > long description as last fallback. So you will see every package linked > to *something*, even if it's just a page with a few words on it. Just FYI: If there is no long description (which is very unlikely), then the string "UNKNOWN" is returned from the --long-description call. Regards, Stephan -- Entrepreneur and Software Geek Google me. "Zope Stephan Richter" ___ 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] docs.zope.org automation
On Monday, August 02, 2010, Stephan Richter wrote: > py26 setup.py --long-description | rst2html > > rst2html have many options that allow you to modify the style, including > the ability to specify a stylesheet. Oh, btw, this is also the method that we used to verify that the long descriptions are proper ReST. ;-) Regards, Stephan -- Entrepreneur and Software Geek Google me. "Zope Stephan Richter" ___ 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] docs.zope.org automation
On Monday, August 02, 2010, Jens Vagelpohl wrote: > Thanks for the hint, I'll try that. Can you give me a sample package > where the long description is supposed to be the main documentation? And > what's the output from that? If it's ReST I'd have to find a way to > convert it to HTML on the fly... zope.security (http://pypi.python.org/pypi/zope.security) Once you have docutils installed, you can do: py26 setup.py --long-description | rst2html rst2html have many options that allow you to modify the style, including the ability to specify a stylesheet. Regards, Stephan -- Entrepreneur and Software Geek Google me. "Zope Stephan Richter" ___ 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] docs.zope.org automation
On Monday, August 02, 2010, Jens Vagelpohl wrote: > 'll have to look at that. Currently, the documentation builder does not > do any introspection on the package itself, mostly because I do not want > to fully install the package and pull in all dependencies. Maybe there's > a simple way that does not require full installation. I agree. This does not build the package: python setup.py --long-description Regards, Stephan -- Entrepreneur and Software Geek Google me. "Zope Stephan Richter" ___ 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] docs.zope.org automation
On Saturday, July 31, 2010, Jens Vagelpohl wrote: > Currently the buildout can recognize the standard Sphinx documentation > layout with a folder named "doc" or "docs" in the package root and a > Sphinx configuration and content therein. The buildout can also use a > kludge and pull in content that is documented using > "z3c.recipe.sphinxdoc" maintained in a separate buildout, but I'm hoping > those project authors would consider using the standard layout as > exemplified by e.g. zope.event[2] and championed by e.g. Tres, Christian > Theune, and several others (including me). We have put a lot of energy into putting the full documentation of packages into the package's long description and most packages have this layout (I know, because I did it for most. ;-) So it might be good to use the long description of the package, if the other two methods fail. This would turn on documentation for a lot of packages and we can move them over slowly. But otherwise, it is great to see such great progress on docs.zope.org! Regards, Stephan -- Entrepreneur and Software Geek Google me. "Zope Stephan Richter" ___ 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] Class advisors in Python 3
On Friday, July 30, 2010, Hanno Schlichting wrote: > zope.interface contains 2to3 fixers to rewrite them to a class > decorator syntax IIRC. Wow, that's really nice. BTW, does Python 2.7 support class decorators already? If so, we could slowly migrate code to that syntax without having to go Py3 all the way. Regards, Stephan -- Entrepreneur and Software Geek Google me. "Zope Stephan Richter" ___ 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.testing / zope.testrunner path forward:
On Wednesday, July 21, 2010, Lennart Regebro wrote: > Nobody said "YES!" and since it actually requires that zope.testing > depends on zope.testrunner to be pracically useful, I think we'll skip > it. I think nobody cares because everyone uses the test runner recipe. As long as that recipe works, we are good. :-) Regards, Stephan -- Entrepreneur and Software Geek Google me. "Zope Stephan Richter" ___ 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] New releases of Zope2 (incl. a potential security fix)
On Tuesday, July 13, 2010, Hanno Schlichting wrote: > In other news Zope 2.13.0a2 now officially supports Python 2.7. How can Zope 2.13 support Python 2.7, when the ZTK 1.0 does not? Regards, Stephan -- Entrepreneur and Software Geek Google me. "Zope Stephan Richter" ___ 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] Can ZTK 1.0 support Python 2.7?
On Tuesday, July 13, 2010, Hanno Schlichting wrote: > What do others think about this? Based on what you wrote, I think this is the right solution. Python 2.4 is clearly important to the Zope 2 / Plone world. Regards, Stephan -- Entrepreneur and Software Geek Google me. "Zope Stephan Richter" ___ 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] Including Paste into the ZTK version list?
On Friday, July 09, 2010, Hanno Schlichting wrote: > I noticed that all three frameworks (BB, Grok, Zope2) have version > pins for Paste, PasteDeploy and PasteScript. Does anyone object to > including them into the ztk-versions.cfg under dependencies? +1 Regards, Stephan -- Entrepreneur and Software Geek Google me. "Zope Stephan Richter" ___ 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] audit of RestrictedPython for Python 2.7
On Thursday, July 08, 2010, David Glick wrote: > I am done (as far as I can tell) evaluating RestrictedPython to see if > changes are needed to support Python 2.7. This is the first time I have > done this, so would appreciate if someone else can look over my work to > make sure I'm not missing something important. I'll describe my process > and findings below. This is a good analysis. I looked over your checkins as they came in and they look good. I am glad you caught the import problem. Regards, Stephan -- Entrepreneur and Software Geek Google me. "Zope Stephan Richter" ___ 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] New release of z3c.form
On Thursday, July 01, 2010, Godefroid Chapelle wrote: > I found http://docs.zope.org/z3c.form/ > > Last updated Nov 08,2009 Version 1.8.2dev. > > What is the process to get the latest version published ? Not sure. I think Paul Carduner did that. Since z3c.form is Sphinx-enabled, I wonder whether we could stick the docs into http://packages.python.org/z3c.form. Manuel does this already: http://packages.python.org/manuel/ Regards, Stephan -- Entrepreneur and Software Geek Google me. "Zope Stephan Richter" ___ 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 2.13 - next steps
On Sunday, June 13, 2010, Hanno Schlichting wrote: > On Sat, Jun 12, 2010 at 9:29 PM, David Glick wrote: > > Has the process of reviewing RestrictedPython against a new Python > > release been documented anywhere? > > Not that I know of. Stephan Richter and Sidnei da Silva were the last > to do these reviews, maybe they know. There is no process really. You have to go through the changes in Python 2.7 and detect API changes in the C code to see whether any op-codes changed or a new API opens up some unwanted access. Regards, Stephan -- Entrepreneur and Software Geek Google me. "Zope Stephan Richter" ___ 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.testrunner 4.0.0b2 problem
On Thursday, June 10, 2010, Hanno Schlichting wrote: > Doing so a in minor release looks bad to me. The release should be a > clear 2.0 and since it depends on a non-final version itself, it > should probably be a beta release on its own. We are not really changing the API in a BBB incompatible way. We simply shuffled code around. We did that all the time and never increased the major version number. > I think rereleasing zc.recipe.testrunner without the zope.testrunner > dependency as a 1.3.1 would be in order. And then releasing the > current 1.3.0 code as a new 2.0b1. I think that would be a bit harsh and not fix the Zope 2 problem, if no versions are pinned, since even 2.0b1 will be picked up as latest. Regards, Stephan -- Entrepreneur and Software Geek Google me. "Zope Stephan Richter" ___ 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.testrunner 4.0.0b2 problem
On Thursday, June 10, 2010, Andreas Jung wrote: > No idea (and I did not investigate it). I had two reports form > co-workers with buildouts breaking suddenly and I encountered a similar > issue with two Plone buildouts. Could you check which zc.recipe.testrunner version is picked up? BTW, pinning zc.recipe.testrunner to 1.2.0 will do the trick. Regards, Stephan -- Entrepreneur and Software Geek Google me. "Zope Stephan Richter" ___ 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.testrunner 4.0.0b2 problem
On Thursday, June 10, 2010, Andreas Jung wrote: > Could someone please remove this release or fix it? > This issue is breaking almost every existing Zope 2 buildout. How can it? Are you not pinning the version of zc.recipe.testrunner and zope.testing? I assume the breakage occurs, since I released zc.recipe.testrunner last night that uses zope.testrunner instead of zope.testing. Regards, Stephan -- Entrepreneur and Software Geek Google me. "Zope Stephan Richter" ___ 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] pypi access for zope.app.authentication and zope.password
On Wednesday, May 26, 2010, Jan-Wijbrand Kolman wrote: > Could someone grant me pypi access to zope.app.authentication and > zope.password? Done. Regards, Stephan -- Entrepreneur and Software Geek Google me. "Zope Stephan Richter" ___ 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] version pinning on tags
On Thursday 29 April 2010, Baiju M wrote: > > +1 to use a KGS. ZTK or BB depending on what the dependencies are. > > Since normally we don't pin versions in trunk, I guess we need to > do the pinning in maintenance branches. Otherwise we can > keep the version pinning in trunk, but comment the "versions" option. > Then, just before going for release, uncomment it. > This will become one more step in creating releases: > http://docs.zope.org/zopetoolkit/process/releasing-software.html Why not leave it always pinned? This way the pinning gets transferred to the branch/tag automatically. Regards, Stephan -- Entrepreneur and Software Geek Google me. "Zope Stephan Richter" ___ 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] windows binaries
On Thursday 29 April 2010, Baiju M wrote: > > I did a few releases just using mingw32. I think it is the best we can do > > for now that scales. As for Python versions, you simply have to > > installthem all and go through the dance. > > Does mingw32 works for 64 bit also ? If you can isntall it on 64bit, it should be able to compile to it as well. Regards, Stephan -- Entrepreneur and Software Geek Google me. "Zope Stephan Richter" ___ 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] windows binaries
On Wednesday 28 April 2010, Adam GROSZER wrote: > How do you used to build binaries for windowze? > I mean which compilers do you use? mingw32? MS? > Ohhh and don't forget win64 ;-) > and various python version, like from 2.4 up to 3.1. I did a few releases just using mingw32. I think it is the best we can do for now that scales. As for Python versions, you simply have to installthem all and go through the dance. Regards, Stephan -- Entrepreneur and Software Geek Google me. "Zope Stephan Richter" ___ 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] version pinning on tags
On Thursday 29 April 2010, Adam GROSZER wrote: > I'd say we should nail the package versions on (at least) tags. > Either to a KGS, or drop a versions.cfg into the package. > The recipe buildout.dumppickedversions would be handy. +1 to use a KGS. ZTK or BB depending on what the dependencies are. Regards, Stephan -- Entrepreneur and Software Geek Google me. "Zope Stephan Richter" ___ 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] releasing KGS
On Wednesday 28 April 2010, Adam GROSZER wrote: > Looking at > svn://svn.zope.org/repos/main/zope.release/branches/3.4/README.txt At 6.) > you do a /bin/upload, it's all I need to do the release? > How does the http://download.zope.org/zope3.4/3.4.0/versions.cfg get > created? There are some scripts in bin, but I'd rather not make a > mistake. I think upload does everything. The good news is it only copies files, which you can easily remove if you mess up. > bin/upload does somewhere an scp to download.zope.org, where I don't > have permission. Whom to ask for permission or to do the upload? I think your best bet would be a mail to the foundation-info list. Regards, Stephan -- Entrepreneur and Software Geek Google me. "Zope Stephan Richter" ___ 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] pypi access to zope.browserresource, zope.browsermenu
On Monday 26 April 2010, Martijn Faassen wrote: > Could someone give me and Hanno pypi access to zope.browserresource and > zope.browsermenu? I am in the process to give you access to all the packages that I am an owner of (now that PyPI is fixed again. :-) Let me know if hannosch wants the same. Regards, Stephan -- Entrepreneur and Software Geek Google me. "Zope Stephan Richter" ___ 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] pypi access to zope.browserresource, zope.browsermenu
On Monday 26 April 2010, Martijn Faassen wrote: > Could someone give me and Hanno pypi access to zope.browserresource and > zope.browsermenu? Done. Regards, Stephan -- Entrepreneur and Software Geek Google me. "Zope Stephan Richter" ___ 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 )
