Re: [Maya-Python] pep 8 nameing convention for packages and modules

On Mon, Sep 26, 2016 at 11:53 AM Alok Gandhi wrote: > Thanks Alok. >> See, some people think that, because they have a lot experience and >> talent(like marcus, and obviously he is very talented), they have they >> right to insult, using sarcastic comments, the people

Re: [Maya-Python] pep 8 nameing convention for packages and modules

> > Thanks Alok. > See, some people think that, because they have a lot experience and > talent(like marcus, and obviously he is very talented), they have they > right to insult, using sarcastic comments, the people who are learning and > asking questions. > ( or maybe it is just with me, who

Re: [Maya-Python] pep 8 nameing convention for packages and modules

Hey Rudi On Mon, 26 Sep 2016, 4:45 AM Rudi Hammad wrote: > Thanks Alok. > > See, some people think that, because they have a lot experience and > talent(like marcus, and obviously he is very talented), they have they > right to insult, using sarcastic comments, the people

Re: [Maya-Python] pep 8 nameing convention for packages and modules

Thanks Alok. See, some people think that, because they have a lot experience and talent(like marcus, and obviously he is very talented), they have they right to insult, using sarcastic comments, the people who are learning and asking questions. ( or maybe it is just with me, who knows). I am

Re: [Maya-Python] pep 8 nameing convention for packages and modules

If you have chosen the style, such as strawberry, preferred by the highest percentage of your family, then you are doing it right. :) strawberry: 7/10 <- winner! pear: 2/10 marmite: 1/10 ​ -- You received this message because you are subscribed to the Google Groups "Python Programming for

Re: [Maya-Python] pep 8 nameing convention for packages and modules

> > And I don´t think it is uglier Both are readable for sure, I agree, 120 is not bad at all. It is good to see that you put some thought not only what your code does but also how does it look. Just another piece of advise - For the perspective of version control system in particular, there is

Re: [Maya-Python] pep 8 nameing convention for packages and modules

> > Strawberry isn't wrong. But tastes differ, and best you can do is cook > something that the largest amount of family members will like. @marcus: My apologies but I fail to get the point. Is it for or against the use of PEP-8? On Sun, Sep 25, 2016 at 10:35 PM, Marcus Ottosson

Re: [Maya-Python] pep 8 nameing convention for packages and modules

I like strawberry. I think strawberry is the best flavour. It tastes good, has the right nutrition and makes every dish I make taste good too. For my family of 10, I will make strawberry meals all day because it is what I prefer. I don't care about what the others like, because they don't share

Re: [Maya-Python] pep 8 nameing convention for packages and modules

Your explanation is very reasonable. I try to write code in a beautiful and readable way always, This is a test to compare. PEP-8 3. Inside strings too: class MyClass(object): def someMethod( some_big_argument_name, another_big_argument,

Re: [Maya-Python] pep 8 nameing convention for packages and modules

> > The 80 characters per line, is definitely crazy When I started programming in python (and that was about 10 years ago) I thought the same. More so, when we have four spaces per indent. But then, now I am completely comfortable with 80 characters per line. There are ways to get your code to

Re: [Maya-Python] pep 8 nameing convention for packages and modules

About style, that is all fine. But if you're in a team, maybe try to think less about what you prefer, and consider the preference of those reading, and potentially maintaining your code.​ Even amazing programmers will appreciate having their preference considered. -- You received this message

Re: [Maya-Python] pep 8 nameing convention for packages and modules

yes, the rb prefix is annoying. I think it makes more cense put all the modules together intead of diferent packages. So the main package would be rigbuilder, and the modules would be guides and skeleton. I will maintain solutions as a package tough. (I can' t remove classes because the code

Re: [Maya-Python] pep 8 nameing convention for packages and modules

Consider how it would affect the readability of your project if you: a) removed the rb prefix and b) made each class into a module At the moment, rb is used as a namespace. In languages such as C, you need those to avoid nameclashes and to make your code look readable. But Python has a nicer way

Re: [Maya-Python] pep 8 nameing convention for packages and modules

wow, I am so glad I asked. It very interesting your points of view, and very clarifying. Let me be a little more specific, because that might change some things. I set my maya environment root to a folder called --> rigbuilder. So this is just a folder, no package. Then inside, I have 3

Re: [Maya-Python] pep 8 nameing convention for packages and modules

I agree too. Based on limited knowledge of what you’re up to, here’s how I might have expected it to look. from rigbuilder import skeleton skeleton.build() - No acronyms - package and modules are included in how you read the code - functions for verbs (classes for names of things)

Re: [Maya-Python] pep 8 nameing convention for packages and modules

> > I think "Build" is a strange name for a class @justin: I agree 100%, taking my word back, Builder is anyday a better name that Build for a class, I think I was focussing more on the package naming conventions as whole not just the class. And here's the more precise rule - "Class names

Re: [Maya-Python] pep 8 nameing convention for packages and modules

I think "Build" is a strange name for a class though, since it implies an action such as something a function should do. But calling a class means calling its contructor. Would a more appropriate name be "Builder" since a class would be a collection of logic that can be used to build a Skeleton?

Re: [Maya-Python] pep 8 nameing convention for packages and modules

> > But a class named Skeleton is more descriptive than Build. Of ourse it is, but only if you do not have a namespace context. I totally agree with Yury here. Your namespace already qualifies what Build class is, so you do not have to worry about the context. Always remeber - Namespaces are

Re: [Maya-Python] pep 8 nameing convention for packages and modules

hmmm, interesting. But a class named Skeleton is more descriptive than Build. I might be overthinking all that, but I am curious about it. El sábado, 24 de septiembre de 2016, 19:47:28 (UTC+1), ynedelin escribió: > > You could use Build instead of Skeleton. > This would make sense since you

Re: [Maya-Python] pep 8 nameing convention for packages and modules

You could use Build instead of Skeleton. This would make sense since you already have skeleton in the rbskeleton, then you will have rbs.Build() It would also work well with other functions like rbs.Destroy() On Sep 24, 2016 12:20 PM, "Rudi Hammad" wrote: > Hi, > so I guess