Pyramid 1.3.3 released

[Chris McDonough]

Pyramid 1.3.3 has been released. It is a maintenance release in the 1.3
series. Here's what happened since the last release (1.3.2):

1.3.3 (2012-08-10)
==================

- Backport bug fix from master: Explicit url dispatch regexes can
now contain colons. https://github.com/Pylons/pyramid/issues/629

- 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: - In Mako Templates lookup, check if
the uri is already adjusted and bring it back to an asset
spec. Normally occurs with inherited templates or included
components. https://github.com/Pylons/pyramid/issues/606
https://github.com/Pylons/pyramid/issues/607

The documentation for the 1.3.3 release is available at
http://docs.pylonsproject.org/projects/pyramid/en/1.3-branch/

You can install 1.3.3 via PyPI:

easy_install Pyramid==1.3.3

Enjoy, and please report any issues you find to the issue tracker at
https://github.com/Pylons/pyramid/issues

Thanks!

- C

[Zak]

What's the best way to update an existing Pyramid install?

[Erik Buttram]

The easy_install command Chris mentioned will update your installed version.

[Mengu]

easy_install -U pyramid

On Aug 11, 11:41 am, Zak <zakdan...@gmail.com> wrote:
> What's the best way to update an existing Pyramid install?
>
>
>
>
>
>
>
> On Saturday, August 11, 2012 1:29:37 AM UTC-5, Chris McDonough wrote:
>
> > Pyramid 1.3.3 has been released.  It is a maintenance release in the 1.3
> > series.  Here's what happened since the last release (1.3.2):
>
> >    1.3.3 (2012-08-10)
> >    ==================
>
> >    - Backport bug fix from master: Explicit url dispatch regexes can
> >      now contain colons.  https://github.com/Pylons/pyramid/issues/629
>
> >    - 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.

[Raj]

Or if you installed Pyramid with `pip`, you can do `pip install --upgrade pyramid`

[Jonathan Vanasco]

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.

[Mike Orr]

On Fri, Aug 17, 2012 at 7:50 AM, Jonathan Vanasco <jona...@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?

--
Mike Orr <slugg...@gmail.com>