Re: [ansible-devel] Is changing the default setting of TRANSFORM_INVALID_GROUP_CHARS a good idea?

2019-08-23 Thread Jeff Geerling
I think part of the problem is the confusion as to whether or not dashes would be completely unsupported after 2.11, and it's good to know that is resolved. However, having to set a variable with "invalid" in the name makes it sound like "you are doing something wrong"... and afaict, dashes

Re: [ansible-devel] Is changing the default setting of TRANSFORM_INVALID_GROUP_CHARS a good idea?

2019-08-23 Thread Brian Coca
On Friday, August 23, 2019 at 9:23:45 AM UTC-4, Jeff Geerling wrote: > It feels like the war on dashes has spilled over from roles (then collections) to now group naming conventions. I can empathize with the 'feeling' but the reality is that this has more to do with underlying tools used

Re: [ansible-devel] Is changing the default setting of TRANSFORM_INVALID_GROUP_CHARS a good idea?

2019-08-23 Thread Kai Stian Olstad
On 23.08.2019 23:12, Steve Kieu wrote: Except for the wrong way of using it by dot notation - which is wrong in my opinion as it is not an complex object type (an instance of a class) but simply a dict, there is no reason to use dot notation to access a dict value. Python does not allow it,

Re: [ansible-devel] Is changing the default setting of TRANSFORM_INVALID_GROUP_CHARS a good idea?

2019-08-23 Thread Steve Kieu
There are many comments already so I just want to be short. Please correct if I am wrong in understanding that based on your comment, you think - allowing hyphen in group name is broken. And I can not find a good rationale for that yet still. Except for the wrong way of using it by dot