Re: [Zope-dev] How to test changes to ZTK packages?
On Tue, 2009-06-30 at 14:35 -0400, Tres Seaver wrote: > While I know that Mac people often report problems building lxml, I > never have issues building lxml on Linux: the '--static-deps' option is > a sufficient workaround for variants with too-old versions of libxml2 / > libxslt. I do not know what platform you are running but I have had my share of frustrations with lxml on Fedora and Ubuntu on x86_64. --Tim -- Timothy Cook, MSc Health Informatics Research & Development Services LinkedIn Profile:http://www.linkedin.com/in/timothywaynecook Skype ID == timothy.cook ** *You may get my Public GPG key from popular keyservers or * *from this link http://timothywayne.cook.googlepages.com/home* ** signature.asc Description: This is a digitally signed message part ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] ComponentLookupError
I'm getting this traceback: == serving on http://127.0.0.1:8080 2009-05-17 11:56:42,332 ERROR [SiteError] http://localhost:8080 Traceback (most recent call last): File "/home/tim/.buildout/eggs/zope.publisher-3.7.0-py2.5.egg/zope/publisher/publish.py", line 127, in publish publication.beforeTraversal(request) File "/home/tim/.buildout/eggs/zope.app.publication-3.5.3-py2.5.egg/zope/app/publication/zopepublication.py", line 85, in beforeTraversal principal = auth.authenticate(request) File "/home/tim/.buildout/eggs/zope.principalregistry-3.7.0-py2.5.egg/zope/principalregistry/principalregistry.py", line 58, in authenticate if p.validate(password): File "/home/tim/.buildout/eggs/zope.principalregistry-3.7.0-py2.5.egg/zope/principalregistry/principalregistry.py", line 190, in validate pwManager = self.__getPasswordManager() File "/home/tim/.buildout/eggs/zope.principalregistry-3.7.0-py2.5.egg/zope/principalregistry/principalregistry.py", line 184, in __getPasswordManager return getUtility(IPasswordManager, self.__pwManagerName) File "/home/tim/.buildout/eggs/zope.component-3.6.0-py2.5.egg/zope/component/_api.py", line 171, in getUtility raise ComponentLookupError(interface, name) ComponentLookupError: (, u'SHA1') Though everything seems "to me" to be okay. This was originally a grokproject based application and uses grok 1.0a3 but I have been incrementally/painfully changing the versions of components to get it to run with ZODB3.9.0b1 The server starts but when I try to access http://localhost:8080 I get the above error. The principal in site.zcml looks like this: Any ideas where to start on this? Thanks, Tim -- Timothy Cook, MSc Health Informatics Research & Development Services LinkedIn Profile:http://www.linkedin.com/in/timothywaynecook Skype ID == timothy.cook ** *You may get my Public GPG key from popular keyservers or * *from this link http://timothywayne.cook.googlepages.com/home* ** signature.asc Description: This is a digitally signed message part ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] [Fwd: [Bug 376907] Re: AttributeError: 'str' object has no attribute 'registerSynch']
On Sat, 2009-05-16 at 08:20 +0200, Michael Howitz wrote: > You use a really ancient version of zope.app.publication. This bug was > fixed in version 3.5.0 of zope.app.publication. I think at least this > version is required to be used together with ZODB 3.9. > Thanks for pointing this out Michael. Some updating led to more which led to more ... I didn't realize that Grok was so far behind in so many packages. :-) This is going to take awhile but I WILL HAVE MY ZOBD3.9x and RelStorage! ;-) Cheers, Tim signature.asc Description: This is a digitally signed message part ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] [Fwd: [Bug 376907] Re: AttributeError: 'str' object has no attribute 'registerSynch']
I forgot to explicitly ask the question. Where do I file this bug report? Thanks, Tim On Fri, 2009-05-15 at 10:24 -0300, Tim Cook wrote: > This is a bug I filed against ZODB3.9.0b1 > As you can see Jim says it is a bug in zope.app.publication but there is > no Launchpad project to forward the bug to for this module. > > The full text of the bug report is below the double lines. > > Thanks, > Tim > > > Forwarded Message > From: Jim Fulton > Reply-to: Bug 376907 <376...@bugs.launchpad.net> > To: timothywayne.c...@gmail.com > Subject: [Bug 376907] Re: AttributeError: 'str' object has no attribute > 'registerSynch' > Date: Fri, 15 May 2009 12:53:47 - > > This is a bug in zope.app.publication. It shouldn't pass a version to > open. > > > ** Changed in: zodb >Status: New => Won't Fix > > == > > ZODB3.9.0b1 - > Linux x86_64 AMD - Grok 10a3. > > Server starts. Creates a new Data.fs, etc. When attempting to open > http://localhost:8080/applications to add my Grok apps I get this error. > > Traceback here: > = > 2009-05-15 08:30:05,890 ERROR [SiteError] http://localhost:8080 > Traceback (most recent call last): > File > "/home/tim/.buildout/eggs/zope.publisher-3.4.6-py2.5.egg/zope/publisher/publish.py", > line 129, in publish > obj = publication.getApplication(request) > File > "/home/tim/.buildout/eggs/grok-1.0a3-py2.5.egg/grok/publication.py", > line 70, in getApplication > result = super(ZopePublicationSansProxy, > self).getApplication(request) > File > "/home/tim/.buildout/eggs/zope.app.publication-3.4.3-py2.5.egg/zope/app/publication/zopepublication.py", > line 150, in getApplication > conn = self.db.open(version) > File > "/home/tim/.buildout/eggs/ZODB3-3.9.0b1-py2.5-linux-x86_64.egg/ZODB/DB.py", > line 759, in open > result.open(transaction_manager) > File > "/home/tim/.buildout/eggs/ZODB3-3.9.0b1-py2.5-linux-x86_64.egg/ZODB/Connection.py", > line 1052, in open > transaction_manager.registerSynch(self) > AttributeError: 'str' object has no attribute 'registerSynch' > === > > -- Timothy Cook, MSc Health Informatics Research & Development Services LinkedIn Profile:http://www.linkedin.com/in/timothywaynecook Skype ID == timothy.cook ** *You may get my Public GPG key from popular keyservers or * *from this link http://timothywayne.cook.googlepages.com/home* ** signature.asc Description: This is a digitally signed message part ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] [Fwd: [Bug 376907] Re: AttributeError: 'str' object has no attribute 'registerSynch']
This is a bug I filed against ZODB3.9.0b1 As you can see Jim says it is a bug in zope.app.publication but there is no Launchpad project to forward the bug to for this module. The full text of the bug report is below the double lines. Thanks, Tim Forwarded Message From: Jim Fulton Reply-to: Bug 376907 <376...@bugs.launchpad.net> To: timothywayne.c...@gmail.com Subject: [Bug 376907] Re: AttributeError: 'str' object has no attribute 'registerSynch' Date: Fri, 15 May 2009 12:53:47 - This is a bug in zope.app.publication. It shouldn't pass a version to open. ** Changed in: zodb Status: New => Won't Fix == ZODB3.9.0b1 - Linux x86_64 AMD - Grok 10a3. Server starts. Creates a new Data.fs, etc. When attempting to open http://localhost:8080/applications to add my Grok apps I get this error. Traceback here: = 2009-05-15 08:30:05,890 ERROR [SiteError] http://localhost:8080 Traceback (most recent call last): File "/home/tim/.buildout/eggs/zope.publisher-3.4.6-py2.5.egg/zope/publisher/publish.py", line 129, in publish obj = publication.getApplication(request) File "/home/tim/.buildout/eggs/grok-1.0a3-py2.5.egg/grok/publication.py", line 70, in getApplication result = super(ZopePublicationSansProxy, self).getApplication(request) File "/home/tim/.buildout/eggs/zope.app.publication-3.4.3-py2.5.egg/zope/app/publication/zopepublication.py", line 150, in getApplication conn = self.db.open(version) File "/home/tim/.buildout/eggs/ZODB3-3.9.0b1-py2.5-linux-x86_64.egg/ZODB/DB.py", line 759, in open result.open(transaction_manager) File "/home/tim/.buildout/eggs/ZODB3-3.9.0b1-py2.5-linux-x86_64.egg/ZODB/Connection.py", line 1052, in open transaction_manager.registerSynch(self) AttributeError: 'str' object has no attribute 'registerSynch' === signature.asc Description: This is a digitally signed message part ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Please use launchpad bugtracking/blueprints more
Good analysis Gary, Though I would tend to see Zope3 as the umbrella and the various projects (components) under it. Is there REALLY too much bad press vs. good press about Zope3? I don't think so. I think inventing a new name ala, Zope Umbrella is a bad thing. Presenting Zope3 as the Zope Component Architecture is not a bad thing. But not consolidating on a specific brand *is* a bad thing. I believe that from an outsiders point of view; keeping the Zope3 moniker ties it to the legacy of Zope.org and Zope Corp. These are not bad things. Explaining that it is now a component architecture is a good thing. In my project, this received a very positive response from Python developers. They liked the ideas of Zope but hated the monolithic structure of Zope2.x I am not a Zope developer, have never contributed a single line of code. I have complained a lot, mostly because I misunderstood Zope. but I can tell you that as a user it is easy to see the power and functionality. Even if I do not yet know how to fully exploit it. Moving away from the name is bad for the FOSS product and bad for the company that started it all. My 2.5 cents, Tim -- Timothy Cook, MSc Health Informatics Research & Development Services LinkedIn Profile:http://www.linkedin.com/in/timothywaynecook Skype ID == timothy.cook ** *You may get my Public GPG key from popular keyservers or * *from this link http://timothywayne.cook.googlepages.com/home* ** ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Please use launchpad bugtracking/blueprints more
On Wed, 2009-03-25 at 19:21 +0100, Martijn Faassen wrote: > Why would the steering group be a project as part of the Zope Framework? > The steering group isn't a project? > > I'm all for setting something up, but I'm still not clear on what you'd > set up. A Zope Framework project group with what inside? > The Steering Committee can be a Team on Launchpad with or without associated source code. I do this with the oship-dev team and it works well. HTH, Tim -- Timothy Cook, MSc Health Informatics Research & Development Services LinkedIn Profile:http://www.linkedin.com/in/timothywaynecook Skype ID == timothy.cook ** *You may get my Public GPG key from popular keyservers or * *from this link http://timothywayne.cook.googlepages.com/home* ** signature.asc Description: This is a digitally signed message part ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] [Zope3-Users] Next Step to Bug Resolution???
Hi Dan, On Sat, 2009-01-17 at 01:28 +0300, Dan Korostelev wrote: > Hi Tim. > > Unfortunately I didn't follow the discussion lately, so may be the > problem is no more, but... There has been a tremendous amount of help from folks like you. However there is still not a solution. I have been asked several times for a 15 minute overview. This is tough given the complexity but allow me to ask the question at a more basic level. I believe it is similar to the way I asked it last year, but here goes. I'm not going to address Field or Object here, just explain the basics. class DataStructure(Persistence): """abstract class""" class ItemStructure(DataStructure): """abstract class""" class ItemList(ItemStructure): u""" Logical list data structure, where each item has a value and can be referred to by a name and a positional index in the list. The list may be empty. """ items = List( value_type=Object(schema=IElement), title=_(u"items"), description=_(u"""Physical representation of the list."""), required=False ) class ItemTable(ItemStructure): u""" Logical relational database style table data structure, in which columns are named and ordered with respect to each other. Implemented using Cluster-per-row encoding. Each row Cluster must have an identical number of Elements, each of which in turn must have identical names and value types in the corresponding postions in each row. Some columns may be designated 'key' columns, containing key data for each row, in the manner of relational tables. This allows row-naming, where each row represents a body site, a blood antigen etc. All values in a column have the same data type. Used to represent any data which is logically a table of values, such as blood pressure, most protocols, many blood tests etc. Not used for time-based data, which should be represented with the temporal class HISTORY.. The table may be empty. """ class ItemSingle(ItemStructure): u""" Logical single value data structure. Used to represent any data which is logically a single value, such as a person's height or weight. """ * There are others and I left out the attributes and methods of these classes; with the exception of ItemList attribute 'items', where it is a zope.schema List but the value types are restricted to the schema described by IElement (also part of openEHR); but I think you get the idea. These classes are used as the base software for all openEHR applications. Of course the classes get more complex and deal directly with healthcare related issues. Now there are thousands of applications that will have data instance with attributes expressed in classes based on the above software that represent single (but complete) clinical concepts. But not all application user interfaces will use all available attributes of the concept. One may use an ItemTable and another an ItemList but they will both be valid in ANY application because the attribute represents a legal instance of ItemStructure. When that data instance is sent from application to another the receiving applications still needs to know the complete semantic context of when that data was collected.Think medico-legal, research and decision support over the lifetimes of patients and populations. So even if the user didn't see all the options in their GUI; it is still all contained in the data that was transfered. So how do I build my schemas so that Zope does the validation of nested schemas and even lets me use standard widgets? I hope this was less than 15 min. For those that want specific examples I can list a few. Cheers, Tim <> signature.asc Description: This is a digitally signed message part ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] BOUNTY! was: Next Step to Bug Resolution???
On Thu, 2008-12-18 at 13:00 -0200, Tim Cook wrote: > This issue is such a huge frustration for me that I am offering a bounty > of 100USD out of my personal pocket to the first person that solves the > issue, gets it committed to a published zope.schema egg and included in > the standard Grok distribution. > > It seems to me to be a reasonable (though not extravagant) amount since > most of the trouble shooting has already been done. Hi All, I want to change the conditions of this offer. Over the past several days there have been too many people to mention help me both publicly and privately with this issue in various ways. Mostly in patience and education. I would like to donate this small amount to the Python Foundation in the name of all professional Zope developers. Assuming no large outcry in the next few days this is where the 100 bucks will go. Thanks, Tim signature.asc Description: This is a digitally signed message part ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Next Step to Bug Resolution???
Thanks All, On Fri, 2009-01-16 at 21:55 +0100, Carsten Senger wrote: > > Sure you can have specialized fields that subclass from Field, TextLine, > or another base class. E.g. RegistrationNumber(TextLine) that takes care > to validate the input for a special format. But you use them in an > interface class, not the class that implements the interface. > Okay. I got this down now. I still have a problem with understanding the use cases for using attribute=Object(schema=IMySchema ... But now all of the docs may make mmore sense with all I've leearned to past few days. Cheers, Tim signature.asc Description: This is a digitally signed message part ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Next Step to Bug Resolution???
Hi Shane, On Tue, 2009-01-13 at 14:10 -0700, Shane Hathaway wrote: > Sorry, but the patch doesn't make any sense. Your version of > _validate_fields quietly skips validation entirely by default. First of all that is why I asked for others to look at it. :-) But I DID test it by inserting an incorrect schema and it did throw the correct error. I think it was the ShemaNotImplemented error. This was a few weeks ago but I can repeat it if needed. As I explained before; when one schema is checked by _validate_fields then all is well. The parameter 'errors' is None. Then errors is set to an empty list and any possible error msgs are appended. BUT when a schema has to check another schema because they are chained. 'errors' is already an empty list but even though the parameter errors is None a new list is appended to the first pass errors. This creates the msg WrongContainedType: [, []] because it IS a WrongContainedType because there is an empty list inside the original list. 'errors' is returned from _validate_fields back to the _validate method of the Object class where it is simply tested to see if it is empty. On this second pass it ISN't empty. It has another list inside so it fails the truth test and incorrectly throws an error. > Look at the __repr__ method of the ValidationError class in the > _bootstrapinterfaces.py module of the zope.schema package. This method > was designed to generate short error messages, but in your case it > appears to be truncating the error messages altogether. I would start > by changing that particular __repr__() method to: > > def __repr__(self): > return '%s(%s)' % (self.__class__.__name__, repr(self.args)) > > This version prefers verbosity. At a minimum, I hope this version of > __repr__ will change the bizarre message > "zope.schema.interfaces.WrongContainedType: [, []]" into something legible. It is more verbose. But I'm afraid it exhibits the same behavior as described above. Here are the results: in _validate raise WrongContainedType(errors) WrongContainedType: [RequiredMissing(()), WrongContainedType(([RequiredMissing(())],))] Note the empty parens. Now if I introduce bad code I get: in _validate raise WrongContainedType(errors) WrongContainedType: [RequiredMissing(()), SchemaNotProvided(())] SchemaNotProvided is correct. Though there isn't much else to go on but the full traceback points me to the right place. *** Shane, I think that so much of this is no longer useful. Right not now I'll go back and read all the obscure documentation (for the upteenth time) and see if it makes more sense now. I am very confused about thee use cases between creating Fields and using the Object(schema=Ischema) approach. Thanks for your help. --Tim -- Timothy Cook, MSc Health Informatics Research & Development Services LinkedIn Profile:http://www.linkedin.com/in/timothywaynecook Skype ID == timothy.cook ** *You may get my Public GPG key from popular keyservers or * *from this link http://timothywayne.cook.googlepages.com/home* ** signature.asc Description: This is a digitally signed message part ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Next Step to Bug Resolution???
Thanks for all the assistance. On Fri, 2009-01-16 at 18:05 +0100, Martijn Faassen wrote: > Yes, you do create new schema fields by subclassing from Field. > > It's just that we saw you putting a field not in a schema but in what > looked like a concrete object. This has given me a BIG pause while I'm working on a simpler example. It may actually solve the problem. Are you saying that in order to create a Field that can be used as an attribute of another class; I should define it in an interface and ONLY in an interface? Such like pseudo: import Field class IAbc(Interface) myNewField = Field( and then when I need to use it in a class, simply state that that class implements(IAbc)? If this is true I have a two month hard core re-factoring to do. Cheers, Tim > Perhaps we were wrong in reading your > code, and this is one reason why you should come up with a minimum > example that demonstrates the problem and only that, without a lot of > distracting code surrounding it. You're the best suited person to > actually create a minimum example. Thanks again. Tim -- Timothy Cook, MSc Health Informatics Research & Development Services LinkedIn Profile:http://www.linkedin.com/in/timothywaynecook Skype ID == timothy.cook ** *You may get my Public GPG key from popular keyservers or * *from this link http://timothywayne.cook.googlepages.com/home* ** signature.asc Description: This is a digitally signed message part ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Next Step to Bug Resolution???
On Fri, 2009-01-16 at 15:55 +0100, Martijn Faassen wrote: > I don't think a wiki page with a chronicle is necessary or even > helpful; you need to give us the information necessary to find the > bug, but no distracting surrounding information. Okay. > To debug this > problem, a developer will need the smallest possible example of code > that demonstrates the problem. That means, I take it, just 2 schemas > and a single form. Describe briefly what you expect to happen and what > in fact happens. If that example can be done *without* inheriting from > Field that'd be good, as it is true that Field is only to be used > inside a schema definition and once someone sees that we'll conclude > that's the cause of the problem even though it might not be. It is interesting that in table 4.1 of Philipp W's book it specifically states that Field is the base class for all other fields. So how does one build fields that are noot part of the standard zope.schema? > > Once we have the example someone can either debug the problem, or tell > you what you're trying to do isn't the right way to do it. > Thanks, Tim -- Timothy Cook, MSc Health Informatics Research & Development Services LinkedIn Profile:http://www.linkedin.com/in/timothywaynecook Skype ID == timothy.cook ** *You may get my Public GPG key from popular keyservers or * *from this link http://timothywayne.cook.googlepages.com/home* ** <> signature.asc Description: This is a digitally signed message part ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Next Step to Bug Resolution???
On Mon, 2009-01-12 at 22:05 +0100, Martijn Faassen wrote: > Okay, I'll take another look then and look at ObjectRef. Ah, yes, Dan > pointed out to you that you are using a zope.schema.Field in a class > instead of in a schema (an interface). That isn't right, and since the > direct use of that causes an error, that looks suspicious. Whether it is > the cause of the bug or not I do not know. Thanks to all for the help. I will put together a wiki page that chronicles and explains the entire issue and process of getting here. Along with the simplest example I can come up with. I'm still a little confused about why using Field as a base class is wrong. I know that it wasn't it's original purpose but here is the situation. I originally inherited from 'object' in my base classes and from Interface in their associated interfaces. But, because many of the base classes (and their schemas) are required to define attributes of other classes. I found that I did not have the meta-data attributes such as required, default, etc for those schemas to represent the attributes in the latter schemas. So I chose to inherit from IField and Field in my bases so that I inherited. Now maybe there is a MUCH more appropriate way to build these OSHIP base classes than inheriting from Field. But in mid-2007 I searched hi and lo and asked on the mailing lists and still do not have a better solution. So if someone can tell me where I can find the documentation/examples for building your own schemas that will be validated then I'll re-factor the entire application to make it right. Cheers, Tim <> signature.asc Description: This is a digitally signed message part ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Next Step to Bug Resolution???
On Fri, 2009-01-09 at 11:05 +, Chris Withers wrote: > I can't. The testrunner is already there and buildout-based development > makes it trivial to run. svn already does the patch creation for you: > > $ svn diff > > > be able to get past that bit. Perhaps a kind Zope dev will pick up on > > this. > > Unlikely with his attitude... > > Chris Hi Chris, Thanks for keeping the thread alive so I can continue on the road to how to solve this problem. I DID submit a patch suggestion in the Launchpad bug report. What I am not sure are, with this fix, about are the possible other implications to the rest of the zope.schema package. I would also like for you to explain just what it is about my "attitude" that you find so offensive/problematic? I traced down and described the problem to the function level. I suggested a fix and asked for experts to review and apply it. I do not have (and am not qualified to have) commit access to ZCA source. So again, referring to the subject line. What are the next steps? Cheers, Tim -- Timothy Cook, MSc Health Informatics Research & Development Services LinkedIn Profile:http://www.linkedin.com/in/timothywaynecook Skype ID == timothy.cook ** *You may get my Public GPG key from popular keyservers or * *from this link http://timothywayne.cook.googlepages.com/home* ** <> signature.asc Description: This is a digitally signed message part ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Next Step to Bug Resolution???
Thanks Dieter, On Fri, 2008-12-19 at 19:41 +0100, Dieter Maurer wrote: > I often approach situations like this with so called "Monkey Patches": > I replace or enhance classes or methods during startup (triggered > by some startup event). > > This may not be optimal but allows me to solve my problems without > tight coupling with the core developpers who usually do not have > my problems and tend not see them as very high priority. I am starting to see why other Python developers aren't too interested in Zope. Despite the awesome power of the architecture. I've been poking around and using and supporting Zope since 1999. But because I am not an expert programmer (my skills are in another field) and because I do not know Zope inside and out. I am being chastised for not supplying my own complete fixes to the developers or at least being able to cover for their mistakes inside my application. Silly me. Working in open source for 14 years and I had no idea it worked like this. I'm sure glad that we do not run openEHR like that. Cheers, Tim -- Timothy Cook, MSc Health Informatics Research & Development Services LinkedIn Profile:http://www.linkedin.com/in/timothywaynecook Skype ID == timothy.cook ** *You may get my Public GPG key from popular keyservers or * *from this link http://timothywayne.cook.googlepages.com/home* ** signature.asc Description: This is a digitally signed message part ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] [Zope3-Users] Next Step to Bug Resolution???
Hi Chris, On Fri, 2008-12-19 at 10:06 +, Chris Withers wrote: > Tim Cook wrote: > > As I said before I may have miss-diagnosed the problem and may fix may > > break other things? > > This is what a full-coverage unit and functional test suit is for. > You have got automated tests for all this stuff, right? > NO! I do not! I am a ZCA user not a full time python programmer. That is why I a asking for help here. Initially at least on the Zope Users list. If you are expecting ZCA users to be full time Python gurus then why have two mailing lists? It seems that you are asking a "user" to provide the "developers" with a ready to commit patch. I wish I had those skills and could do so. Alas, it isn't going to happen. Cheers, Tim -- Timothy Cook, MSc Health Informatics Research & Development Services LinkedIn Profile:http://www.linkedin.com/in/timothywaynecook Skype ID == timothy.cook ** *You may get my Public GPG key from popular keyservers or * *from this link http://timothywayne.cook.googlepages.com/home* ** signature.asc Description: This is a digitally signed message part ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] [Zope3-Users] Next Step to Bug Resolution???
Hi Dan, Thanks for taking a look. On Thu, 2008-12-18 at 20:06 +0300, Dan Korostelev wrote: > Hi, Tim. > > I builded out your application and took a quick look at the error. It > looks like you're mis-using the zope.schema.Field class and its > interface. It should be only used in schema definition, while you are > using Field instances as attributes for other objects. For example, > you are defining the ObjectId as a field, but are using its instances > as objects. That's not a valid use. Okay. I can accept that it might be a mis-use. > > I extracted the problematic code to separate file and changed the > IField to Interface and Field to ``object`` (though you'll want to use > Persistent, i guess) for ObjectId and ObjectRef and it works okay. :-) > This is actually what I did at first. You may want to refer to the UML http://www.openehr.org/svn/specification/TAGS/Release-1.0.1/publishing/architecture/computable/UML/uml_start_view.html (This is the rm.support.identification package we are looking at) Since ObjectId is an abstract class so inheriting from object seems reasonable. However, most of the other id classes inherit from ObjectId and when they are used as attributes to other classes they need to have the meta data expected by zope.schema. Otherwise you get errors like "keyword required not found" (or something similar). This is true throughout the model. So my solution (and CERTAINLY there may be a better one) was to use the Field class (it is just a Python class - right?) as the base class for all of the base classes in the model. As I said before I may have miss-diagnosed the problem and may fix may break other things? > Or, it might be that I don't fully understand your code and > application architecture, so I would like to hear more about it. It > looks quite over-engeneered to me. I fully understand why you might think that. IF you'll bear with me... healthcare information is very complex (certainly the complex domain I've run into in 32 years of dealing with information systems) and the knowledge domain is constantly changing. I have a short point paper here http://timothywayne.cook.googlepages.com/context-lies.pdf that gives a 30,000' view of the issues of semantic interoperability and computability of healthcare information. and a good introduction to the domain issues are here: http://www.openehr.org/shared-resources/getting_started/openehr_primer.html This model has more than 20 years of constantly improving R&D on this subject. The key goal have always been to be abstract enough so that it can be implemented in any OO language on any platform in any type of healthcare setting and all stored patient information is guaranteed to be computable (decision support, etc) as well as maintain it's semantic integrity over the course of time irregardless of the changes in the science. So in essence you can go back to any point in time and not only know what the blood pressure of the patient was, but also "what was known" about blood pressure at that time. This model has been implemented in Eiffel, Java, C# and VB. The applications (both commercial and open source) have demonstrated these capabilities. Certainly the model isn't perfect but there is a completely open change management system in place that deals with any changes due to new ares or new science. In order for this Python implementation to remain as true as possible to the model as well as exercise the value in the ZCA; this is the path I have taken. Thanks for your help. Cheers, Tim -- Timothy Cook, MSc Health Informatics Research & Development Services LinkedIn Profile:http://www.linkedin.com/in/timothywaynecook Skype ID == timothy.cook ** *You may get my Public GPG key from popular keyservers or * *from this link http://timothywayne.cook.googlepages.com/home* ** <> signature.asc Description: This is a digitally signed message part ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] BOUNTY! was: Next Step to Bug Resolution???
OOOPS! I forgot to provide the link to the installation instructions: http://www.openehr.org/wiki/display/dev/OSHIP+Installation --Tim On Thu, 2008-12-18 at 13:00 -0200, Tim Cook wrote: > Based on private responses I have received I would like to clarify some > things. > > I fully realize that people have their days jobs. So do I. I do not > get paid to work on this project. > > Secondly, I am a ZCA user. I am a Python tinkerer, not a programmer. > It seems to me that it would take me days to contrive a mockup of this > situation so that there is a live demonstration of this error outside of > my project. > > I believe that it would take an experienced Python/Zope developer no ore > than 1-2 hours to install my application, see the problem and provide a > fix. > > There is an explanation of how to exercise the problem as well as how to > apply my suggested fix here: > http://www.openehr.org/mailarchives/ref_impl_python/msg00406.html > > The pertinent part is the last 4 paragraphs and it is copied below for > convenience. > > > I will later commit an update that fixes two errors he found. I will > also include a new zope.schema._filed.py file that correctly processes > the multi-level Object field calls that we make. I have no idea when > the Zope gurus will be updating zope.schema But I know this fix works > for our needs. It will be in the docs directory and named as > _field.py.oship > > To see the problem that exists in the current _filed.py you can start > your server and verify that you can go to > http://localhost:8080/oship/archetypedetails and verify that you can see > the archetype details. In your terminal window you should see that > there are no errors reported. > > Stop your server and go to > oship/km/openehr/ehr/cluster/checklist_item_general.py and around line > #75 and uncomment the self.parentArchetype assignment. Now start your > server and go to the link above. You will get a server error and in > your terminal window you'll see that you have a WrongContainedType > error. > > Stop your server. Replace _field.py in you zope.schema egg directory > (rename your original first) with the _field.py.oship Restart your > server and you will see that it now correctly processes the multi-level > Object fields. If you want more details about this then please see the > bug report I filed on Launchpad > https://bugs.launchpad.net/bugs/301226 > > > > This issue is such a huge frustration for me that I am offering a bounty > of 100USD out of my personal pocket to the first person that solves the > issue, gets it committed to a published zope.schema egg and included in > the standard Grok distribution. > > It seems to me to be a reasonable (though not extravagant) amount since > most of the trouble shooting has already been done. > > Thanks, > Tim > > > > On Thu, 2008-12-18 at 08:35 -0200, Tim Cook wrote: > > Hi All, > > > > I have had an issue on the table for months. I started a dialog about > > it here: > > > > http://mail.zope.org/pipermail/zope3-users/2008-October/008215.html > > > > The thread was interesting, helpful and did lead me to find an error in > > some schema definitions because of a misunderstanding of the required > > attribute. But that had nothing to do with the problem. > > > > It was first thought that it was a nasty, empty error report. After > > some investigation I discovered that it was an error that shouldn't be > > an error. Once I determined what I thought was the cause and a possible > > fix I posted a bug report on Launchpad > > > > https://bugs.launchpad.net/zope3/+bug/301226 > > > > So here we are. I have a possible solution and the only comments I get > > from the Zope Community are private emails (yes plural) asking me if > > anyone is working on this issue. I have to say that as far as I can > > tell; no. At this point I would be happier if someone just told me why > > my fix might negatively affect the other schema field validations. > > > > Now I realize that I must be the only person in the entire world to > > exercise zope.schema this way. BUT! It should work or it should be WELL > > documented that you cannot have cascading attribute=Object(IMySchema) > > definitions. > > > > The description of the project is here: > > http://www.openehr.org/wiki/display/dev/OSHIP+Developer%27s+Wiki > > > > This is a rather major project. See: http://www.ohloh.net/
[Zope-dev] BOUNTY! was: Next Step to Bug Resolution???
Based on private responses I have received I would like to clarify some things. I fully realize that people have their days jobs. So do I. I do not get paid to work on this project. Secondly, I am a ZCA user. I am a Python tinkerer, not a programmer. It seems to me that it would take me days to contrive a mockup of this situation so that there is a live demonstration of this error outside of my project. I believe that it would take an experienced Python/Zope developer no ore than 1-2 hours to install my application, see the problem and provide a fix. There is an explanation of how to exercise the problem as well as how to apply my suggested fix here: http://www.openehr.org/mailarchives/ref_impl_python/msg00406.html The pertinent part is the last 4 paragraphs and it is copied below for convenience. I will later commit an update that fixes two errors he found. I will also include a new zope.schema._filed.py file that correctly processes the multi-level Object field calls that we make. I have no idea when the Zope gurus will be updating zope.schema But I know this fix works for our needs. It will be in the docs directory and named as _field.py.oship To see the problem that exists in the current _filed.py you can start your server and verify that you can go to http://localhost:8080/oship/archetypedetails and verify that you can see the archetype details. In your terminal window you should see that there are no errors reported. Stop your server and go to oship/km/openehr/ehr/cluster/checklist_item_general.py and around line #75 and uncomment the self.parentArchetype assignment. Now start your server and go to the link above. You will get a server error and in your terminal window you'll see that you have a WrongContainedType error. Stop your server. Replace _field.py in you zope.schema egg directory (rename your original first) with the _field.py.oship Restart your server and you will see that it now correctly processes the multi-level Object fields. If you want more details about this then please see the bug report I filed on Launchpad https://bugs.launchpad.net/bugs/301226 This issue is such a huge frustration for me that I am offering a bounty of 100USD out of my personal pocket to the first person that solves the issue, gets it committed to a published zope.schema egg and included in the standard Grok distribution. It seems to me to be a reasonable (though not extravagant) amount since most of the trouble shooting has already been done. Thanks, Tim On Thu, 2008-12-18 at 08:35 -0200, Tim Cook wrote: > Hi All, > > I have had an issue on the table for months. I started a dialog about > it here: > > http://mail.zope.org/pipermail/zope3-users/2008-October/008215.html > > The thread was interesting, helpful and did lead me to find an error in > some schema definitions because of a misunderstanding of the required > attribute. But that had nothing to do with the problem. > > It was first thought that it was a nasty, empty error report. After > some investigation I discovered that it was an error that shouldn't be > an error. Once I determined what I thought was the cause and a possible > fix I posted a bug report on Launchpad > > https://bugs.launchpad.net/zope3/+bug/301226 > > So here we are. I have a possible solution and the only comments I get > from the Zope Community are private emails (yes plural) asking me if > anyone is working on this issue. I have to say that as far as I can > tell; no. At this point I would be happier if someone just told me why > my fix might negatively affect the other schema field validations. > > Now I realize that I must be the only person in the entire world to > exercise zope.schema this way. BUT! It should work or it should be WELL > documented that you cannot have cascading attribute=Object(IMySchema) > definitions. > > The description of the project is here: > http://www.openehr.org/wiki/display/dev/OSHIP+Developer%27s+Wiki > > This is a rather major project. See: http://www.ohloh.net/p/oship for > some metrics. We have just received three years of funding from the > Brazilian government to complete the platform and develop an > Epidemiological decision support system on top of it to improve the > recognition of syndromic outbreaks. > > Right now the hardworking core open source team understands that we need > to replace zope.schema._field.py with our own to make it work. But when > the project is ready, in a few months, for healthcare application > developers worldwide to start using it. It may be a hard sell to say; > "Yeah we use the really cool, robust, well tested and trusted > application server called the
[Zope-dev] Next Step to Bug Resolution???
Hi All, I have had an issue on the table for months. I started a dialog about it here: http://mail.zope.org/pipermail/zope3-users/2008-October/008215.html The thread was interesting, helpful and did lead me to find an error in some schema definitions because of a misunderstanding of the required attribute. But that had nothing to do with the problem. It was first thought that it was a nasty, empty error report. After some investigation I discovered that it was an error that shouldn't be an error. Once I determined what I thought was the cause and a possible fix I posted a bug report on Launchpad https://bugs.launchpad.net/zope3/+bug/301226 So here we are. I have a possible solution and the only comments I get from the Zope Community are private emails (yes plural) asking me if anyone is working on this issue. I have to say that as far as I can tell; no. At this point I would be happier if someone just told me why my fix might negatively affect the other schema field validations. Now I realize that I must be the only person in the entire world to exercise zope.schema this way. BUT! It should work or it should be WELL documented that you cannot have cascading attribute=Object(IMySchema) definitions. The description of the project is here: http://www.openehr.org/wiki/display/dev/OSHIP+Developer%27s+Wiki This is a rather major project. See: http://www.ohloh.net/p/oship for some metrics. We have just received three years of funding from the Brazilian government to complete the platform and develop an Epidemiological decision support system on top of it to improve the recognition of syndromic outbreaks. Right now the hardworking core open source team understands that we need to replace zope.schema._field.py with our own to make it work. But when the project is ready, in a few months, for healthcare application developers worldwide to start using it. It may be a hard sell to say; "Yeah we use the really cool, robust, well tested and trusted application server called the Zope Component Architecture because it really shows the strengths of the open source development process. Oh, by the way, after everything is installed you have to replace a core ZCA file with the one we provide you in order to make it actually work." Doesn't sound very professional to me and it should be embarrassing to the Zope Community if that has to happen. Thank you for reading this long posting. I hope someone delivers me a Holiday package in the form of a fixed zope.schema package. :-) Cheers, Tim -- Timothy Cook, MSc Health Informatics Research & Development Services LinkedIn Profile:http://www.linkedin.com/in/timothywaynecook Skype ID == timothy.cook ** *You may get my Public GPG key from popular keyservers or * *from this link http://timothywayne.cook.googlepages.com/home* ** signature.asc Description: This is a digitally signed message part ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Show Stopping Bug
Hi All, I started a conversation on the Zope Users list back in October about an issue I had with the Object field in zope.schema. http://mail.zope.org/pipermail/zope3-users/2008-October/008215.html After comments acknowledging that this is a real problem there still wasn't any activity on it. I did some investigation myself and "I THINK" I found the problem. So I filed this bug report: https://bugs.launchpad.net/zope3/+bug/301226 I am not a great Python programmer nor do I know a lot about the ZCA internals. I did make a suggestion as to the solution and it seems to work for me but it really needs an expert to look at it and see what ramifications it may have on other aspects of the ZCA. I will REALLY appreciate someone with expertise in this area taking a look at this. I have spent nearly one year on this project http://www.openehr.org/wiki/display/dev/OSHIP+Developer%27s+Wiki (completely open source) and I think it is a serious black eye to have to tell users of my platform that they have to replace, by hand, a portion of the Zope core in order to make it function. Thanks, Tim -- Timothy Cook, MSc Health Informatics Research & Development Services LinkedIn Profile:http://www.linkedin.com/in/timothywaynecook Skype ID == timothy.cook ** *You may get my Public GPG key from popular keyservers or * *from this link http://timothywayne.cook.googlepages.com/home* ** signature.asc Description: This is a digitally signed message part ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Python 2.6
Now that ZCA is working with Python 2.5 on 32 and 64 bit platforms (thanks guys!) Is there a plan being formulated to address all the deprecation warnings about 'with' becoming a reserved word in Python2.6? Thanks, --Tim ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Re: Zope 3 on Python 2.5, Zope 3 releases
I have reported Bug 248380: on this issue. The problem seems to me to be in building the .c modules. That causes the MemoryError that Lorenzo reported but it isn't the root of the problem. There are a large number of "warning: initialization from incompatible pointer type" issues. --Tim On Mon, 2008-07-14 at 13:30 +0200, Martijn Faassen wrote: > Hi there, > > Tres, could you report this issue on Launchpad? > > Not Lorenzo's issue as it happens with an empty container, but perhaps > we can work out a bug report for the ZODB folks as well. Just dig into > what's up in .values() or .items() and where the error exactly occurs, > perhaps this way we can come up with a very small ZODB sample > application. > > Regards, > > Martijn > ___ > Zope-Dev maillist - Zope-Dev@zope.org > http://mail.zope.org/mailman/listinfo/zope-dev > ** No cross posts or HTML encoding! ** > (Related lists - > http://mail.zope.org/mailman/listinfo/zope-announce > http://mail.zope.org/mailman/listinfo/zope ) -- ** Join the OSHIP project. It is the standards based, open source healthcare application platform in Python. Home page: https://launchpad.net/oship/ Wiki: http://www.openehr.org/wiki/display/dev/Python+developer%27s+page ** signature.asc Description: This is a digitally signed message part ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Zope 3 on Python 2.5, Zope 3 releases
On Thu, 2008-06-26 at 13:14 -0700, Paul Carduner wrote: > On Thu, Jun 26, 2008 at 1:06 PM, Martijn Faassen <[EMAIL PROTECTED]> wrote: > > Hi there, > > > > I'm curious about the plans of Zope 3 on Python 2.5. > > > > * Are people using Zope 3 with Python 2.5 already? What are your > > experiences? > > We are using Python 2.5 fully for the last several months now and have > encountered zero problems. > Paul, Are you doing this on Linux? I tried 3.4 on Python 2.5 a few weeks ago and I don't recall the problems now but there were several. --Tim -- Timothy Cook, MSc Health Informatics Research & Development Services LinkedIn Profile:http://www.linkedin.com/in/timothywaynecook Skype ID == timothy.cook ** *You may get my Public GPG key from popular keyservers or * *from this link http://timothywayne.cook.googlepages.com/home* ** signature.asc Description: This is a digitally signed message part ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] buildout failures
On Sat, 2008-06-14 at 13:10 +0200, Christian Theune wrote: > That's exactly the behaviour I was afraid of. > > I propose to keep it around for a few more days to see how it stabilizes. If > it jerks again, I'll switch off notifications until I get a change done that > avoids this behaviour. > > Christian Thanks Christian. But then using a little client side mail filtering made it easy enough to dump them into their own folder so it isn't such a big deal. --Tim -- Timothy Cook, MSc Health Informatics Research & Development Services LinkedIn Profile:http://www.linkedin.com/in/timothywaynecook Skype ID == timothy.cook ** *You may get my Public GPG key from popular keyservers or * *from this link http://timothywayne.cook.googlepages.com/home* ** signature.asc Description: This is a digitally signed message part ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
