It's out -- or at least partially...
The homepage and update site at sourceforge are not updated because the sourceforge shell is currently offline (https://sourceforge.net/docs/a04), so, as soon as it's back the release should be completed...
Still, it is already available in the update site at http://fabioz.com/pydev and as zip files at sourceforge.
This release enables changing a value in the debugger, and the pydev package explorer can now be safely used, as default actions (copy, paste, rename, etc) were reimplemented (see previous comment to see what this fixed) -- so, the package explorer is now almost out of the beta state.
Some high-priority fixes also made it into this release: the PYTHONPATH passed to PyLint now contains the project PYTHONPATH and a halting condition on code-completion is gone.
As for the pydev extensions, the major change is that the rename refactoring now works in comments and strings (and occurrences are also marked on those).
Tuesday, February 13, 2007
Friday, February 09, 2007
Notes on configuring Zope and Pylons
Just wanted to note that recently I added a (rather short) how-to on configuring Pylons in the sourceforge forum
And for those configuring Zope, there is one little catch... Zope actually has multiple locations with a 'Products' folder (and the parent of those Products folder must be added to the pythonpath... to the system pythonpath if it is a part of zope or to the project pythonpath if it is a part of your project)...
Now, the catch is that the Products folder does not have an __init__.py file... so, pydev won't recognize it as a valid python package unless an __init__.py file is added to each of the Products folder...
Apparently zope does some 'hacking' with the pythonpath itself and adds some black-magic to the mix instead of using the regular python import structure, to have multiple 'Products' scattered around (python would usually find the first one and not get the other Products)... still, it seems that adding those __init__.py files won't have any side-effect on zope itself (and will enable code-completion / code analysis for your projects).
Update: some more details were added to: http://pydev.blogspot.com/2007/05/debugging-zope-in-pydev-extensions.html
And for those configuring Zope, there is one little catch... Zope actually has multiple locations with a 'Products' folder (and the parent of those Products folder must be added to the pythonpath... to the system pythonpath if it is a part of zope or to the project pythonpath if it is a part of your project)...
Now, the catch is that the Products folder does not have an __init__.py file... so, pydev won't recognize it as a valid python package unless an __init__.py file is added to each of the Products folder...
Apparently zope does some 'hacking' with the pythonpath itself and adds some black-magic to the mix instead of using the regular python import structure, to have multiple 'Products' scattered around (python would usually find the first one and not get the other Products)... still, it seems that adding those __init__.py files won't have any side-effect on zope itself (and will enable code-completion / code analysis for your projects).
Update: some more details were added to: http://pydev.blogspot.com/2007/05/debugging-zope-in-pydev-extensions.html
Subscribe to:
Posts (Atom)