Re: [pylons-devel] Re: pcreate: Uppercase version of the package name?

2014-11-28 Thread Torsten Irländer
2014-11-25 17:14 GMT+01:00 Jonathan Vanasco :

> I would create an Issue and propose it on the Github.  One of the core
> maintainers will say something like "Great!", "Maybe..." or  "No way".
> I've seen (and personally gotten) a lot more "No Way" than "Okay" for
> proposed changes.
>
> This is such an edge case though, that I don't know if they'll go for it
> "as-is".  Why would other people need or use this?  I don't see it getting
> added unless you can come up with a compelling reason.
>

Jonathan , Thank you for your answer. As Michael writes there is no need
for me to change anything in the pcreate command.

-- 
You received this message because you are subscribed to the Google Groups 
"pylons-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to pylons-devel+unsubscr...@googlegroups.com.
To post to this group, send email to pylons-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/pylons-devel.
For more options, visit https://groups.google.com/d/optout.


Re: [pylons-devel] Re: pcreate: Uppercase version of the package name?

2014-11-28 Thread Torsten Irländer
A great! Thank you Michael for the hint. It works perfect for me.

2014-11-25 17:50 GMT+01:00 Michael Merickel :

> AFAIK all of the things you are asking for are possible using the
> (documented) scaffolding API. You basically just subclass
> ``PyramidTemplate`` and override ``pre`` to mutate the ``vars`` and
> add what you like.
>
>
> http://docs.pylonsproject.org/projects/pyramid/en/1.5-branch/narr/scaffolding.html
>
>
> http://docs.pylonsproject.org/projects/pyramid/en/1.5-branch/api/scaffolds.html#pyramid.scaffolds.PyramidTemplate.pre
>
> On Tue, Nov 25, 2014 at 10:14 AM, Jonathan Vanasco
>  wrote:
> > I would create an Issue and propose it on the Github.  One of the core
> > maintainers will say something like "Great!", "Maybe..." or  "No way".
> I've
> > seen (and personally gotten) a lot more "No Way" than "Okay" for proposed
> > changes.
> >
> > This is such an edge case though, that I don't know if they'll go for it
> > "as-is".  Why would other people need or use this?  I don't see it
> getting
> > added unless you can come up with a compelling reason.
> >
> > This is purely a guess - but I think you might have better luck
> proposing it
> > as some sort of "hook" for pcreate.  i.e., if there was some way to pass
> in
> > other template variables to pcreate.
> >
> >
> > --
> > You received this message because you are subscribed to the Google Groups
> > "pylons-devel" group.
> > To unsubscribe from this group and stop receiving emails from it, send an
> > email to pylons-devel+unsubscr...@googlegroups.com.
> > To post to this group, send email to pylons-devel@googlegroups.com.
> > Visit this group at http://groups.google.com/group/pylons-devel.
> > For more options, visit https://groups.google.com/d/optout.
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "pylons-devel" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/pylons-devel/umFqVR6KmKo/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> pylons-devel+unsubscr...@googlegroups.com.
> To post to this group, send email to pylons-devel@googlegroups.com.
> Visit this group at http://groups.google.com/group/pylons-devel.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"pylons-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to pylons-devel+unsubscr...@googlegroups.com.
To post to this group, send email to pylons-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/pylons-devel.
For more options, visit https://groups.google.com/d/optout.


Re: [pylons-devel] Re: pcreate: Uppercase version of the package name?

2014-11-25 Thread Michael Merickel
AFAIK all of the things you are asking for are possible using the
(documented) scaffolding API. You basically just subclass
``PyramidTemplate`` and override ``pre`` to mutate the ``vars`` and
add what you like.

http://docs.pylonsproject.org/projects/pyramid/en/1.5-branch/narr/scaffolding.html

http://docs.pylonsproject.org/projects/pyramid/en/1.5-branch/api/scaffolds.html#pyramid.scaffolds.PyramidTemplate.pre

On Tue, Nov 25, 2014 at 10:14 AM, Jonathan Vanasco
 wrote:
> I would create an Issue and propose it on the Github.  One of the core
> maintainers will say something like "Great!", "Maybe..." or  "No way".  I've
> seen (and personally gotten) a lot more "No Way" than "Okay" for proposed
> changes.
>
> This is such an edge case though, that I don't know if they'll go for it
> "as-is".  Why would other people need or use this?  I don't see it getting
> added unless you can come up with a compelling reason.
>
> This is purely a guess - but I think you might have better luck proposing it
> as some sort of "hook" for pcreate.  i.e., if there was some way to pass in
> other template variables to pcreate.
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "pylons-devel" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to pylons-devel+unsubscr...@googlegroups.com.
> To post to this group, send email to pylons-devel@googlegroups.com.
> Visit this group at http://groups.google.com/group/pylons-devel.
> For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups 
"pylons-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to pylons-devel+unsubscr...@googlegroups.com.
To post to this group, send email to pylons-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/pylons-devel.
For more options, visit https://groups.google.com/d/optout.


Re: [pylons-devel] Re: pcreate: Uppercase version of the package name?

2014-11-25 Thread Jonathan Vanasco
I would create an Issue and propose it on the Github.  One of the core 
maintainers will say something like "Great!", "Maybe..." or  "No way". 
 I've seen (and personally gotten) a lot more "No Way" than "Okay" for 
proposed changes.

This is such an edge case though, that I don't know if they'll go for it 
"as-is".  Why would other people need or use this?  I don't see it getting 
added unless you can come up with a compelling reason.

This is purely a guess - but I think you might have better luck proposing 
it as some sort of "hook" for pcreate.  i.e., if there was some way to pass 
in other template variables to pcreate.  


-- 
You received this message because you are subscribed to the Google Groups 
"pylons-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to pylons-devel+unsubscr...@googlegroups.com.
To post to this group, send email to pylons-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/pylons-devel.
For more options, visit https://groups.google.com/d/optout.


Re: [pylons-devel] Re: pcreate: Uppercase version of the package name?

2014-11-25 Thread Torsten Irländer
Thanks for the reply Jonathan,

I knew the "project" variable, but as you mention is keeps the name is it
was entered. Well I think I will monkeypatch this one for my need.

But how is the common workflow if I want to get this upstream?
1. Create an Issue
2. Patch
3. Pull-Request?

Torsten

2014-11-21 0:42 GMT+01:00 Jonathan Vanasco :

> You might be able to use the "Project" variable, if you pass in a
> Capitalized form
>
> $ pcreate --scaffold starter Foo
> > 'project': Foo,
> > 'package': foo,
>
> Note that this doesn't "Capitalize" the name.  it keeps it as-is:
>
> $ pcreate --scaffold starter FooBarBash
> > 'project': FooBarBash,
> > 'package': foobarbash,
>
>
> Otherwise you'd have to patch or monkeypatch pcreate.py in order to do
> that:
>
>
> https://github.com/Pylons/pyramid/blob/master/pyramid/scripts/pcreate.py#L106-L112
>
>  --
> You received this message because you are subscribed to a topic in the
> Google Groups "pylons-devel" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/pylons-devel/umFqVR6KmKo/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> pylons-devel+unsubscr...@googlegroups.com.
> To post to this group, send email to pylons-devel@googlegroups.com.
> Visit this group at http://groups.google.com/group/pylons-devel.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"pylons-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to pylons-devel+unsubscr...@googlegroups.com.
To post to this group, send email to pylons-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/pylons-devel.
For more options, visit https://groups.google.com/d/optout.