- Backport bug fix from master: On at least one 64-bit Ubuntu system
under Python 3.2, using the ``view_config`` decorator caused a
``RuntimeError: dictionary changed size during iteration``
exception. It no longer does. See
https://github.com/Pylons/pyramid/issues/635 for more information.
> - Backport bug fix from master: On at least one 64-bit Ubuntu system > under Python 3.2, using the ``view_config`` decorator caused a > ``RuntimeError: dictionary changed size during iteration`` > exception. It no longer does. See > https://github.com/Pylons/pyramid/issues/635 for more information.
>> - Backport bug fix from master: On at least one 64-bit Ubuntu system >> under Python 3.2, using the ``view_config`` decorator caused a >> ``RuntimeError: dictionary changed size during iteration`` >> exception. It no longer does. See >> https://github.com/Pylons/pyramid/issues/635 for more information.
> > - Backport bug fix from master: On at least one 64-bit Ubuntu system
> > under Python 3.2, using the ``view_config`` decorator caused a
> > ``RuntimeError: dictionary changed size during iteration``
> > exception. It no longer does. See
> > https://github.com/Pylons/pyramid/issues/635for more information.
>> - Backport bug fix from master: On at least one 64-bit Ubuntu system >> under Python 3.2, using the ``view_config`` decorator caused a >> ``RuntimeError: dictionary changed size during iteration`` >> exception. It no longer does. See >> https://github.com/Pylons/pyramid/issues/635 for more information.
you can upgrade packages installed with `pip` using `easy_install`, and vice versa.
pip currently has a bug in the upgrade function, so i'd recommend against using it for upgrades.
a call to `easy_install --upgrade PACKAGE` will upgrade that package , upgrade any dependencies to required version numbers, and recurse through all the packages with the same logic. many times, this will only upgrade a single package and take a few moments.
the current version of `pip --upgrade PACKAGE` will upgrade the package, reinstall any dependencies to the latest versions, and recurse through all the packages with the same logic. this will cause every package in the 'ecosystem' to be upgraded -- which can take many minutes , and can upgrade packages to newer & incompatible versions.
the pip team is actively discussing a fix for this.
until this is addressed though, i would *strongly* recommend that you don't '--upgrade' anything in pip. the process is needlessly long, and you'll find it introducing random bugs and inconsistencies in your code that are really hard to track down if you use many 3rd party libraries in your pyramid apps.
On Fri, Aug 17, 2012 at 7:50 AM, Jonathan Vanasco <jonat...@findmeon.com> wrote:
> you can upgrade packages installed with `pip` using `easy_install`, and vice
> versa.
> pip currently has a bug in the upgrade function, so i'd recommend against
> using it for upgrades.
> a call to `easy_install --upgrade PACKAGE` will upgrade that package ,
> upgrade any dependencies to required version numbers, and recurse through
> all the packages with the same logic.
> many times, this will only upgrade a single package and take a few moments.
Will it respect the existing installation method (a regular package
install) or will it convert it to easy_install's
package-inside-an-egg-directory-that's-added-to-a-pth-file?
