<?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 Keep Python as the scripting language in Field Calculator in Python Questions</title>
    <link>https://community.esri.com/t5/python-questions/keep-python-as-the-scripting-language-in-field/m-p/676340#M52375</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I'm finally dragging myself kicking and screaming into Python after using VB for a number of years to calculate field values.&amp;nbsp; It's really frustrating to have a script run fine on one or two selected records, only to have it immediately bomb out on the entire table of records: especially when the only problem is the calculator has reverted back to VB automagically. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is there a way to keep Python as the scripting language default or, how do I keep it from reverting back to VB?&amp;nbsp;&amp;nbsp;&amp;nbsp; (Using version 10.0 desktop)&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 01 Dec 2014 19:59:37 GMT</pubDate>
    <dc:creator>JoeBorgione</dc:creator>
    <dc:date>2014-12-01T19:59:37Z</dc:date>
    <item>
      <title>Keep Python as the scripting language in Field Calculator</title>
      <link>https://community.esri.com/t5/python-questions/keep-python-as-the-scripting-language-in-field/m-p/676340#M52375</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I'm finally dragging myself kicking and screaming into Python after using VB for a number of years to calculate field values.&amp;nbsp; It's really frustrating to have a script run fine on one or two selected records, only to have it immediately bomb out on the entire table of records: especially when the only problem is the calculator has reverted back to VB automagically. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is there a way to keep Python as the scripting language default or, how do I keep it from reverting back to VB?&amp;nbsp;&amp;nbsp;&amp;nbsp; (Using version 10.0 desktop)&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 01 Dec 2014 19:59:37 GMT</pubDate>
      <guid>https://community.esri.com/t5/python-questions/keep-python-as-the-scripting-language-in-field/m-p/676340#M52375</guid>
      <dc:creator>JoeBorgione</dc:creator>
      <dc:date>2014-12-01T19:59:37Z</dc:date>
    </item>
    <item>
      <title>Re: Keep Python as the scripting language in Field Calculator</title>
      <link>https://community.esri.com/t5/python-questions/keep-python-as-the-scripting-language-in-field/m-p/676341#M52376</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Not as far as I know. It should retain python within a session, but not as a general setting. It would seem like a&amp;nbsp; no-brainer since ESRI's embraced python and VBScript is no longer supported, but there you have it. Maybe at 10.3 or 11, whenever they come out.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 01 Dec 2014 20:38:21 GMT</pubDate>
      <guid>https://community.esri.com/t5/python-questions/keep-python-as-the-scripting-language-in-field/m-p/676341#M52376</guid>
      <dc:creator>Zeke</dc:creator>
      <dc:date>2014-12-01T20:38:21Z</dc:date>
    </item>
    <item>
      <title>Re: Keep Python as the scripting language in Field Calculator</title>
      <link>https://community.esri.com/t5/python-questions/keep-python-as-the-scripting-language-in-field/m-p/676342#M52377</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;SPAN style="text-decoration: underline;"&gt;&lt;EM&gt;&lt;STRONG&gt;It should retain python within a session,&lt;/STRONG&gt;&lt;/EM&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="text-decoration: underline;"&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;That's what I figured, but for whatever reason, the script stays intact, but the radio button goes back to VB: it craps out in a hurry...&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 01 Dec 2014 21:03:40 GMT</pubDate>
      <guid>https://community.esri.com/t5/python-questions/keep-python-as-the-scripting-language-in-field/m-p/676342#M52377</guid>
      <dc:creator>JoeBorgione</dc:creator>
      <dc:date>2014-12-01T21:03:40Z</dc:date>
    </item>
    <item>
      <title>Re: Keep Python as the scripting language in Field Calculator</title>
      <link>https://community.esri.com/t5/python-questions/keep-python-as-the-scripting-language-in-field/m-p/676343#M52378</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Well, I'm on 10.2.2, maybe that particular bug has been taken care of, if I understand correctly. I've been caught by it myself before. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 01 Dec 2014 21:16:11 GMT</pubDate>
      <guid>https://community.esri.com/t5/python-questions/keep-python-as-the-scripting-language-in-field/m-p/676343#M52378</guid>
      <dc:creator>Zeke</dc:creator>
      <dc:date>2014-12-01T21:16:11Z</dc:date>
    </item>
    <item>
      <title>Re: Keep Python as the scripting language in Field Calculator</title>
      <link>https://community.esri.com/t5/python-questions/keep-python-as-the-scripting-language-in-field/m-p/676344#M52379</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The interactive right click field / calculate&amp;nbsp; method is the "old" way to do it and the interface is used to call the Calculate Field tool - after that first run you can recall it from the Results window where it will be "stuck" for you with the parameters you want.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 02 Dec 2014 04:22:01 GMT</pubDate>
      <guid>https://community.esri.com/t5/python-questions/keep-python-as-the-scripting-language-in-field/m-p/676344#M52379</guid>
      <dc:creator>curtvprice</dc:creator>
      <dc:date>2014-12-02T04:22:01Z</dc:date>
    </item>
    <item>
      <title>Re: Keep Python as the scripting language in Field Calculator</title>
      <link>https://community.esri.com/t5/python-questions/keep-python-as-the-scripting-language-in-field/m-p/676345#M52380</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;A href="https://c.na9.visual.force.com/apex/ideaView?id=08730000000brslAAA"&gt;https://c.na9.visual.force.com/apex/ideaView?id=08730000000brslAAA&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I posted this to the esri idea submission site in 2011, so go vote for it!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 02 Dec 2014 17:16:31 GMT</pubDate>
      <guid>https://community.esri.com/t5/python-questions/keep-python-as-the-scripting-language-in-field/m-p/676345#M52380</guid>
      <dc:creator>KevinBell</dc:creator>
      <dc:date>2014-12-02T17:16:31Z</dc:date>
    </item>
    <item>
      <title>Re: Keep Python as the scripting language in Field Calculator</title>
      <link>https://community.esri.com/t5/python-questions/keep-python-as-the-scripting-language-in-field/m-p/676346#M52381</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I don't think that's the link you want. Goes to SalesForce.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 02 Dec 2014 18:36:45 GMT</pubDate>
      <guid>https://community.esri.com/t5/python-questions/keep-python-as-the-scripting-language-in-field/m-p/676346#M52381</guid>
      <dc:creator>Zeke</dc:creator>
      <dc:date>2014-12-02T18:36:45Z</dc:date>
    </item>
    <item>
      <title>Re: Keep Python as the scripting language in Field Calculator</title>
      <link>https://community.esri.com/t5/python-questions/keep-python-as-the-scripting-language-in-field/m-p/676347#M52382</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Kevin,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I believe this is the link that you want:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://ideas.arcgis.com/ideaView?id=08730000000brslAAA" title="http://ideas.arcgis.com/ideaView?id=08730000000brslAAA"&gt;ArcGIS Idea - Field Calculator default to Python&lt;/A&gt;‌ &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 02 Dec 2014 18:47:21 GMT</pubDate>
      <guid>https://community.esri.com/t5/python-questions/keep-python-as-the-scripting-language-in-field/m-p/676347#M52382</guid>
      <dc:creator>AlexanderNohe1</dc:creator>
      <dc:date>2014-12-02T18:47:21Z</dc:date>
    </item>
    <item>
      <title>Re: Keep Python as the scripting language in Field Calculator</title>
      <link>https://community.esri.com/t5/python-questions/keep-python-as-the-scripting-language-in-field/m-p/676348#M52383</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Seems like a number of extra clicks just to get back to the old style right click on the field. But if that works for you, it's cool with me...&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 02 Dec 2014 20:18:23 GMT</pubDate>
      <guid>https://community.esri.com/t5/python-questions/keep-python-as-the-scripting-language-in-field/m-p/676348#M52383</guid>
      <dc:creator>JoeBorgione</dc:creator>
      <dc:date>2014-12-02T20:18:23Z</dc:date>
    </item>
  </channel>
</rss>

