<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: PEP 8 style guide in Python Questions</title>
    <link>https://community.esri.com/t5/python-questions/pep-8-style-guide/m-p/224227#M17318</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;I presume this is in reference to the capitalization scheme of the arcpy APIs. In this regard, no. It would break all existing scripts. The scheme, while not PEP-8 compliant, acts as a bridge between the naming and capitalization scheme of older scripting APIs such as the old Dispatch object.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;The rules are as follows:&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;UL&gt;&lt;BR /&gt;&lt;LI&gt;All top-level functions and classes are CapitalizedLikeThis&lt;/LI&gt;&lt;BR /&gt;&lt;LI&gt;All class methods and properties are capitalizedLikeThis&lt;/LI&gt;&lt;BR /&gt;&lt;LI&gt;Constants are PRESENTED_AS_ALL_CAPS_STRINGS&lt;/LI&gt;&lt;BR /&gt;&lt;/UL&gt;&lt;BR /&gt;&lt;SPAN&gt;As a long-time Python developer I appreciate the desire to follow PEP 8, but as the ArcGIS system is quite a bit larger and encompassing a lot more than just a single Python API, there are motivating factors that make more sense with a bit of compromise with regard to the rest of the stack. It has its own style guide that may not match 1:1 with PEP 8, but it does make sense in ArcGIS and arcpy is internally consistent in its naming.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Sun, 13 May 2012 08:58:24 GMT</pubDate>
    <dc:creator>JasonScheirer</dc:creator>
    <dc:date>2012-05-13T08:58:24Z</dc:date>
    <item>
      <title>PEP 8 style guide</title>
      <link>https://community.esri.com/t5/python-questions/pep-8-style-guide/m-p/224226#M17317</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Hi!&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I've been asking for criticism on my arcpy scripts by experienced Python programmers, and they all say arcpy needs to adhere to &lt;/SPAN&gt;&lt;A href="http://www.python.org/dev/peps/pep-0008/"&gt;the PEP 8 style guide&lt;/A&gt;&lt;SPAN&gt;. Is this likely to happen anytime soon?&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Thanks!&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 12 May 2012 06:27:49 GMT</pubDate>
      <guid>https://community.esri.com/t5/python-questions/pep-8-style-guide/m-p/224226#M17317</guid>
      <dc:creator>DwayneHenderson</dc:creator>
      <dc:date>2012-05-12T06:27:49Z</dc:date>
    </item>
    <item>
      <title>Re: PEP 8 style guide</title>
      <link>https://community.esri.com/t5/python-questions/pep-8-style-guide/m-p/224227#M17318</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;I presume this is in reference to the capitalization scheme of the arcpy APIs. In this regard, no. It would break all existing scripts. The scheme, while not PEP-8 compliant, acts as a bridge between the naming and capitalization scheme of older scripting APIs such as the old Dispatch object.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;The rules are as follows:&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;UL&gt;&lt;BR /&gt;&lt;LI&gt;All top-level functions and classes are CapitalizedLikeThis&lt;/LI&gt;&lt;BR /&gt;&lt;LI&gt;All class methods and properties are capitalizedLikeThis&lt;/LI&gt;&lt;BR /&gt;&lt;LI&gt;Constants are PRESENTED_AS_ALL_CAPS_STRINGS&lt;/LI&gt;&lt;BR /&gt;&lt;/UL&gt;&lt;BR /&gt;&lt;SPAN&gt;As a long-time Python developer I appreciate the desire to follow PEP 8, but as the ArcGIS system is quite a bit larger and encompassing a lot more than just a single Python API, there are motivating factors that make more sense with a bit of compromise with regard to the rest of the stack. It has its own style guide that may not match 1:1 with PEP 8, but it does make sense in ArcGIS and arcpy is internally consistent in its naming.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 13 May 2012 08:58:24 GMT</pubDate>
      <guid>https://community.esri.com/t5/python-questions/pep-8-style-guide/m-p/224227#M17318</guid>
      <dc:creator>JasonScheirer</dc:creator>
      <dc:date>2012-05-13T08:58:24Z</dc:date>
    </item>
  </channel>
</rss>

