Re: [pylons-discuss] Will `render_to_response` ever return something that is not `pyramid.response.Response`?

2020-10-12 Thread 'Jonathan Vanasco' via pylons-discuss 
Thank you, Michael!

This helps me a lot.

On Monday, October 12, 2020 at 4:16:40 PM UTC-4 mmer...@gmail.com wrote:

> There is a null_renderer in Pyramid, but it's not available via 
> render_to_response. I do not see a code path that would return anything 
> other than an object implementing pyramid.interfaces.IResponse (the 
> expected return value from the app's configured IResponseFactory). This is, 
> of course, slightly more general than pyramid.response.Response.
>
> - Michael
>
> On Oct 12, 2020, at 13:48, 'Jonathan Vanasco' via pylons-discuss <
> pylons-...@googlegroups.com> wrote:
>
> I've looked at the code and am pretty sure the answer is no, but a bunch 
> of subclasses are used here, so I think it's best to ask --  Will 
> render_to_response ever return something that is not 
> `pyramid.response.Response`?
>
> I have a small library that will act on the output of render_to_response; 
> I am trying to catch edge cases where it is improperly invoked and a 
> developer passes in a normal dict (which would be rendered via view_config 
> template or json renderer) instead of the expected output of 
> render_to_response.
>
> -- 
> 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 view this discussion on the web visit 
> https://groups.google.com/d/msgid/pylons-discuss/32fddda9-dba9-4c84-a26a-c0a28a6953dbn%40googlegroups.com
>  
> 
> .
>
>
>

-- 
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-discuss+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/pylons-discuss/13360489-4e50-440e-8553-6ee26d838da0n%40googlegroups.com.

Re: [pylons-discuss] Will `render_to_response` ever return something that is not `pyramid.response.Response`?

2020-10-12 Thread Michael Merickel 
There is a null_renderer in Pyramid, but it's not available via 
render_to_response. I do not see a code path that would return anything other 
than an object implementing pyramid.interfaces.IResponse (the expected return 
value from the app's configured IResponseFactory). This is, of course, slightly 
more general than pyramid.response.Response.

- Michael

> On Oct 12, 2020, at 13:48, 'Jonathan Vanasco' via pylons-discuss 
>  wrote:
> 
> I've looked at the code and am pretty sure the answer is no, but a bunch of 
> subclasses are used here, so I think it's best to ask --  Will 
> render_to_response ever return something that is not 
> `pyramid.response.Response`?
> 
> I have a small library that will act on the output of render_to_response; I 
> am trying to catch edge cases where it is improperly invoked and a developer 
> passes in a normal dict (which would be rendered via view_config template or 
> json renderer) instead of the expected output of render_to_response.
> 
> 
> -- 
> 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-discuss+unsubscr...@googlegroups.com 
> .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/pylons-discuss/32fddda9-dba9-4c84-a26a-c0a28a6953dbn%40googlegroups.com
>  
> .

-- 
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-discuss+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/pylons-discuss/FF9784FC-2B2D-48DA-9516-8DED98ED9D1E%40gmail.com.

[pylons-discuss] Will `render_to_response` ever return something that is not `pyramid.response.Response`?

2020-10-12 Thread 'Jonathan Vanasco' via pylons-discuss 
 

I've looked at the code and am pretty sure the answer is no, but a bunch of 
subclasses are used here, so I think it's best to ask --  Will 
render_to_response ever return something that is not 
`pyramid.response.Response`?

I have a small library that will act on the output of render_to_response; I 
am trying to catch edge cases where it is improperly invoked and a 
developer passes in a normal dict (which would be rendered via view_config 
template or json renderer) instead of the expected output of 
render_to_response.

-- 
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-discuss+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/pylons-discuss/32fddda9-dba9-4c84-a26a-c0a28a6953dbn%40googlegroups.com.

Re: [pylons-discuss] migrating away from formencode?

2020-10-12 Thread 'Jonathan Vanasco' via pylons-discuss 
It's not a big deal and only shows the wrong message if your file is 
required.

We have many forms with optional file uploads.  Not including a file would 
break the form validation.
On Monday, October 5, 2020 at 11:44:45 PM UTC-4 Mike Orr wrote:

> I'm using Formencode 1.3.1. My application switched to Python 3 in
> 2017 and I haven't had any problems with Formencode. It has two file
> uploads, one with a form, and if I submit it without a file I get the
> error message "Please provide only one value" mentioned in the issue.
> This is not a big deal in my use case. Now that Formencode 2 is out
> I'll upgrade to it.
>
> On Mon, Oct 5, 2020 at 7:34 AM 'Jonathan Vanasco' via pylons-discuss
>  wrote:
> >
> > Talk about timing. Several hours after I posted this, Formencode merged 
> the Python3 fix(es) and did a 2.0 release. I guess I'm safe for now, and 
> can migrate away at a more leisurely pace.
> >
> > The big bug was on file uploads (
> https://github.com/formencode/formencode/issues/101), which broke under 
> Python3.
> >
> > I think the other tickers were all housekeeping.
> >
> > On Friday, October 2, 2020 at 4:28:29 PM UTC-4 i...@laspilitas.com 
> wrote:
> >>
> >> I guess I'm still using formencode too with python3 but maybe I just 
> worked around the bugs. Do you know what is holding up the release? Is it 
> for sure a dead-end?
> >>
> >> - Ian
> >>
> >> On Fri, Oct 2, 2020 at 1:20 PM Steve Piercy  
> wrote:
> >>>
> >>> Deform uses Colander and Peppercorn. Use Colander for schemas and 
> validation. There are no tutorials to migrate, but the demo should provide 
> sufficient Colander schema examples for each Deform widget that you want. 
> If you don't see something, ask!
> >>>
> >>> --steve
> >>>
> >>>
> >>> On 10/2/20 1:00 PM, 'Jonathan Vanasco' via pylons-discuss wrote:
> >>> > Thanks, Stev!
> >>> >
> >>> > Deform is high on the list; I should have been more specific - I'm 
> looking for any guidelines/tutorials/tools to migrate the code from 
> Formencode to other libraries. I have a lot of forms schemas/definitions to 
> migrate. I wrote my own validation layer, so I'm not too worried about 
> migrating the code that interacts with forms.
> >>> >
> >>> > FormEncode should my *last* Python2 library to support! There is a 
> longstanding bug on it file uploads breaking on Python3 . I've been using 
> someone's stale PR as a patch for 2 years now, but that is just making 
> everything too fragile so I try to keep all those apps running under 
> Python2..
> >>> >
> >>> >
> >>> > On Friday, October 2, 2020 at 3:40:22 PM UTC-4 Steve Piercy wrote:
> >>> >
> >>> > On 10/2/20 10:06 AM, 'Jonathan Vanasco' via pylons-discuss wrote:
> >>> > > Does anyone have tips/advice for migrating away from Formencode?
> >>> >
> >>> > For server side rendering of forms, Deform is under active 
> development and works under both Python 2 and 3.
> >>> >
> >>> > Demo:
> >>> > https://deformdemo.pylonsproject.org/
> >>> >
> >>> > GitHub:
> >>> > https://github.com/pylons/deform
> >>> >
> >>> > Deform 3.0.0 will use Bootstrap 4 for its templates and drop Python 
> 2 support, although it might still work under Python 2.
> >>> > https://github.com/Pylons/deform/milestone/3
> >>> >
> >>> > --steve
> >>> >
> >>> > --
> >>> > 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  pylons-discus...@googlegroups.com>.
> >>> > To view this discussion on the web visit 
> https://groups.google.com/d/msgid/pylons-discuss/d0a0d404-f081-41f8-865f-b073ed17bc78n%40googlegroups.com
>  
> <
> https://groups.google.com/d/msgid/pylons-discuss/d0a0d404-f081-41f8-865f-b073ed17bc78n%40googlegroups.com?utm_medium=email_source=footer
> >.
> >>>
> >>> --
> >>> 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 view this discussion on the web visit 
> https://groups.google.com/d/msgid/pylons-discuss/6f0f2332-daa6-70a1-f148-2b32abdbb459%40gmail.com
> .
> >
> > --
> > 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 view this discussion on the web visit 
> https://groups.google.com/d/msgid/pylons-discuss/1d1850a5-2e49-47f3-835d-c44a6595c60an%40googlegroups.com
> .
>
>
>
> -- 
> Mike Orr 
>

-- 
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-discuss+unsubscr...@googlegroups.com.
To view this discussion on the web visit