topic Re: importing product level modules - still part of 10.1 as &quot;arcview,&quot; etc.? in Python Questions https://community.esri.com/t5/python-questions/importing-product-level-modules-still-part-of-10-1/m-p/312928#M24332 <HTML><HEAD></HEAD><BODY><SPAN>It's correct. Still using the old product names to maintain backwards compatibility.</SPAN></BODY></HTML> Tue, 26 Jun 2012 16:11:51 GMT JasonScheirer 2012-06-26T16:11:51Z importing product level modules - still part of 10.1 as &quot;arcview,&quot; etc.? https://community.esri.com/t5/python-questions/importing-product-level-modules-still-part-of-10-1/m-p/312927#M24331 <HTML><HEAD></HEAD><BODY><SPAN>I am looking at 10.1 Help online, since we haven't installed 10.1 locally yet. I saw this:</SPAN><BR /><BR /><SPAN>"The product level should be set by importing the appropriate product module (arcinfo, arceditor, arcview, arcserver, arcenginegeodb, or arcengine) prior to importing arcpy. "</SPAN><BR /><BR /><SPAN>Is this still correct? Or do we need to import using a different name ("basic," "standard," whatever)?</SPAN></BODY></HTML> Tue, 26 Jun 2012 15:33:31 GMT https://community.esri.com/t5/python-questions/importing-product-level-modules-still-part-of-10-1/m-p/312927#M24331 HarryBowman 2012-06-26T15:33:31Z Re: importing product level modules - still part of 10.1 as "arcview," etc.? https://community.esri.com/t5/python-questions/importing-product-level-modules-still-part-of-10-1/m-p/312928#M24332 <HTML><HEAD></HEAD><BODY><SPAN>It's correct. Still using the old product names to maintain backwards compatibility.</SPAN></BODY></HTML> Tue, 26 Jun 2012 16:11:51 GMT https://community.esri.com/t5/python-questions/importing-product-level-modules-still-part-of-10-1/m-p/312928#M24332 JasonScheirer 2012-06-26T16:11:51Z