From gerard.blokdijk at theartofservice.com Wed Oct 5 15:17:41 2016 From: gerard.blokdijk at theartofservice.com (Gerard Blokdijk) Date: Wed, 5 Oct 2016 19:17:41 +0000 Subject: [pydotorg-www] Question about Programming paradigm covered at https://wiki.python.org/moin/PythonFederalEnterpriseArchitecture Message-ID: <010001579647a7fc-7351d444-609d-476a-b76c-a6d8b951a1c1-000000@email.amazonses.com> Hello Pydotorg, I was searching for Programming paradigm information and I came across https://wiki.python.org/moin/PythonFederalEnterpriseArchitecture, where you cover Programming paradigm. Programming paradigm is included in the current Enterprise Architecture predictive analytics report at https://theartofservice.com/Enterprise-Architecture-predictive-analytics-report.html Because I feel this is of interest to you, and to find mutual ground, I want to give you the full $97 report for free. You can download the PDF direct here https://theartofservicelab.s3.amazonaws.com/report/Enterprise%20Architecture%20Predictive%20Analytics.pdf What is the value of the report? I've been in many enterprise data center management and CxO roles over the past 25 years, and something simple as reports like we're producing was always the guide I missed; transparant data across many data points covering a specific topic and its related topics, highlighting what's important now and in the future - a simple way to instantly understand and move forward in the right direction, based on verifiable data. The aim of the report is to give a compass-overview of what is, and is going to be, of impact to the topic of the report - for readers who need a quick starter and insight into the topic. It is NOT meant for an expert in the field, who knows the field inside-out. The report's target audience is the manager and professional who needs quick insight into the field and where it is heading. Would you give me a bit of your time to go look at it? I'm asking this because the analysis has to win on its own right and appeal to you. It solves a lot of clients' problems and it has to be obvious to you how it would create value to you. Please feel free to use the data, including graphics, in any way. I would appreciate it if you would consider linking to https://theartofservice.com/Enterprise-Architecture-predictive-analytics-report.html. To make it easy you can use the following text (or use any text you like): 'The Art of Service's Enterprise Architecture predictive analytics report evaluates technologies and applications (including Programming paradigm) in terms of their business impact, adoption rate and maturity level to help users decide where and when to invest.' If I can assist you with anything else, or return the favor, please let me know. Gerard Blokdijk Connect with me here: https://www.linkedin.com/in/gerardblokdijk CEO The Art of Service https://theartofservice.com gerard.blokdijk at theartofservice.com From guido at python.org Wed Oct 5 16:11:55 2016 From: guido at python.org (Guido van Rossum) Date: Wed, 5 Oct 2016 13:11:55 -0700 Subject: [pydotorg-www] Question about Programming paradigm covered at https://wiki.python.org/moin/PythonFederalEnterpriseArchitecture In-Reply-To: <010001579647a7fc-7351d444-609d-476a-b76c-a6d8b951a1c1-000000@email.amazonses.com> References: <010001579647a7fc-7351d444-609d-476a-b76c-a6d8b951a1c1-000000@email.amazonses.com> Message-ID: Everyone, don't bother with this. It's spam. On Wed, Oct 5, 2016 at 12:17 PM, Gerard Blokdijk wrote: > Hello Pydotorg, > > I was searching for Programming paradigm information and I came across https://wiki.python.org/moin/PythonFederalEnterpriseArchitecture, where you cover Programming paradigm. > > Programming paradigm is included in the current Enterprise Architecture predictive analytics report at https://theartofservice.com/Enterprise-Architecture-predictive-analytics-report.html > > Because I feel this is of interest to you, and to find mutual ground, I want to give you the full $97 report for free. You can download the PDF direct here https://theartofservicelab.s3.amazonaws.com/report/Enterprise%20Architecture%20Predictive%20Analytics.pdf > > What is the value of the report? > > I've been in many enterprise data center management and CxO roles over the past 25 years, and something simple as reports like we're producing was always the guide I missed; transparant data across many data points covering a specific topic and its related topics, highlighting what's important now and in the future - a simple way to instantly understand and move forward in the right direction, based on verifiable data. > > The aim of the report is to give a compass-overview of what is, and is going to be, of impact to the topic of the report - for readers who need a quick starter and insight into the topic. It is NOT meant for an expert in the field, who knows the field inside-out. The report's target audience is the manager and professional who needs quick insight into the field and where it is heading. > > Would you give me a bit of your time to go look at it? > > I'm asking this because the analysis has to win on its own right and appeal to you. It solves a lot of clients' problems and it has to be obvious to you how it would create value to you. > > Please feel free to use the data, including graphics, in any way. > > I would appreciate it if you would consider linking to https://theartofservice.com/Enterprise-Architecture-predictive-analytics-report.html. To make it easy you can use the following text (or use any text you like): 'The Art of Service's Enterprise Architecture predictive analytics report evaluates technologies and applications (including Programming paradigm) in terms of their business impact, adoption rate and maturity level to help users decide where and when to invest.' > > If I can assist you with anything else, or return the favor, please let me know. > > Gerard Blokdijk > Connect with me here: https://www.linkedin.com/in/gerardblokdijk > CEO > The Art of Service > https://theartofservice.com > gerard.blokdijk at theartofservice.com > _______________________________________________ > pydotorg-www mailing list > pydotorg-www at python.org > https://mail.python.org/mailman/listinfo/pydotorg-www -- --Guido van Rossum (python.org/~guido) From skaperen at unseen.is Thu Oct 6 02:18:12 2016 From: skaperen at unseen.is (skaperen at unseen.is) Date: Thu, 6 Oct 2016 06:18:12 +0000 (GMT) Subject: [pydotorg-www] editing on the wiki Message-ID: <454164006.544247.1475734692765.JavaMail.zimbra@unseen.is> i just signed up on the wiki as my real name PhilHoward per the stated name format and request editor authorization. i am Skaperen on python-forum.io. my editing intentions are minimal ... cleaning up typos and adding hints as i run into them. i will be looking over the wiki to understand the scope of coverage. other emails i use are phil.d.howard at gmail.com and phil at stratusrelay.com. thank you. -------------- next part -------------- An HTML attachment was scrubbed... URL: From rosuav at gmail.com Thu Oct 6 02:42:30 2016 From: rosuav at gmail.com (Chris Angelico) Date: Thu, 6 Oct 2016 17:42:30 +1100 Subject: [pydotorg-www] editing on the wiki In-Reply-To: <454164006.544247.1475734692765.JavaMail.zimbra@unseen.is> References: <454164006.544247.1475734692765.JavaMail.zimbra@unseen.is> Message-ID: On Thu, Oct 6, 2016 at 5:18 PM, wrote: > i just signed up on the wiki as my real name PhilHoward per the stated name > format and request editor authorization. i am Skaperen on python-forum.io. > my editing intentions are minimal ... cleaning up typos and adding hints as > i run into them. i will be looking over the wiki to understand the scope of > coverage. other emails i use are phil.d.howard at gmail.com and > phil at stratusrelay.com. thank you. Copyeditors are always welcome. Thank you for offering to contribute! You should now be able to make edits. ChrisA From solipsis at pitrou.net Thu Oct 6 11:39:49 2016 From: solipsis at pitrou.net (Antoine Pitrou) Date: Thu, 6 Oct 2016 17:39:49 +0200 Subject: [pydotorg-www] gnutls_handshake() failed: Error in the pull function Message-ID: <20161006173949.5a1c25e0@fsol> Hello, For some time now, I have had sporadic failures when browsing to www.python.org and related websites such as docs.python.org. With Firefox, I would simply get a blank page without any error message whatsoever. With curl, it manifests with the following error: $ curl -v -I https://www.python.org/ * Trying 2a04:4e42:a::223... * Trying 151.101.40.223... * Connected to www.python.org (2a04:4e42:a::223) port 443 (#0) * found 173 certificates in /etc/ssl/certs/ca-certificates.crt * found 704 certificates in /etc/ssl/certs * ALPN, offering http/1.1 * gnutls_handshake() failed: Error in the pull function. * Closing connection 0 curl: (35) gnutls_handshake() failed: Error in the pull function. It is extremely irregular, sometimes it doesn't happen, sometimes several times in a row, sometimes once in a while. Is anyone else noticing this? Regards Antoine. From brittney at mail.vpb.com Fri Oct 7 04:39:23 2016 From: brittney at mail.vpb.com (Brittney) Date: Fri, 7 Oct 2016 16:39:23 +0800 Subject: [pydotorg-www] I think you need! Message-ID: <5fb844e71fa8f4476d2ee1b52f83dd95@43.239.167.7> An HTML attachment was scrubbed... URL: From anabell at mit.edu Mon Oct 10 11:23:07 2016 From: anabell at mit.edu (Ana Bell) Date: Mon, 10 Oct 2016 15:23:07 +0000 Subject: [pydotorg-www] editing a wiki page Message-ID: <644312767BEE164B82EFB7E1B264E86B6E33CB50@OC11EXPO25.exchange.mit.edu> Hello, My Wiki username is AnaBell and I don?t have access to edit the wiki of Introductory books here: https://wiki.python.org/moin/IntroductoryBooks I am an author for an introductory python book with Manning Publications. If possible, I would like to add my book to the list in the wiki above. Below is the text I would like to add. Thank you very much! Ana Learn Python By Ana Bell Manning Publications Co ISBN 9781617293788 325 pages (estimated) printed in black & white MEAP began October 2016, Publication in Spring 2017 (estimated) Book overview: When you're ready to learn to program, Python is a great language to start with. It has a straightforward syntax, you'll find it easy to learn, and it's extremely versatile. Once you master the basics, you'll appreciate Python's very strong online community where you can continue learning and tinkering with more advanced programming techniques. All you need is some help to get going. Learning to program with Python doesn't have to be difficult, in fact it can even be fun. This book will get you started! Learn Python is an introduction to programming using one of the most popular programming languages. The first few chapters give you a quick background to programming concepts and a hands-on guide to setting up your programming environment. You will then be gently introduced to the basics of programming, building up to writing your first programs! This easy-to-follow tutorial is full of exercises to practice and reinforce each new concept, as well as to give you confidence that you are ready to move on to the next lesson. As you progress, you'll learn programming topics and concepts that are ubiquitous across almost all other programming languages. By the end of the book, you'll have a solid grasp of how to write programs as well as programming best practices. Who this book is written for: Anyone without programming experience who wants an easy-to-follow book that guides you through short lessons and exercises. Publisher's page: https://www.manning.com/books/learn-python -------------- next part -------------- An HTML attachment was scrubbed... URL: From rosuav at gmail.com Mon Oct 10 11:31:35 2016 From: rosuav at gmail.com (Chris Angelico) Date: Tue, 11 Oct 2016 02:31:35 +1100 Subject: [pydotorg-www] editing a wiki page In-Reply-To: <644312767BEE164B82EFB7E1B264E86B6E33CB50@OC11EXPO25.exchange.mit.edu> References: <644312767BEE164B82EFB7E1B264E86B6E33CB50@OC11EXPO25.exchange.mit.edu> Message-ID: On Tue, Oct 11, 2016 at 2:23 AM, Ana Bell wrote: > My Wiki username is AnaBell and I don?t have access to edit the wiki of > Introductory books here: https://wiki.python.org/moin/IntroductoryBooks > > I am an author for an introductory python book with Manning Publications. If > possible, I would like to add my book to the list in the wiki above. Below > is the text I would like to add. Thank you very much! > > ISBN 9781617293788 325 pages (estimated) printed in black & white > > MEAP began October 2016, Publication in Spring 2017 (estimated) Other wiki admins: What's policy on upcoming materials? ChrisA From mal at python.org Mon Oct 10 11:40:08 2016 From: mal at python.org (M.-A. Lemburg) Date: Mon, 10 Oct 2016 17:40:08 +0200 Subject: [pydotorg-www] editing a wiki page In-Reply-To: References: <644312767BEE164B82EFB7E1B264E86B6E33CB50@OC11EXPO25.exchange.mit.edu> Message-ID: <57FBB658.1080207@python.org> On 10.10.2016 17:31, Chris Angelico wrote: > On Tue, Oct 11, 2016 at 2:23 AM, Ana Bell wrote: >> My Wiki username is AnaBell and I don?t have access to edit the wiki of >> Introductory books here: https://wiki.python.org/moin/IntroductoryBooks >> >> I am an author for an introductory python book with Manning Publications. If >> possible, I would like to add my book to the list in the wiki above. Below >> is the text I would like to add. Thank you very much! >> >> ISBN 9781617293788 325 pages (estimated) printed in black & white >> >> MEAP began October 2016, Publication in Spring 2017 (estimated) > > Other wiki admins: What's policy on upcoming materials? I don't think it's useful to add unreleased book infos to the website. Having the infos available once the book is available sounds like a good thing, though. -- Marc-Andre Lemburg Python Software Foundation http://www.python.org/psf/ http://www.malemburg.com/ From rosuav at gmail.com Mon Oct 10 11:58:27 2016 From: rosuav at gmail.com (Chris Angelico) Date: Tue, 11 Oct 2016 02:58:27 +1100 Subject: [pydotorg-www] editing a wiki page In-Reply-To: <644312767BEE164B82EFB7E1B264E86B6E33CB50@OC11EXPO25.exchange.mit.edu> References: <644312767BEE164B82EFB7E1B264E86B6E33CB50@OC11EXPO25.exchange.mit.edu> Message-ID: On Tue, Oct 11, 2016 at 2:23 AM, Ana Bell wrote: > I am an author for an introductory python book with Manning Publications. If > possible, I would like to add my book to the list in the wiki above. Hi Ana! At the moment, your book is still in development, right? You mention an estimated publication date only. Once the book becomes available, it would be a very useful addition to the web site, but for now, it would probably only tease, rather than serving. But we would be very happy to welcome your contribution to the wiki once the book is ready to be bought and/or downloaded! ChrisA From anabell at mit.edu Mon Oct 10 12:10:45 2016 From: anabell at mit.edu (Ana Bell) Date: Mon, 10 Oct 2016 16:10:45 +0000 Subject: [pydotorg-www] editing a wiki page In-Reply-To: References: <644312767BEE164B82EFB7E1B264E86B6E33CB50@OC11EXPO25.exchange.mit.edu>, Message-ID: <644312767BEE164B82EFB7E1B264E86B6E33CCBA@OC11EXPO25.exchange.mit.edu> Hi Chris, Thanks for the quick reply! Yep, it is still in development but the MEAP program allows readers to get early access to chapters as they get written. But if you think it will be better to add it when it is finished, I?ll ping you again then. Thank you! Ana From: Chris Angelico Sent: Monday, October 10, 2016 11:58 AM To: Ana Bell Cc: pydotorg-www at python.org Subject: Re: [pydotorg-www] editing a wiki page On Tue, Oct 11, 2016 at 2:23 AM, Ana Bell wrote: > I am an author for an introductory python book with Manning Publications. If > possible, I would like to add my book to the list in the wiki above. Hi Ana! At the moment, your book is still in development, right? You mention an estimated publication date only. Once the book becomes available, it would be a very useful addition to the web site, but for now, it would probably only tease, rather than serving. But we would be very happy to welcome your contribution to the wiki once the book is ready to be bought and/or downloaded! ChrisA -------------- next part -------------- An HTML attachment was scrubbed... URL: From rosuav at gmail.com Mon Oct 10 12:52:32 2016 From: rosuav at gmail.com (Chris Angelico) Date: Tue, 11 Oct 2016 03:52:32 +1100 Subject: [pydotorg-www] editing a wiki page In-Reply-To: <644312767BEE164B82EFB7E1B264E86B6E33CCBA@OC11EXPO25.exchange.mit.edu> References: <644312767BEE164B82EFB7E1B264E86B6E33CB50@OC11EXPO25.exchange.mit.edu> <644312767BEE164B82EFB7E1B264E86B6E33CCBA@OC11EXPO25.exchange.mit.edu> Message-ID: On Tue, Oct 11, 2016 at 3:10 AM, Ana Bell wrote: > Thanks for the quick reply! Yep, it is still in development but the MEAP > program allows readers to get early access to chapters as they get written. > But if you think it will be better to add it when it is finished, I?ll ping > you again then. Oh! I think I understand. So what you're saying is that some of the content is available *right now*, and more is becoming available progressively? If you could add a few words to the copy to explain that, it would be helpful - I'm not the only person who is entirely unfamiliar with MEAP. On that basis, it's sounding a lot more like something that'll be useful to people now, and thus worth having on the wiki. I'm giving you editor access so you can add that reference. Thank you for your contribution to the Python community! ChrisA From anabell at mit.edu Mon Oct 10 13:16:52 2016 From: anabell at mit.edu (Ana Bell) Date: Mon, 10 Oct 2016 17:16:52 +0000 Subject: [pydotorg-www] editing a wiki page In-Reply-To: References: <644312767BEE164B82EFB7E1B264E86B6E33CB50@OC11EXPO25.exchange.mit.edu> <644312767BEE164B82EFB7E1B264E86B6E33CCBA@OC11EXPO25.exchange.mit.edu>, Message-ID: <644312767BEE164B82EFB7E1B264E86B6E33CD49@OC11EXPO25.exchange.mit.edu> Thanks Chris! I edited the page and added a sentence explaining that chapters are available now and will become available as they are written. Much appreciated, Ana From: Chris Angelico Sent: Monday, October 10, 2016 12:52 PM To: Ana Bell Cc: pydotorg-www at python.org Subject: Re: [pydotorg-www] editing a wiki page On Tue, Oct 11, 2016 at 3:10 AM, Ana Bell wrote: > Thanks for the quick reply! Yep, it is still in development but the MEAP > program allows readers to get early access to chapters as they get written. > But if you think it will be better to add it when it is finished, I?ll ping > you again then. Oh! I think I understand. So what you're saying is that some of the content is available *right now*, and more is becoming available progressively? If you could add a few words to the copy to explain that, it would be helpful - I'm not the only person who is entirely unfamiliar with MEAP. On that basis, it's sounding a lot more like something that'll be useful to people now, and thus worth having on the wiki. I'm giving you editor access so you can add that reference. Thank you for your contribution to the Python community! ChrisA -------------- next part -------------- An HTML attachment was scrubbed... URL: From phillip.m.feldman at gmail.com Wed Oct 12 21:50:57 2016 From: phillip.m.feldman at gmail.com (Phillip Feldman) Date: Wed, 12 Oct 2016 18:50:57 -0700 Subject: [pydotorg-www] proposed correction to https://wiki.python.org/moin/NewClassVsClassicClass\ Message-ID: I'd like to propose a correction to the page at https://wiki.python.org/moin/NewClassVsClassicClass: Current text: The minor syntactic difference is that New Style Classes happen to inherit from object. Proposed replacement: The syntactic difference between new- and old-style classes is that the former inherit from `object` and/or from other new-style classes. Dr. Phillip M. Feldman -------------- next part -------------- An HTML attachment was scrubbed... URL: From rosuav at gmail.com Thu Oct 13 03:43:44 2016 From: rosuav at gmail.com (Chris Angelico) Date: Thu, 13 Oct 2016 18:43:44 +1100 Subject: [pydotorg-www] proposed correction to https://wiki.python.org/moin/NewClassVsClassicClass\ In-Reply-To: References: Message-ID: On Thu, Oct 13, 2016 at 12:50 PM, Phillip Feldman wrote: > I'd like to propose a correction to the page at > https://wiki.python.org/moin/NewClassVsClassicClass: If you'd like to make that edit, create a wiki account and we can give you editing access. We do need to know your account name, though. ChrisA From karlijn at datacamp.com Thu Oct 13 09:36:06 2016 From: karlijn at datacamp.com (Karlijn Willems) Date: Thu, 13 Oct 2016 15:36:06 +0200 Subject: [pydotorg-www] Python Basics For Data Science Cheat Sheet Message-ID: Hi As DataCamp's data journalist, I launched a Python For Data Science Cheat Sheet on the DataCamp community yesterday, covering the basics that beginners need to know in order to get started on doing data science with Python. You can find it here: https://www.datacamp.com/community/tutorials/ python-data-science-cheat-sheet-basics I would love to get some feedback from you guys and I was wondering if you might consider adding this cheat sheet as an addition to the Beginner's guide of the Python Wiki. Thanks in advance for your time and looking forward to your reply Karlijn -------------- next part -------------- An HTML attachment was scrubbed... URL: From steve at holdenweb.com Thu Oct 13 11:02:27 2016 From: steve at holdenweb.com (Steve Holden) Date: Thu, 13 Oct 2016 16:02:27 +0100 Subject: [pydotorg-www] Python Basics For Data Science Cheat Sheet In-Reply-To: References: Message-ID: Hi Karlijn, The value of a Wiki is that it's user-editable. You have to create an account, then let us know what it is and we can add editing privileges. This looks like halfway reasonable content, but it would be MUCH better to link straight to the cheat sheet. Sending them through a landing page smacks of advertising, which is definitely not approved of in our informational pages. Having said which, there is also a Python Training page, where you might find an appropriate place to publicize your courses. It's a long time since I visited it. regards Steve PS: The usual abbreviation for "third" is "3rd", but the cheat sheet uses "3d". Also the line reading "x = my_list > 3" should almost certainly read "x = my_array > 3". Errors like that really reduce the value of the content, and make the authors seem unreliable. Steve Holden On Thu, Oct 13, 2016 at 2:36 PM, Karlijn Willems wrote: > Hi > > As DataCamp's data journalist, I launched a Python For Data Science Cheat > Sheet on the DataCamp community yesterday, covering the basics that > beginners need to know in order to get started on doing data science with > Python. > > You can find it here: https://www.datacamp.com/community/tutorials/python- > data-science-cheat-sheet-basics > > I would love to get some feedback from you guys and I was wondering if you > might consider adding this cheat sheet as an addition to the Beginner's > guide of the Python Wiki. > > Thanks in advance for your time and looking forward to your reply > > Karlijn > > _______________________________________________ > pydotorg-www mailing list > pydotorg-www at python.org > https://mail.python.org/mailman/listinfo/pydotorg-www > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From mats at wichmann.us Thu Oct 13 12:03:18 2016 From: mats at wichmann.us (Mats Wichmann) Date: Thu, 13 Oct 2016 10:03:18 -0600 Subject: [pydotorg-www] Python Basics For Data Science Cheat Sheet In-Reply-To: References: Message-ID: <06b07edb-74f9-3269-96f0-c77a85f56f61@wichmann.us> On 10/13/2016 09:02 AM, Steve Holden wrote: > Hi Karlijn, > > The value of a Wiki is that it's user-editable. You have to create an > account, then let us know what it is and we can add editing privileges. > > This looks like halfway reasonable content, but it would be MUCH better to > link straight to the cheat sheet. Sending them through a landing page > smacks of advertising, which is definitely not approved of in our > informational pages. In addition, external links have an irritating tendency to go stale. A lot of the "bugs" against the Python website end up dealing with this very topic. ... > > regards > Steve > > PS: The usual abbreviation for "third" is "3rd", but the cheat sheet uses > "3d". Also the line reading "x = my_list > 3" should almost certainly read > "x = my_array > 3". Errors like that really reduce the value of the > content, and make the authors seem unreliable. looks like those were already corrected, cool. For consistency purposes, note you can't actually run the numpy examples as listed. That doesn't make things broken, but.... This line: >>> import numpy as alias could correct some of that - examples use np, so make it >>> import numpy as np or else just spell it out as numpy in the examples. The "Selecting NumPy Elements" section might be better if you showed outputs. your current 2-d line won't work on the example data you give. In "NumPy Array Operations", you could save a line of precious real estate here: >>> x = my_array > 3 >>> x array([False, False, False, True], dtype=bool) By not assigning-then-printing (the other examples don't do it): >>> my_array > 3 array([False, False, False, True], dtype=bool) Cheeers! From rosuav at gmail.com Thu Oct 13 17:43:34 2016 From: rosuav at gmail.com (Chris Angelico) Date: Fri, 14 Oct 2016 08:43:34 +1100 Subject: [pydotorg-www] proposed correction to https://wiki.python.org/moin/NewClassVsClassicClass\ In-Reply-To: References: Message-ID: On Fri, Oct 14, 2016 at 8:12 AM, Phillip Feldman wrote: > I created a wiki account. My user ID is PhillipMFeldman. > No problem. I've made you an editor. ChrisA From programmingncr at india.com Fri Oct 14 06:21:03 2016 From: programmingncr at india.com (Manish V.) Date: Fri, 14 Oct 2016 10:21:03 +0000 (UTC) Subject: [pydotorg-www] Requesting editing rights Message-ID: <1437606358.141848.1476440463935.JavaMail.tomcat8@be02> Hello, Intended edits to https://wiki.python.org/moin/PythonTraining : I want to add this info : Manish V. is a freelance trainer based in Gurgaon (now Gurugram), India. He provides training, conducts classroom and online classes for beginners offering basic, intermediate, advanced courses covering web development, automation, GUI, data analysis, scientific computing, machine learning, data visualization etc. He also provides coaching for school students of CBSE, ICSE or regional boards as per the python course curriculum followed by the respective boards. He teaches python coding to kids of ages 8 years and more. For further details, please visit http://pythongurgaon.blogspot.com Account Name: ManiV Please allow editing rights for the same. Thanks, Manish From phillip.m.feldman at gmail.com Fri Oct 14 14:34:59 2016 From: phillip.m.feldman at gmail.com (Phillip Feldman) Date: Fri, 14 Oct 2016 11:34:59 -0700 Subject: [pydotorg-www] proposed correction to https://wiki.python.org/moin/NewClassVsClassicClass\ In-Reply-To: References: Message-ID: Hello Chris, Despite having logged in, the system appears to want an additional authentication (TextCha), and I can't seem to get past that step. So, I'm pasting my revised text below. Yours, Phillip The "New Class" is the recommended way to create a class in modern Python. A "Classic Class" or "old-style class" is a class as it existed in Python 2.1 and before. They have been retained for backwards compatibility. This page explains the differences. The syntactic difference between old- and new-style classes is that the latter inherit from `object` or from at least one new-style class. A class that inherits from nothing, or that inherits only from old-style classes, is an old-style class. {{{ class Old1: ... class Old2(Old1, UserDict): # Assuming UserDict is still old-style ... }}} vs {{{ class New1(object): ... class New2(New1): ... class New3(Old1, New2): ... class New4(dict, Old1): # dict is a newstyle class ... }}} * New Style classes can use descriptors (including {{{__slots__}}}), while Old Style classes cannot. Normally, this is just an advantage for New Style Classes, but it can affect lookup. An old-style class will always find an attribute on an instance before it looks in the hierarchy. (So you can hide a method.) A new-style class will let the class definition win if it is a writeable descriptor, so you may not be able to (effectively) store data on an instance. [[ http://www.python.org/2.2.2/descrintro.html#property|More information on slots and descriptors.]] Warning: In 2.5, magic names (typically those with a double underscore (DunderAlias) at both ends of the name) may look at the class rather than the instance even for old-style classes. I say this based on some python-dev discussion; I didn't notice how solidly the final decision was made. Later discussion extended it to "next" (despite the lack of underscore) and Guido said not to count on it in either direction. Since magic names are supposed be generally reserved anyhow, normal code should not care. * Magic names (which ones even exist) have changed a little. Old classes don't have an {{{__mro__}}}, new classes (generally) don't have {{{__members__}}} or {{{__methods__}}}. New classes generally won't let you change the class's {{{__bases__}}} or {{{__name__}}} (though you can still call it whatever you want in your namespace) and are pickier about changing an object's {{{__class__}}}. See http://www.python.org/2.2.2/bugs.html for a list of expected converting-an-old-class-to-a-new-class problems. * When numeric operations (including "*", or "%") are applied to objects of different types, there is a fairly complex chain of logic to decide what should eventually happen. For old-style classes, there is often an attempt to Coerce the objects to the same type; for new style classes, there is no automatic call to {{{__coerce__}}}. (Really just an important example of the magic names change.) * An Exception cannot be a New-Style class. This is a wart that will probably be removed in 2.5. (As of 2.5a1, Exception is New Style.) Previously it was required because of some complex backward compatibility dances involving (deprecated) string exceptions and whether a raised object should be treated as a Class or as an Instance of a Class. Note that you can inherit from both Exception and object; you just can't raise the result. {{{ >>> class NewException(Exception, object): pass >>> raise NewException Traceback (most recent call last): File "", line 1, in -toplevel- raise NewException TypeError: exceptions must be classes, instances, or strings (deprecated), not type >>> raise NewException() Traceback (most recent call last): File "", line 1, in -toplevel- raise NewException() TypeError: exceptions must be classes, instances, or strings (deprecated), not NewException }}} * MRO; [[http://www.python.org/2.3/mro.html|Method Resolution Order]] Old Style classes search each base class, including the bases of the bases, Left To Right. New Style classes search each base class only once, and the order may be slightly different than what one would get with an ambiguous Old Style class. {{{ >>> class Old: pass >>> class O1(Old): pass >>> class O2(Old): pass >>> class OD(O1, O2): pass >>> OD.__mro__ Traceback (most recent call last): File "", line 1, in -toplevel- O.__mro__ AttributeError: class O has no attribute '__mro__' }}} OK, but write some methods to figure it out... and the effective MRO is OD, O1, Old, O2, Old So that Old is searched before its own derived class O2, then (uselessly) searched again at the end. {{{ >>> class New(object): pass >>> class N1(New): pass >>> class N2(New): pass >>> class ND(N1, N2): pass >>> ND.__mro__ (, , , , ) }}} So New (and its own base, object) is only searched once -- after *all* of its own subclasses have already been searched. Generally, the New MRO is better, but they aren't the same, and it can be painful to inherit from both types of class in the same derived class. One time when the older method did work better was mixin classes -- if you assume that methods will always be completely overridden (not just extended), then the old conventions are simpler and cleaner. If you need to combine methods, the old conventions (to explicitly call Base.method(self, args)) required a fragile knowledge of the inheritance hierarchy. ---- CategoryDocumentation On Thu, Oct 13, 2016 at 2:43 PM, Chris Angelico wrote: > On Fri, Oct 14, 2016 at 8:12 AM, Phillip Feldman > wrote: > > I created a wiki account. My user ID is PhillipMFeldman. > > > > No problem. I've made you an editor. > > ChrisA > -------------- next part -------------- An HTML attachment was scrubbed... URL: From woodswalben at gmail.com Mon Oct 17 13:55:34 2016 From: woodswalben at gmail.com (Walter Woods) Date: Mon, 17 Oct 2016 10:55:34 -0700 Subject: [pydotorg-www] Inclusion of job_stream in Parallel Processing wiki page Message-ID: Hello, Since normal users can no longer edit the wiki, I was wondering if someone would mind including job_stream (https://wwoods.github.io/job_stream/) on the Parallel Processing wiki page ( https://wiki.python.org/moin/ParallelProcessing). Maybe with a line like: An MPI-based C++ or Python library for easy, distributed pipeline processing, with an emphasis on running scientific simulations Thanks, Walt Woods -------------- next part -------------- An HTML attachment was scrubbed... URL: From steve at holdenweb.com Mon Oct 17 15:46:45 2016 From: steve at holdenweb.com (Steve Holden) Date: Mon, 17 Oct 2016 20:46:45 +0100 Subject: [pydotorg-www] Inclusion of job_stream in Parallel Processing wiki page In-Reply-To: References: Message-ID: Hi Walt, It isn't that we wish to discourage "normal" users, it's that their privileges were deomonstrably abused by spammers, and so now we hand edit privileges out when requested rather than permitting them generally. If you can create a Wiki account and let us know the username we can add you. Thanks very much for your interest in Python, and welcome to the Wiki community as an editor! Feel free to make other improvements you determine the need for. regards Steve Steve Holden On Mon, Oct 17, 2016 at 6:55 PM, Walter Woods wrote: > Hello, > > Since normal users can no longer edit the wiki, I was wondering if someone > would mind including job_stream (https://wwoods.github.io/job_stream/) on > the Parallel Processing wiki page (https://wiki.python.org/ > moin/ParallelProcessing). Maybe with a line like: > > An MPI-based C++ or Python library for easy, distributed pipeline > processing, with an emphasis on running scientific simulations > > Thanks, > Walt Woods > > _______________________________________________ > pydotorg-www mailing list > pydotorg-www at python.org > https://mail.python.org/mailman/listinfo/pydotorg-www > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From skip.montanaro at gmail.com Mon Oct 31 14:42:19 2016 From: skip.montanaro at gmail.com (Skip Montanaro) Date: Mon, 31 Oct 2016 13:42:19 -0500 Subject: [pydotorg-www] Steering search engines and users away from 3.0/3.1 docs? Message-ID: Not quite sure where this should go, so I'll start here. I needed to look up a bit more information about the timeit module than I happened to be carrying around in my noggin just now, so I asked Google to tell me about "Python timeit". The first three hits were: https://docs.python.org/2/library/timeit.html https://docs.python.org/3.0/library/timeit.html http://stackoverflow.com/questions/8220801/how-to-use-timeit-module The first and third hits are fine. The second, not so much. At this point, I think any and all links directly into the 3.0 (and maybe 3.1) documentation should perhaps redirect to the supported https://docs.python.org/3 pages, at least unless URLs carry some sort of "yes-damnit!" parameter. Maybe the robots.txt file should "disallow" traversal of the /3.0 and /3.1 trees as well. Just a couple thoughts... Skip Montanaro -------------- next part -------------- An HTML attachment was scrubbed... URL: From steve at holdenweb.com Mon Oct 31 14:51:54 2016 From: steve at holdenweb.com (Steve Holden) Date: Mon, 31 Oct 2016 18:51:54 +0000 Subject: [pydotorg-www] Steering search engines and users away from 3.0/3.1 docs? In-Reply-To: References: Message-ID: Good place to start. So, not acceptable because 3.0 rather than 3, right, and therefore not the current version? I could imagine a system whereby any reference to older versions was redirected to current if the source is a search engine. This should only be implemented for pages that can be version-selected. It seems to me this could be a feasible technical fix, but the question of whether this would be a desirable change remains to be debated. Not all problems should have technical solutions ... regards Steve PS: Spooky Halloween thought: I have no idea why pydotorg-www@ should be listed in my address book as "Food" ... Steve Holden On Mon, Oct 31, 2016 at 6:42 PM, Skip Montanaro wrote: > Not quite sure where this should go, so I'll start here. > > I needed to look up a bit more information about the timeit module than I > happened to be carrying around in my noggin just now, so I asked Google to > tell me about "Python timeit". The first three hits were: > > https://docs.python.org/2/library/timeit.html > https://docs.python.org/3.0/library/timeit.html > http://stackoverflow.com/questions/8220801/how-to-use-timeit-module > > The first and third hits are fine. The second, not so much. At this point, > I think any and all links directly into the 3.0 (and maybe 3.1) > documentation should perhaps redirect to the supported > https://docs.python.org/3 pages, at least unless URLs carry some sort of > "yes-damnit!" parameter. Maybe the robots.txt file should "disallow" > traversal of the /3.0 and /3.1 trees as well. > > Just a couple thoughts... > > Skip Montanaro > > > _______________________________________________ > pydotorg-www mailing list > pydotorg-www at python.org > https://mail.python.org/mailman/listinfo/pydotorg-www > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From mal at egenix.com Mon Oct 31 16:55:34 2016 From: mal at egenix.com (M.-A. Lemburg) Date: Mon, 31 Oct 2016 21:55:34 +0100 Subject: [pydotorg-www] Steering search engines and users away from 3.0/3.1 docs? In-Reply-To: References: Message-ID: <5817AFC6.5080202@egenix.com> On 31.10.2016 19:42, Skip Montanaro wrote: > Not quite sure where this should go, so I'll start here. > > I needed to look up a bit more information about the timeit module than I > happened to be carrying around in my noggin just now, so I asked Google to > tell me about "Python timeit". The first three hits were: > > https://docs.python.org/2/library/timeit.html > https://docs.python.org/3.0/library/timeit.html > http://stackoverflow.com/questions/8220801/how-to-use-timeit-module > > The first and third hits are fine. The second, not so much. At this point, > I think any and all links directly into the 3.0 (and maybe 3.1) > documentation should perhaps redirect to the supported > https://docs.python.org/3 pages, at least unless URLs carry some sort of > "yes-damnit!" parameter. Maybe the robots.txt file should "disallow" > traversal of the /3.0 and /3.1 trees as well. The idea with the robots.txt file is a good one; not sure about the suggestion to force a redirect to /3/, since those version, albeit un-maintained may still be in use. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Experts (#1, Oct 31 2016) >>> Python Projects, Coaching and Consulting ... http://www.egenix.com/ >>> Python Database Interfaces ... http://products.egenix.com/ >>> Plone/Zope Database Interfaces ... http://zope.egenix.com/ ________________________________________________________________________ ::: We implement business ideas - efficiently in both time and costs ::: eGenix.com Software, Skills and Services GmbH Pastor-Loeh-Str.48 D-40764 Langenfeld, Germany. CEO Dipl.-Math. Marc-Andre Lemburg Registered at Amtsgericht Duesseldorf: HRB 46611 http://www.egenix.com/company/contact/ http://www.malemburg.com/ From makj320 at gmail.com Mon Oct 31 18:34:48 2016 From: makj320 at gmail.com (Mak Jones) Date: Mon, 31 Oct 2016 15:34:48 -0700 Subject: [pydotorg-www] (no subject) Message-ID: -------------- next part -------------- An HTML attachment was scrubbed... URL: