From glen at glenjarvis.com Mon Jan 2 01:18:01 2017 From: glen at glenjarvis.com (Glen Jarvis) Date: Sun, 1 Jan 2017 22:18:01 -0800 Subject: [Baypiggies] BayPIGgies - a year later / Progress in 2017 / KUDOS to Jeff - he's so awesome! Message-ID: Year 2016 was quite a dramatic and difficult year for BAyPIGgies. Exactly one year ago, there was confusion about the control of the MeetUp site and potential dues being charged. Because the MeetUp site was set to charge dues (not something that we agreed to), and because we had lost some control of the site, we saw many members being automatically removed from the MeetUp group. Our MeetUp membership dropped from many thousands to a small handful. However, we have been a group long before MeetUp (an awesome disruptive tool in this space) was even around. And, we decided to focus on our purpose and what we have always done: Bring speakers and an audience together around the subject of Python. This brought out the best in us. Volunteers from our community came together and pulled together like never before. We had help in everything from greeters to help people find the room to metric managers. For example, Grant Ridder completely owned the attendance numbers so we have metrics on our growth. We were able to get over 100 people together for that first January meeting. We were also able to sort out the MeetUp control issues as well. And, our MeetUp numbers rebooted. We started with just a handful and, one year later, we now have 1,559 members registered for the MeetUp site. None of this would have been possible if it weren't for one member of our community: Jeff Fischer. Jeff owned the lion's share of work. He helped get speakers, he ran the full meetings, and he was at the "helm of the ship" for months at a time completely by himself. And, not once did he complain. He gave so much of himself to this community and is continuing to give more this year. I am so lucky to be part of this open source community. People often ask, "I want to participate more in Open Source, but I don't know what to do." There is always something that we can do to help our community, and we don't have to be the most experienced coders to do it. I believe the year 2017 will be even better for us. There is only one change that we're implementing this year. Our audience interest pool seems focused around three main areas: 1. New Learners - growing a new community of programmers 2. Data Science - Python has exploded in this area and we have a great deal of interest here 3. Advanced topics - Our core audience, that has been around for many years has interest in those advanced talks, for example, talks from Alex or Guido. To keep talks that appeal to our audience balanced, we will try to organize our talks in this manner: January: Beginner talk February: Data Science talk March: Advanced talk April: Beginner talk... etc. To kick this off, we have our first beginner talk: Python Buzzwords by Charles Merriam. Please RSVP today: https://www.meetup.com/BAyPIGgies/events/233553028/ I look forward to another great year with a great community. In awe of being here, Glen Jarvis -------------- next part -------------- An HTML attachment was scrubbed... URL: From jeffrey.fischer at gmail.com Mon Jan 2 13:07:51 2017 From: jeffrey.fischer at gmail.com (Jeff Fischer) Date: Mon, 2 Jan 2017 10:07:51 -0800 Subject: [Baypiggies] BayPIGgies - a year later / Progress in 2017 / KUDOS to Jeff - he's so awesome! In-Reply-To: References: Message-ID: Happy New Year! I'm looking forward to another great year of talks. I think 2016 turned out great for BayPiggies, in spite of the rough start. Thanks, Glen for the kind words, for all your help, and for using your extensive connections to line up great speakers. A thanks also to: - Bill Deegan for redoing the baypiggies.net website - All those who helped with logistics at the meetings - LinkedIn for hosting us and providing food - Everyone for coming to the meetings, providing a lot of positive energy for the speakers, and asking great questions Here's to a great 2017! See you all on the 26th (note it will be back to the normal 4th Thursday). Regards, Jeff On Sun, Jan 1, 2017 at 10:18 PM, Glen Jarvis wrote: > Year 2016 was quite a dramatic and difficult year for BAyPIGgies. Exactly > one year ago, there was confusion about the control of the MeetUp site and > potential dues being charged. Because the MeetUp site was set to charge > dues (not something that we agreed to), and because we had lost some > control of the site, we saw many members being automatically removed from > the MeetUp group. Our MeetUp membership dropped from many thousands to a > small handful. > > However, we have been a group long before MeetUp (an awesome disruptive > tool in this space) was even around. And, we decided to focus on our > purpose and what we have always done: Bring speakers and an audience > together around the subject of Python. > > This brought out the best in us. Volunteers from our community came > together and pulled together like never before. We had help in everything > from greeters to help people find the room to metric managers. For example, > Grant Ridder completely owned the attendance numbers so we have metrics on > our growth. > > We were able to get over 100 people together for that first January > meeting. We were also able to sort out the MeetUp control issues as well. > And, our MeetUp numbers rebooted. We started with just a handful and, one > year later, we now have 1,559 members registered for the MeetUp site. > > None of this would have been possible if it weren't for one member of our > community: Jeff Fischer. Jeff owned the lion's share of work. He helped get > speakers, he ran the full meetings, and he was at the "helm of the ship" > for months at a time completely by himself. And, not once did he complain. > He gave so much of himself to this community and is continuing to give more > this year. > > I am so lucky to be part of this open source community. People often ask, > "I want to participate more in Open Source, but I don't know what to do." > There is always something that we can do to help our community, and we > don't have to be the most experienced coders to do it. > > I believe the year 2017 will be even better for us. There is only one > change that we're implementing this year. Our audience interest pool seems > focused around three main areas: > > 1. New Learners - growing a new community of programmers > 2. Data Science - Python has exploded in this area and we have a great > deal of interest here > 3. Advanced topics - Our core audience, that has been around for many > years has interest in those advanced talks, for example, talks from Alex > or Guido. > > To keep talks that appeal to our audience balanced, we will try to > organize our talks in this manner: > > January: Beginner talk > February: Data Science talk > March: Advanced talk > April: Beginner talk... > etc. > > To kick this off, we have our first beginner talk: Python Buzzwords by > Charles Merriam. > > > Please RSVP today: > > https://www.meetup.com/BAyPIGgies/events/233553028/ > > > > I look forward to another great year with a great community. > > > In awe of being here, > > > Glen Jarvis > > _______________________________________________ > Baypiggies mailing list > Baypiggies at python.org > To change your subscription options or unsubscribe: > https://mail.python.org/mailman/listinfo/baypiggies > -------------- next part -------------- An HTML attachment was scrubbed... URL: From deirdre at deirdre.net Mon Jan 2 16:47:05 2017 From: deirdre at deirdre.net (Deirdre Saoirse Moen) Date: Mon, 2 Jan 2017 13:47:05 -0800 Subject: [Baypiggies] BayPIGgies - a year later / Progress in 2017 / KUDOS to Jeff - he's so awesome! In-Reply-To: References: Message-ID: <6C592A85-0B80-4008-A3FA-D912D3F45082@deirdre.net> I want to thank all for taking this little group I started in 1999, keeping it going, and making it far bigger than I ever did. Deirdre > On Jan 2, 2017, at 10:07 AM, Jeff Fischer wrote: > > Happy New Year! > > I'm looking forward to another great year of talks. I think 2016 turned out great for BayPiggies, in spite of the rough start. Thanks, Glen for the kind words, for all your help, and for using your extensive connections to line up great speakers. A thanks also to: > Bill Deegan for redoing the baypiggies.net website > All those who helped with logistics at the meetings > LinkedIn for hosting us and providing food > Everyone for coming to the meetings, providing a lot of positive energy for the speakers, and asking great questions > > Here's to a great 2017! See you all on the 26th (note it will be back to the normal 4th Thursday). > > Regards, > Jeff > >> On Sun, Jan 1, 2017 at 10:18 PM, Glen Jarvis wrote: >> Year 2016 was quite a dramatic and difficult year for BAyPIGgies. Exactly one year ago, there was confusion about the control of the MeetUp site and potential dues being charged. Because the MeetUp site was set to charge dues (not something that we agreed to), and because we had lost some control of the site, we saw many members being automatically removed from the MeetUp group. Our MeetUp membership dropped from many thousands to a small handful. >> >> However, we have been a group long before MeetUp (an awesome disruptive tool in this space) was even around. And, we decided to focus on our purpose and what we have always done: Bring speakers and an audience together around the subject of Python. >> >> This brought out the best in us. Volunteers from our community came together and pulled together like never before. We had help in everything from greeters to help people find the room to metric managers. For example, Grant Ridder completely owned the attendance numbers so we have metrics on our growth. >> >> We were able to get over 100 people together for that first January meeting. We were also able to sort out the MeetUp control issues as well. And, our MeetUp numbers rebooted. We started with just a handful and, one year later, we now have 1,559 members registered for the MeetUp site. >> >> None of this would have been possible if it weren't for one member of our community: Jeff Fischer. Jeff owned the lion's share of work. He helped get speakers, he ran the full meetings, and he was at the "helm of the ship" for months at a time completely by himself. And, not once did he complain. He gave so much of himself to this community and is continuing to give more this year. >> >> I am so lucky to be part of this open source community. People often ask, "I want to participate more in Open Source, but I don't know what to do." There is always something that we can do to help our community, and we don't have to be the most experienced coders to do it. >> >> I believe the year 2017 will be even better for us. There is only one change that we're implementing this year. Our audience interest pool seems focused around three main areas: >> >> 1. New Learners - growing a new community of programmers >> 2. Data Science - Python has exploded in this area and we have a great deal of interest here >> 3. Advanced topics - Our core audience, that has been around for many years has interest in those advanced talks, for example, talks from Alex or Guido. >> >> To keep talks that appeal to our audience balanced, we will try to organize our talks in this manner: >> >> January: Beginner talk >> February: Data Science talk >> March: Advanced talk >> April: Beginner talk... >> etc. >> >> To kick this off, we have our first beginner talk: Python Buzzwords by Charles Merriam. >> >> >> Please RSVP today: >> >> https://www.meetup.com/BAyPIGgies/events/233553028/ >> >> >> >> I look forward to another great year with a great community. >> >> >> In awe of being here, >> >> >> Glen Jarvis >> >> _______________________________________________ >> Baypiggies mailing list >> Baypiggies at python.org >> To change your subscription options or unsubscribe: >> https://mail.python.org/mailman/listinfo/baypiggies > > _______________________________________________ > Baypiggies mailing list > Baypiggies at python.org > To change your subscription options or unsubscribe: > https://mail.python.org/mailman/listinfo/baypiggies -------------- next part -------------- An HTML attachment was scrubbed... URL: From guido at python.org Mon Jan 2 17:01:54 2017 From: guido at python.org (Guido van Rossum) Date: Mon, 2 Jan 2017 14:01:54 -0800 Subject: [Baypiggies] BayPIGgies - a year later / Progress in 2017 / KUDOS to Jeff - he's so awesome! In-Reply-To: <6C592A85-0B80-4008-A3FA-D912D3F45082@deirdre.net> References: <6C592A85-0B80-4008-A3FA-D912D3F45082@deirdre.net> Message-ID: Thanks for creating BayPiggies, Deirdre! And thanks to all piggies for being my greatest audience. --Guido On Mon, Jan 2, 2017 at 1:47 PM, Deirdre Saoirse Moen wrote: > I want to thank all for taking this little group I started in 1999, > keeping it going, and making it far bigger than I ever did. > > Deirdre > > On Jan 2, 2017, at 10:07 AM, Jeff Fischer > wrote: > > Happy New Year! > > I'm looking forward to another great year of talks. I think 2016 turned > out great for BayPiggies, in spite of the rough start. Thanks, Glen for the > kind words, for all your help, and for using your extensive connections to > line up great speakers. A thanks also to: > > - Bill Deegan for redoing the baypiggies.net website > - All those who helped with logistics at the meetings > - LinkedIn for hosting us and providing food > - Everyone for coming to the meetings, providing a lot of positive > energy for the speakers, and asking great questions > > > Here's to a great 2017! See you all on the 26th (note it will be back to > the normal 4th Thursday). > > Regards, > Jeff > > On Sun, Jan 1, 2017 at 10:18 PM, Glen Jarvis wrote: > >> Year 2016 was quite a dramatic and difficult year for BAyPIGgies. Exactly >> one year ago, there was confusion about the control of the MeetUp site and >> potential dues being charged. Because the MeetUp site was set to charge >> dues (not something that we agreed to), and because we had lost some >> control of the site, we saw many members being automatically removed from >> the MeetUp group. Our MeetUp membership dropped from many thousands to a >> small handful. >> >> However, we have been a group long before MeetUp (an awesome disruptive >> tool in this space) was even around. And, we decided to focus on our >> purpose and what we have always done: Bring speakers and an audience >> together around the subject of Python. >> >> This brought out the best in us. Volunteers from our community came >> together and pulled together like never before. We had help in everything >> from greeters to help people find the room to metric managers. For example, >> Grant Ridder completely owned the attendance numbers so we have metrics on >> our growth. >> >> We were able to get over 100 people together for that first January >> meeting. We were also able to sort out the MeetUp control issues as well. >> And, our MeetUp numbers rebooted. We started with just a handful and, one >> year later, we now have 1,559 members registered for the MeetUp site. >> >> None of this would have been possible if it weren't for one member of our >> community: Jeff Fischer. Jeff owned the lion's share of work. He helped get >> speakers, he ran the full meetings, and he was at the "helm of the ship" >> for months at a time completely by himself. And, not once did he complain. >> He gave so much of himself to this community and is continuing to give more >> this year. >> >> I am so lucky to be part of this open source community. People often ask, >> "I want to participate more in Open Source, but I don't know what to do." >> There is always something that we can do to help our community, and we >> don't have to be the most experienced coders to do it. >> >> I believe the year 2017 will be even better for us. There is only one >> change that we're implementing this year. Our audience interest pool seems >> focused around three main areas: >> >> 1. New Learners - growing a new community of programmers >> 2. Data Science - Python has exploded in this area and we have a great >> deal of interest here >> 3. Advanced topics - Our core audience, that has been around for many >> years has interest in those advanced talks, for example, talks from Alex >> or Guido. >> >> To keep talks that appeal to our audience balanced, we will try to >> organize our talks in this manner: >> >> January: Beginner talk >> February: Data Science talk >> March: Advanced talk >> April: Beginner talk... >> etc. >> >> To kick this off, we have our first beginner talk: Python Buzzwords by >> Charles Merriam. >> >> >> Please RSVP today: >> >> https://www.meetup.com/BAyPIGgies/events/233553028/ >> >> >> >> I look forward to another great year with a great community. >> >> >> In awe of being here, >> >> >> Glen Jarvis >> >> _______________________________________________ >> Baypiggies mailing list >> Baypiggies at python.org >> To change your subscription options or unsubscribe: >> https://mail.python.org/mailman/listinfo/baypiggies >> > > _______________________________________________ > Baypiggies mailing list > Baypiggies at python.org > To change your subscription options or unsubscribe: > https://mail.python.org/mailman/listinfo/baypiggies > > > _______________________________________________ > Baypiggies mailing list > Baypiggies at python.org > To change your subscription options or unsubscribe: > https://mail.python.org/mailman/listinfo/baypiggies > -- --Guido van Rossum (python.org/~guido) -------------- next part -------------- An HTML attachment was scrubbed... URL: From bbrelin at gmail.com Wed Jan 4 12:30:06 2017 From: bbrelin at gmail.com (Braun Brelin) Date: Wed, 4 Jan 2017 19:30:06 +0200 Subject: [Baypiggies] Question on Python's MRO... Message-ID: Hi all, I'm trying to figure out how to understand Python's Method Resolution order. One of the things that's really confusing me is that from my understanding if I have a class declaration like this class C(A,B): ... Python does the inheritance order from right to left, yet all the tutorials on MRO start talking about inheritance from left to right. Is the right to left order a property of the older Python 2 style classes that didn't explicitly inherit from object? Thanks -------------- next part -------------- An HTML attachment was scrubbed... URL: From guido at python.org Wed Jan 4 12:37:17 2017 From: guido at python.org (Guido van Rossum) Date: Wed, 4 Jan 2017 09:37:17 -0800 Subject: [Baypiggies] Question on Python's MRO... In-Reply-To: References: Message-ID: C's MRO is (C, A, B, object), and method lookup happens in that order. So if both A and B define a method m, but C doesn't, A.m gets used. For old-style classes the lookup order would still be (C, A, B). Maybe you can clarify *what* is happening from right to left in your understanding? Code speaks! On Wed, Jan 4, 2017 at 9:30 AM, Braun Brelin wrote: > Hi all, > > I'm trying to figure out how to understand Python's Method Resolution > order. > One of the things that's really confusing me is that from my understanding > if I have a class declaration like this > > class C(A,B): > ... > > Python does the inheritance order from right to left, yet all the > tutorials on MRO > start talking about inheritance from left to right. > > Is the right to left order a property of the older Python 2 style classes > that didn't > explicitly inherit from object? > > Thanks > > > > _______________________________________________ > Baypiggies mailing list > Baypiggies at python.org > To change your subscription options or unsubscribe: > https://mail.python.org/mailman/listinfo/baypiggies > -- --Guido van Rossum (python.org/~guido) -------------- next part -------------- An HTML attachment was scrubbed... URL: From bbrelin at gmail.com Wed Jan 4 13:07:19 2017 From: bbrelin at gmail.com (Braun Brelin) Date: Wed, 4 Jan 2017 20:07:19 +0200 Subject: [Baypiggies] Question on Python's MRO... In-Reply-To: References: Message-ID: What I'm confused about is the following: #!/usr/bin/env python3 class mixin1(object): def foo(self): print ("In mixin1.foo()") class mixin2 (object): def foo(self): print ("In mixin2.foo()") class A(object): def __init__(self): print ("In class A") class B(A,mixin1,mixin2): def __init__(self): self.foo() myB = B() -------------------------------------------------------------------------------------------------------------- The output of this program is: In mixin1.foo() So, it seems to be doing method resolution from right to left. No? Braun I've always understood that the class hierarchy when determining inheritance is that Python looks at class mixin2 first, then class mixin1, then the base class A. I.e. the order is right to left. A number of web site On Wed, Jan 4, 2017 at 7:37 PM, Guido van Rossum wrote: > C's MRO is (C, A, B, object), and method lookup happens in that order. So > if both A and B define a method m, but C doesn't, A.m gets used. > > For old-style classes the lookup order would still be (C, A, B). > > Maybe you can clarify *what* is happening from right to left in your > understanding? Code speaks! > > On Wed, Jan 4, 2017 at 9:30 AM, Braun Brelin wrote: > >> Hi all, >> >> I'm trying to figure out how to understand Python's Method Resolution >> order. >> One of the things that's really confusing me is that from my understanding >> if I have a class declaration like this >> >> class C(A,B): >> ... >> >> Python does the inheritance order from right to left, yet all the >> tutorials on MRO >> start talking about inheritance from left to right. >> >> Is the right to left order a property of the older Python 2 style classes >> that didn't >> explicitly inherit from object? >> >> Thanks >> >> >> >> _______________________________________________ >> Baypiggies mailing list >> Baypiggies at python.org >> To change your subscription options or unsubscribe: >> https://mail.python.org/mailman/listinfo/baypiggies >> > > > > -- > --Guido van Rossum (python.org/~guido) > -------------- next part -------------- An HTML attachment was scrubbed... URL: From minesh at gmail.com Wed Jan 4 14:20:17 2017 From: minesh at gmail.com (Minesh Patel) Date: Wed, 4 Jan 2017 11:20:17 -0800 Subject: [Baypiggies] Question on Python's MRO... In-Reply-To: References: Message-ID: If the order was mixin2->mixin1->class A then wouldn't it have printed "In mixin2.foo()"? On Wed, Jan 4, 2017 at 10:07 AM, Braun Brelin wrote: > What I'm confused about is the following: > > #!/usr/bin/env python3 > class mixin1(object): > def foo(self): > print ("In mixin1.foo()") > > class mixin2 (object): > def foo(self): > print ("In mixin2.foo()") > > class A(object): > def __init__(self): > print ("In class A") > > class B(A,mixin1,mixin2): > def __init__(self): > self.foo() > > > myB = B() > > ------------------------------------------------------------ > -------------------------------------------------- > The output of this program is: > In mixin1.foo() > > So, it seems to be doing method resolution from right to left. No? > > Braun > > > > I've always understood that the class hierarchy when determining > inheritance is that Python looks at class mixin2 first, then class mixin1, > then the base class A. I.e. the order is right to left. A number of web > site > > On Wed, Jan 4, 2017 at 7:37 PM, Guido van Rossum wrote: > >> C's MRO is (C, A, B, object), and method lookup happens in that order. So >> if both A and B define a method m, but C doesn't, A.m gets used. >> >> For old-style classes the lookup order would still be (C, A, B). >> >> Maybe you can clarify *what* is happening from right to left in your >> understanding? Code speaks! >> >> On Wed, Jan 4, 2017 at 9:30 AM, Braun Brelin wrote: >> >>> Hi all, >>> >>> I'm trying to figure out how to understand Python's Method Resolution >>> order. >>> One of the things that's really confusing me is that from my >>> understanding >>> if I have a class declaration like this >>> >>> class C(A,B): >>> ... >>> >>> Python does the inheritance order from right to left, yet all the >>> tutorials on MRO >>> start talking about inheritance from left to right. >>> >>> Is the right to left order a property of the older Python 2 style >>> classes that didn't >>> explicitly inherit from object? >>> >>> Thanks >>> >>> >>> >>> _______________________________________________ >>> Baypiggies mailing list >>> Baypiggies at python.org >>> To change your subscription options or unsubscribe: >>> https://mail.python.org/mailman/listinfo/baypiggies >>> >> >> >> >> -- >> --Guido van Rossum (python.org/~guido) >> > > > _______________________________________________ > Baypiggies mailing list > Baypiggies at python.org > To change your subscription options or unsubscribe: > https://mail.python.org/mailman/listinfo/baypiggies > -- Thanks, --Minesh -------------- next part -------------- An HTML attachment was scrubbed... URL: From rodrigc at freebsd.org Wed Jan 4 14:29:12 2017 From: rodrigc at freebsd.org (Craig Rodrigues) Date: Wed, 4 Jan 2017 11:29:12 -0800 Subject: [Baypiggies] Question on Python's MRO... In-Reply-To: References: Message-ID: Hi, If you haven't read them, I suggest that you read these tutorials on the Python MRO: https://makina-corpus.com/blog/metier/2014/python-tutorial-understanding-python-mro-class-search-path http://stackoverflow.com/questions/1848474/method-resolution-order-mro-in-new-style-python-classes I read those tutorials a few times and went through the examples. I found that going through the examples helped my understanding of the MRO and differences between "old-style" and "new-style" classes. -- Craig On Wed, Jan 4, 2017 at 9:30 AM, Braun Brelin wrote: > Hi all, > > I'm trying to figure out how to understand Python's Method Resolution > order. > One of the things that's really confusing me is that from my understanding > if I have a class declaration like this > > class C(A,B): > ... > > Python does the inheritance order from right to left, yet all the > tutorials on MRO > start talking about inheritance from left to right. > > Is the right to left order a property of the older Python 2 style classes > that didn't > explicitly inherit from object? > > Thanks > > > > _______________________________________________ > Baypiggies mailing list > Baypiggies at python.org > To change your subscription options or unsubscribe: > https://mail.python.org/mailman/listinfo/baypiggies > -------------- next part -------------- An HTML attachment was scrubbed... URL: From bbrelin at gmail.com Wed Jan 4 14:33:39 2017 From: bbrelin at gmail.com (Braun Brelin) Date: Wed, 4 Jan 2017 21:33:39 +0200 Subject: [Baypiggies] Question on Python's MRO... In-Reply-To: References: Message-ID: The point here is 'which' foo is being called. Since it seems to go from right to left, it finds mixin2's foo method first, and then when it finds mixin1's foo method second that becomes the one that is used... At least that's what seems to be happening. On Wed, Jan 4, 2017 at 9:20 PM, Minesh Patel wrote: > If the order was mixin2->mixin1->class A then wouldn't it have printed "In > mixin2.foo()"? > > > > On Wed, Jan 4, 2017 at 10:07 AM, Braun Brelin wrote: > >> What I'm confused about is the following: >> >> #!/usr/bin/env python3 >> class mixin1(object): >> def foo(self): >> print ("In mixin1.foo()") >> >> class mixin2 (object): >> def foo(self): >> print ("In mixin2.foo()") >> >> class A(object): >> def __init__(self): >> print ("In class A") >> >> class B(A,mixin1,mixin2): >> def __init__(self): >> self.foo() >> >> >> myB = B() >> >> ------------------------------------------------------------ >> -------------------------------------------------- >> The output of this program is: >> In mixin1.foo() >> >> So, it seems to be doing method resolution from right to left. No? >> >> Braun >> >> >> >> I've always understood that the class hierarchy when determining >> inheritance is that Python looks at class mixin2 first, then class mixin1, >> then the base class A. I.e. the order is right to left. A number of web >> site >> >> On Wed, Jan 4, 2017 at 7:37 PM, Guido van Rossum >> wrote: >> >>> C's MRO is (C, A, B, object), and method lookup happens in that order. >>> So if both A and B define a method m, but C doesn't, A.m gets used. >>> >>> For old-style classes the lookup order would still be (C, A, B). >>> >>> Maybe you can clarify *what* is happening from right to left in your >>> understanding? Code speaks! >>> >>> On Wed, Jan 4, 2017 at 9:30 AM, Braun Brelin wrote: >>> >>>> Hi all, >>>> >>>> I'm trying to figure out how to understand Python's Method Resolution >>>> order. >>>> One of the things that's really confusing me is that from my >>>> understanding >>>> if I have a class declaration like this >>>> >>>> class C(A,B): >>>> ... >>>> >>>> Python does the inheritance order from right to left, yet all the >>>> tutorials on MRO >>>> start talking about inheritance from left to right. >>>> >>>> Is the right to left order a property of the older Python 2 style >>>> classes that didn't >>>> explicitly inherit from object? >>>> >>>> Thanks >>>> >>>> >>>> >>>> _______________________________________________ >>>> Baypiggies mailing list >>>> Baypiggies at python.org >>>> To change your subscription options or unsubscribe: >>>> https://mail.python.org/mailman/listinfo/baypiggies >>>> >>> >>> >>> >>> -- >>> --Guido van Rossum (python.org/~guido) >>> >> >> >> _______________________________________________ >> Baypiggies mailing list >> Baypiggies at python.org >> To change your subscription options or unsubscribe: >> https://mail.python.org/mailman/listinfo/baypiggies >> > > > > -- > Thanks, > --Minesh > -------------- next part -------------- An HTML attachment was scrubbed... URL: From bbrelin at gmail.com Wed Jan 4 14:52:39 2017 From: bbrelin at gmail.com (Braun Brelin) Date: Wed, 4 Jan 2017 21:52:39 +0200 Subject: [Baypiggies] Question on Python's MRO... In-Reply-To: <35AAF918-175B-4ADC-99BD-D7D49C6EB2C8@ryanhiebert.com> References: <35AAF918-175B-4ADC-99BD-D7D49C6EB2C8@ryanhiebert.com> Message-ID: Hmmm...This is interesting. I've read a number of web sites that indicate that the class hierarchy in Python is right to left, not left to right. Is this a common mis-perception? Braun On Wed, Jan 4, 2017 at 9:47 PM, Ryan Hiebert wrote: > > > On Jan 4, 2017, at 1:33 PM, Braun Brelin wrote: > > > > The point here is 'which' foo is being called. Since it seems to go > from right to left, it finds mixin2's foo method first, and then when it > finds mixin1's foo method second that becomes the one that is used... > > > > At least that's what seems to be happening. > > Ah, I think I see your confusion. It's not the _last_ one in the MRO that > get's called, it's the _first_. The highest root (object) will always be > last in the MRO, and type of the current object will be first. -------------- next part -------------- An HTML attachment was scrubbed... URL: From guido at python.org Wed Jan 4 22:53:41 2017 From: guido at python.org (Guido van Rossum) Date: Wed, 4 Jan 2017 19:53:41 -0800 Subject: [Baypiggies] Question on Python's MRO... In-Reply-To: References: Message-ID: On Wed, Jan 4, 2017 at 11:33 AM, Braun Brelin wrote: > The point here is 'which' foo is being called. Since it seems to go from > right to left, it finds mixin2's foo method first, and then when it finds > mixin1's foo method second that becomes the one that is used... > This clarifies the misunderstanding. The example you gave (where "mixin1.foo()" got called -- we all agree on that!) is clearly left-to-right for everyone here, but you cited it as proof that the algorithm is right-to-left. You seem to interpret the algorithm as going from right to left and then using the *last* one found. But the way the algorithm is normally described (not to mention how it's implemented :-) is that it goes from left to right and stops at the *first* one found. Hope this help! (If you can find a website that claims it's right-to-left I'd like to see a link to that -- I've never seen it described that way before, and I've seen a lot of tutorials about Python's MRO... :-) -- --Guido van Rossum (python.org/~guido) -------------- next part -------------- An HTML attachment was scrubbed... URL: From simeonf at gmail.com Tue Jan 10 19:23:16 2017 From: simeonf at gmail.com (Simeon Franklin) Date: Tue, 10 Jan 2017 16:23:16 -0800 Subject: [Baypiggies] Looking for Talks for SF Python Meetup Message-ID: Hey Baypiggies - SF Python Meetup has a CFP open. Please submit your bio and abstract in the next week or so as we plan Q1 & Q2 slots. Talks you've given at Baypiggies are welcome! SF Python Meetup meets on the 2nd Wednesday of each month in San Francisco for *Talks Night* and typically draws 150-180 participants. We're looking for talks encompassing Python Fundamentals, Performance, Data, and Networking. You can check out previous meetups at http://sfpythonmeetup.com/ -regards Simeon Franklin ps - SF Python Meetup also hosts a *Project Night* each month on the third Wednesday. Project Night features tutorials on a variety of experience levels but focuses on welcoming beginners into the Python community. If you've got a tutorial you're interested in presenting drop me an email! I'm happy to report that project night next week at Galvanize will feature Baypiggies' own Jeff Fischer who is trying out a new "MicroPython on ESP8266" tutorial! -------------- next part -------------- An HTML attachment was scrubbed... URL: From chityala at gmail.com Wed Jan 11 19:39:42 2017 From: chityala at gmail.com (Ravi) Date: Wed, 11 Jan 2017 16:39:42 -0800 Subject: [Baypiggies] Two Python courses at UCSC Extension in Santa Clara this winter Message-ID: Hello All, Two identical Python courses are being offered at the UCSC Extension in Santa Clara during the Winter term. Both the courses will cover the most important aspects of Python such as functions, object oriented programming, decorators, generators etc. and will be very hands-on with in-class activities and homework. We will also provide IPython notebook that will contain many examples. We are also introducing a new collaborative learning tool. You can choose to take one of the course according to your schedule. The content and material used in the course are identical. The first course starts on Jan 18th, 2017 and ends on March 22nd, 2017 and will be held every Wednesday from 6:30pm-9:30 pm. The second course starts on Jan 31st, 2017 and ends on Apr 4th, 2017 and will be held every Tuesday from 6:30-9:30 pm. To register for either section visit http://course.ucsc- extension.edu/modules/shop/index.html?action=section& OfferingID=1531625&SectionID=5279163 and select either the tab *3064.126 *or* 3064.127*. UCSC Extension is accredited by various bodies through the University of California, Santa Cruz. Hence, many employers will reimburse the cost of the course. Join now to become a Pythonista and program in one of the fastest growing language. You can email me at chityala at gmail.com if you have any questions. Thanks, Regards, Ravi Chityala -------------- next part -------------- An HTML attachment was scrubbed... URL: From jeffrey.fischer at gmail.com Tue Jan 17 10:41:51 2017 From: jeffrey.fischer at gmail.com (Jeff Fischer) Date: Tue, 17 Jan 2017 07:41:51 -0800 Subject: [Baypiggies] November and December talks are now up on YouTube Message-ID: *November 2016 Baypiggies Talk at LinkedIn: Django and Security* Speaker: James Bennett https://youtu.be/wCO8icdG_zg *Dec 2016 BayPiggies Talk at LinkedIn: Introducing Type Annotations for Python* Speakers: Guido Van Rossum, Greg Price, and David Fisher https://youtu.be/ZP_QV4ccFHQ Thanks to Josh and the LinkedIn A-V team for recording the talks and getting them to us. Thanks again to the speakers for the great talks. Regards, Jeff -------------- next part -------------- An HTML attachment was scrubbed... URL: From santiago.basulto at gmail.com Fri Jan 20 11:50:11 2017 From: santiago.basulto at gmail.com (Santiago Basulto) Date: Fri, 20 Jan 2017 13:50:11 -0300 Subject: [Baypiggies] Who's in charge of python.org/doc/av/ Message-ID: Hello guys, do you know who's in charge of https://www.python.org/doc/av/? There are several broken links and we'd like to propose new content Thanks! -- Santiago Basulto.- Up! -------------- next part -------------- An HTML attachment was scrubbed... URL: From web at stevepiercy.com Fri Jan 20 14:37:36 2017 From: web at stevepiercy.com (Steve Piercy - Website Builder) Date: Fri, 20 Jan 2017 11:37:36 -0800 Subject: [Baypiggies] Who's in charge of python.org/doc/av/ In-Reply-To: Message-ID: In the website footer: Submit Website Bug https://github.com/python/pythondotorg/issues --steve On 1/20/17 at 1:50 PM, santiago.basulto at gmail.com (Santiago Basulto) pronounced: > Hello guys, do you know who's in charge of https://www.python.org/doc/av/? > There are several broken links and we'd like to propose new content > > Thanks! > -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- Steve Piercy Website Builder Soquel, CA From glen at glenjarvis.com Sun Jan 22 22:15:55 2017 From: glen at glenjarvis.com (Glen Jarvis) Date: Sun, 22 Jan 2017 19:15:55 -0800 Subject: [Baypiggies] Gift: I just paid the MeetUp dues | But, I could use some help... Message-ID: We received a bill for the MeetUp website again. Some people may remember that being a source of confusion a little over a year ago. I just paid the bill again for the first part of this year (I also paid last year). I certainly don't mind. This is a great community and well worth it. I know there are pythonistas who also like to help this community. But, if you want to help, I'm going to ask you to help me with something bigger - and something that may make a pretty big impact for us. I have been working to increase our black diversity at PyCon this year. I've specifically been working with a group here in Oakland known as The Hidden Genius Project. Here is a quick video to explain what they do: https://www.youtube.com/watch?v=9raOJkMghiA I have worked with them to explain what PyCon is and they are very excited. I have a list of twelve very interested individuals who want to go. I have just sent an email to pycon-staff with the 12 names in hope that we can get scholarships. I don't know, however, if transportation is included. I am working on a "back up plan" now to solicit pledges (no money now, just a pledge if it's needed) to sponsor each of the twelve participants on a flight from the Bay Area to Portland this year. I personally will sponsor one flight (so I'll just double what I pay for my flight). And, I'm asking for others who can help sponsor too. Again, no money is need at the moment. But, if you can help (or even think that you *may* be able to help), please send me an email with: To: Glen Jarvis Subject (exactly): "Hidden Genius Project PyCon Flight" (that will help me collate them). Body: Please also include the amount of the pledge (estimating what you think it will cost to fly round trip from the Bay Area to Portland). We may not need to take the money that you pledge, but would appreciate it if needed. I am very excited to increase our diversity and to share with the Hidden Genius Project the magic that I think of when I go to PyCon. Warmest Regards, Glen Jarvis -------------- next part -------------- An HTML attachment was scrubbed... URL: From shortdudey123 at gmail.com Thu Jan 26 22:38:10 2017 From: shortdudey123 at gmail.com (Grant Ridder) Date: Thu, 26 Jan 2017 19:38:10 -0800 Subject: [Baypiggies] Talk attendance numbers for 2017 Message-ID: Hey Everyone, Here is the count of how many people attended the talks so far this year DATE - ATTENDED (YES'S ON MEETUP.COM ) Jan 26 - 150 (353) Feb 23 - Mar 23 - Apr 27 - May 25 - Jun 22 - Jul Aug Sept Oct Nov Dev -Grant -------------- next part -------------- An HTML attachment was scrubbed... URL: From glen at glenjarvis.com Thu Jan 26 22:48:11 2017 From: glen at glenjarvis.com (Glen Jarvis) Date: Thu, 26 Jan 2017 19:48:11 -0800 Subject: [Baypiggies] Streaming tonight's talk: Message-ID: Did you miss the talk? We are live streaming.... http://www.google.com/url?q=http%3A%2F%2Fwww.ustream.tv% 2Flinkedin-events&sa=D&sntz=1&usg=AFQjCNEs-eoxSJfUGPEn4RCtSc6TM5kBGw And, also recording.... -------------- next part -------------- An HTML attachment was scrubbed... URL: From zadka.moshe at gmail.com Sun Jan 29 13:51:39 2017 From: zadka.moshe at gmail.com (Moshe Zadka) Date: Sun, 29 Jan 2017 18:51:39 +0000 Subject: [Baypiggies] Announcing the First Peninsula Python Meetup Message-ID: San Francisco too far up north? Sunnyvale too far down south? Were you looking for a meetup in the Peninsula goldilocks zone? Announcing Pyninsula, the First Peninsula Python Meetup. URL: https://www.meetup.com/Pyninsula-Python-Peninsula-Meetup/ Date: Feb 21st, 2017 Time: 6:30pm-9:30pm Place: shopkick, 900 Middlefield Rd., 3rd floor, Redwood City, CA shopkick is right next to the Redwood City CalTrain station, for those using public transportation. If arriving by car, park at the Jefferson Garage (830 Jefferson Ave., Redwood City). Please RSVP. -------------- next part -------------- An HTML attachment was scrubbed... URL: