Re: [pylons-discuss] is it possible to 'nest' a pyramid application within a larger library?

[Jonathan Vanasco]

thank you! 

On Monday, January 27, 2020 at 5:41:42 PM UTC-5, Theron Luhn wrote:
>
> Your setup.py is correct.
>
> In the ini file, `use` points not to a module but an entry point.  
>

-- 
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/7df57ab7-b9c6-4bf0-b1e2-b37b495eefe4%40googlegroups.com.

Re: [pylons-discuss] is it possible to 'nest' a pyramid application within a larger library?

[Theron Luhn]

Your setup.py is correct.

In the ini file, `use` points not to a module but an entry point.  So it should 
be `use = egg:myapp#main`

— Theron



> On Jan 27, 2020, at 2:37 PM, Jonathan Vanasco  wrote:
> 
> wow. it would be great if I can get this to work then.  this package started 
> out as a pyramid app, but now the pyramid/web usage is 1/3 of typical usage 
> patterns (it also has a terminal console and a python developer library).  
> i'd prefer to restructure the distribution so the pyramid-only stuff is 
> reorganized under "web".
> 
> I can't match up the right combo of these 2 things into something that will 
> install/run.  i assume these are what I need to configure:
> 
> environment.ini
>   [app:main]
>   use = egg:myapp.web
> 
> setup.py
>   [paste.app_factory]
>   main =  myapp.web:main
> 
> 
> 
> On Monday, January 27, 2020 at 3:44:11 PM UTC-5, Theron Luhn wrote:
> This is totally possible.  I actually have a live application that’s set up 
> in much the same way.  (Pyramid app nested inside another Pyramid app.)
> 
> It was pretty straightforward when I did it, I don’t think there’s any 
> assumptions made about where the application lives.  What particular troubles 
> you’re having?
> 
> — Theron
> 
> 
> 
>> On Jan 27, 2020, at 12:37 PM, Jonathan Vanasco > 
>> wrote:
>> 
>> does anyone know if it possible to nest a pyramid application within a 
>> larger library?
>> 
>> for example, I would like a Pyramid application's root to be `myapp.web`, 
>> instead of `myapp`.  
>> 
>> I don't think this is possible, which is fine - I can just split the pyramid 
>> app into a separate package.
>> 
>> 
>> -- 
>> 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-...@googlegroups.com <>.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/pylons-discuss/66bd44da-f33b-44db-b479-b5d060091067%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/ba721314-be8b-481e-a686-8dfe05f2ef25%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/696E60DC-CD8E-4EE2-932E-5C71AC79B999%40luhn.com.

Re: [pylons-discuss] is it possible to 'nest' a pyramid application within a larger library?

[Jonathan Vanasco]

wow. it would be great if I can get this to work then.  this package 
started out as a pyramid app, but now the pyramid/web usage is 1/3 of 
typical usage patterns (it also has a terminal console and a python 
developer library).  i'd prefer to restructure the distribution so the 
pyramid-only stuff is reorganized under "web".

I can't match up the right combo of these 2 things into something that will 
install/run.  i assume these are what I need to configure:

environment.ini
  [app:main]
  use = egg:myapp.web

setup.py
  [paste.app_factory]
  main =  myapp.web:main



On Monday, January 27, 2020 at 3:44:11 PM UTC-5, Theron Luhn wrote:
>
> This is totally possible.  I actually have a live application that’s set 
> up in much the same way.  (Pyramid app nested inside another Pyramid app.)
>
> It was pretty straightforward when I did it, I don’t think there’s any 
> assumptions made about where the application lives.  What particular 
> troubles you’re having?
>
> — Theron
>
>
>
> On Jan 27, 2020, at 12:37 PM, Jonathan Vanasco  > wrote:
>
> does anyone know if it possible to nest a pyramid application within a 
> larger library?
>
> for example, I would like a Pyramid application's root to be `myapp.web`, 
> instead of `myapp`.  
>
> I don't think this is possible, which is fine - I can just split the 
> pyramid app into a separate package.
>
>
> -- 
> 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-...@googlegroups.com .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/pylons-discuss/66bd44da-f33b-44db-b479-b5d060091067%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/ba721314-be8b-481e-a686-8dfe05f2ef25%40googlegroups.com.

Re: [pylons-discuss] is it possible to 'nest' a pyramid application within a larger library?

[Theron Luhn]

This is totally possible.  I actually have a live application that’s set up in 
much the same way.  (Pyramid app nested inside another Pyramid app.)

It was pretty straightforward when I did it, I don’t think there’s any 
assumptions made about where the application lives.  What particular troubles 
you’re having?

— Theron



> On Jan 27, 2020, at 12:37 PM, Jonathan Vanasco  wrote:
> 
> does anyone know if it possible to nest a pyramid application within a larger 
> library?
> 
> for example, I would like a Pyramid application's root to be `myapp.web`, 
> instead of `myapp`.  
> 
> I don't think this is possible, which is fine - I can just split the pyramid 
> app into a separate package.
> 
> 
> -- 
> 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/66bd44da-f33b-44db-b479-b5d060091067%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/28519279-604D-4A85-A24F-8617F1D93D78%40luhn.com.

[pylons-discuss] is it possible to 'nest' a pyramid application within a larger library?

[Jonathan Vanasco]

does anyone know if it possible to nest a pyramid application within a 
larger library?

for example, I would like a Pyramid application's root to be `myapp.web`, 
instead of `myapp`.  

I don't think this is possible, which is fine - I can just split the 
pyramid app into a separate package.

-- 
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/66bd44da-f33b-44db-b479-b5d060091067%40googlegroups.com.