Pyramid Debugtoolbar 3.0 released

[Michael Merickel]

Hey folks, after 2.5 was released with some incremental changes, I've released 3.0 today with a slightly larger change to the toolbar which could potentially break custom panels (if you're using any).

Here are the highlights:

- Updated to bootstrap v3.3.6 and moved some static assets around.

- Enabled interactive tablesorting on table columns (performance and sqlalchemy panels).

- setuptools-git is now required to install a fork of the codebase in non-editable mode. This is only for forks, not for the official version from PyPI.

- pyramid_mako and the .dbtmako renderer are no longer included in your applications when using the toolbar. You may need to include pyramid_mako if your app is depending on it and were skating by because the toolbar included it for you.

- The toolbar is now completely isolated from your application. This means it does all of its rendering of the panels in its own app and does not depend on any features of your own application. This will break custom panels if they are not using the correct "request" object for the toolbar to do rendering. Previously there were cases where the panels were rendered via your application instead of within the toolbar, requiring the toolbar to install things like pyramid_mako into your apps even if you didn't need it.


Full change history:
http://docs.pylonsproject.org/projects/pyramid-debugtoolbar/en/latest/changes.html


You can install it via PyPI:

  pip install pyramid_debugtoolbar==3.0

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

Thanks!

- Pylons Project core developers

[Jonathan Vanasco]

On Saturday, April 23, 2016 at 2:34:24 PM UTC-4, Michael Merickel wrote:

- setuptools-git is now required to install a fork of the codebase in non-editable mode. This is only for forks, not for the official version from PyPI.

Is there a changeset related to this?  I'm trying to see if this will affect me, and there isn't much info in the repo regarding this via searching `setuptools-git` or `git`

[Bert JW Regeer]

https://github.com/Pylons/pyramid_debugtoolbar/commit/e348868a2d5513b8c6b53b0853e830d66076d034

It’s similar as the rest of the Pylons projects in that there is no MANIFEST.in.

So if you check out the repo without .git and without setuptools-git, by default setuptools will only package up the .py files, and none of the other required assets.

Bert

> --
> You received this message because you are subscribed to the Google Groups "pylons-discuss" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to pylons-discus...@googlegroups.com.
> To post to this group, send email to pylons-...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/pylons-discuss/063aee4e-69c5-4fba-8368-5c85a938f236%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

[Jonathan Vanasco]

Thanks. Totally unaffected by this!

[Mike Orr]

On Sun, Apr 24, 2016 at 9:27 PM, Bert JW Regeer <xist...@0x58.com> wrote:
> https://github.com/Pylons/pyramid_debugtoolbar/commit/e348868a2d5513b8c6b53b0853e830d66076d034
>
> It’s similar as the rest of the Pylons projects in that there is no MANIFEST.in.
>
> So if you check out the repo without .git and without setuptools-git, by default setuptools will only package up the .py files, and none of the other required assets.

Is that why Pyramid from source requires a special setup procedure?

Is there a reason for not using MANIFEST.in? How does setuptools-git
know which files to include and which ones not to?

[Bert JW Regeer]

> On Apr 26, 2016, at 10:19, Mike Orr <slugg...@gmail.com> wrote:
>
> On Sun, Apr 24, 2016 at 9:27 PM, Bert JW Regeer <xist...@0x58.com> wrote:
>> https://github.com/Pylons/pyramid_debugtoolbar/commit/e348868a2d5513b8c6b53b0853e830d66076d034
>>
>> It’s similar as the rest of the Pylons projects in that there is no MANIFEST.in.
>>
>> So if you check out the repo without .git and without setuptools-git, by default setuptools will only package up the .py files, and none of the other required assets.
>
> Is that why Pyramid from source requires a special setup procedure?

We don’t support Pyramid from source, so there is no “special” setup procedure. Either fetch it from PyPi or do an editable checkout using git (only required if hacking on Pyramid and friends).

>
> Is there a reason for not using MANIFEST.in? How does setuptools-git
> know which files to include and which ones not to?

https://github.com/msabramo/setuptools-git

That explains what is and isn’t included. tl;dr: everything checked into git is added.

For background please take a look at https://github.com/Pylons/pyramid/issues/121 (also Pyramid’s oldest and longest running issue to date).

>
> --
> You received this message because you are subscribed to the Google Groups "pylons-discuss" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to pylons-discus...@googlegroups.com.
> To post to this group, send email to pylons-...@googlegroups.com.

> To view this discussion on the web visit https://groups.google.com/d/msgid/pylons-discuss/CAH9f%3Dupf%3DHWzcSZnfYj8zcEM9skF5YDTG4P7mvDTiBuGEw%3DNww%40mail.gmail.com.