Hi everybody..
Happy to be back soon. We are happy to see ourselves making progress in different ways.
We managed to get the failure, in the module Products, fixed which needed only a slight change in the file C-API file _Acquisition.c . Of course we got help from the Zope-dev mailing list. We have already made the Checkin for this fixing.
Bristow and Deepak have managed to fix the deprecation warnings regarding 'with' and 'as' by replacing the respective variables with another name. The changes are still to be checked in as both of them are waiting to get their commit access to the Zope svn. The replies from the mailing lists of Zope-devPython-dev towards their doubts were pretty much helpful.
Vijin and Vyshakh are still working on removing all other deprecated warnings. Hope to see them make it very soon.
The security auditing of zope in python2.5/2.6 is also at the starting phase. We have put mails in mailing lists of Zope-dev , PyPy (Which we have decided not to give so much importance after some discussions with Sidnei) and in Python-dev. We hope to start with the AST implementation of the restricted python very soon.
Not so much for now. And hope to see you soon with more updates on the progress... and
Tuesday, July 22, 2008
THE ROUTE GET DIVIDES ...
The mid-term evaluation is over by now. And we are happy to be here again. Sidnei has helped us by pointing out the next works to be accomplished. As the time-line for the project is still known to be the first or second week of August, we have decided to divide the work among ourselves.
The works -
Testing and fixing Zope on Python 2.6 - will be handled by Bristow and Deepak..
Fixing all the deprecation warnings - will be handled by Vijin and Vyshakh..
Doing a security audit on new types introduced in Python 2.5/2.6- will be handled by Ranjith..
Sidnei has already pointed out another work - Trying to run other applications, for example, Plone on top of
Zope/Python 2.5 to see if anything breaks- which we will be looking afterwards.
We are also going through the failure and error left in the modules Products and Zope2..
Thats all upto now..
The works -
Testing and fixing Zope on Python 2.6 - will be handled by Bristow and Deepak..
Fixing all the deprecation warnings - will be handled by Vijin and Vyshakh..
Doing a security audit on new types introduced in Python 2.5/2.6- will be handled by Ranjith..
Sidnei has already pointed out another work - Trying to run other applications, for example, Plone on top of
Zope/Python 2.5 to see if anything breaks- which we will be looking afterwards.
We are also going through the failure and error left in the modules Products and Zope2..
Thats all upto now..
Thursday, July 10, 2008
BACK ON TRACK...
Sorry for this late post. Since we were having university exams we were not able to devote fully into the project. Any way we are now back in track.
For the last few days we were trying to fix the failures in modules Products and ZPublisher and the error in Zope2. The failure in ZPublisher was a doc test failure. We fixed it by making a slight change in the doc test. We have already made Zope checkin with this change.
We have been going through the error in Zope2 and failure in Products. In Zope2 the error is due to the raising of configuration error with an invalid warning category in python2.5 . And in module Products the failure is basically because of the change in class hierarchy in python2.5 which results in the failure to find the attribute of a class. We are trying to get these fixed. Hope it won't take much time.
For the RPython implementation in zope2 we are in need of some help and guidance as we are not much familiar to the security auditing of RestrictedPython. Our organization administrator has suggested that a volunteer named Chris Withers is interested to help us in this matter. We have asked about it in the Zope dev mailing list.
We will back soon with more progress..
For the last few days we were trying to fix the failures in modules Products and ZPublisher and the error in Zope2. The failure in ZPublisher was a doc test failure. We fixed it by making a slight change in the doc test. We have already made Zope checkin with this change.
We have been going through the error in Zope2 and failure in Products. In Zope2 the error is due to the raising of configuration error with an invalid warning category in python2.5 . And in module Products the failure is basically because of the change in class hierarchy in python2.5 which results in the failure to find the attribute of a class. We are trying to get these fixed. Hope it won't take much time.
For the RPython implementation in zope2 we are in need of some help and guidance as we are not much familiar to the security auditing of RestrictedPython. Our organization administrator has suggested that a volunteer named Chris Withers is interested to help us in this matter. We have asked about it in the Zope dev mailing list.
We will back soon with more progress..
Subscribe to:
Posts (Atom)
