title: PyCharm debug mode throws fake errors but runs normally when not in debug
body: <p><strong>EDIT</strong>: I rolled back PyCharm versions and it's working again. CLEARLY an IDE issue, not a script issue now. PyCharm version 2017.2.4 is what I rolled back to.</p>
  
  <p>So I have a script that's been working great for me, until today. For some reason, the script will run fine with no errors at all, as long as I don't use PyCharm (Community Edition 2017.3.3) in debugging mode. I need to use debugger, so when it throws errors for no reason and stops the script, it makes it a pointless IDE.</p>
  
  <p>The reason I know this is a PyCharm problem is because I copied the entire script into a different IDE (Wing), set to the same python interpreter, and went through it in debug mode there and it worked fine, no errors.</p>
  
  <p>I have done extensive error testing to make sure the errors aren't actually there in my script; they're not. The script should work as written. It keeps saying datasets don't exist or input features for arcpy tools (a spatial program that hooks into python via a library called "arcpy") don't have values when they do. It's not a script problem, it's an IDE problem.</p>
  
  <p>Has anybody encountered this and know how to fix it?</p>
  
  <p>I do not have any specific environment settings, I just popped an ArcGIS python interpreter in there for the project so I could have access to the arcpy library and that's it. It should be noted that this interpreter is python 2.7 because ArcGIS is not yet compatible with python 3+. I doubt that has anything to do with it, but you never know...</p>
  
  <p>This is a chunk of script causing the issues (if you don't have/know how to use ArcGIS don't bother trying to run it, it won't work for you). What I want to point out is that if I put a breakpoint at the <code>qh_buffer</code> line, it will break after trying to run that line with an arcpy error message that states invalid input/parameters (they are not invalid, it's written exactly how it should be and I have checked that <code>qhPolys</code> is being created and exists). THEN, if I move the breakpoint to the <code>crop_intersect</code> line and run it in debug, it runs through the entire code, INCLUDING the buffer statement, but then errors out with error 000732 "Input Features: Dataset #1; #2 does not exist or is not supported" (they both do exist, because I have hardcoded them to an output directory before and they are created just fine).</p>
  
  <pre><code>import arcpy
  
  arcpy.env.overwriteOutput = True
  
  svyPtFC = r"C:\Users\xxx\GIS_Testing\Crop_Test.shp"
  
  select_query = '"FID" = 9'
  
  qhPolys = arcpy.Select_analysis(svyPtFC, 'in_memory/qhPolys', select_query)
  qh_buffer = arcpy.Buffer_analysis(qhPolys, 'in_memory/qh_buffer', '50 
  Meters')
  cropFID = '"FID" = 1'
  cropPoly = arcpy.Select_analysis(svyPtFC, 'in_memory/cropPoly', cropFID)
  crop_intersect = arcpy.Intersect_analysis([[cropPoly, 1], [qh_buffer, 2]],
                                        r'C:\Users\xxx\GIS_Testing\crp_int.shp')
  feature_count = arcpy.GetCount_management(crop_intersect)
  print feature_count
  </code></pre>
  
  <p>It does not make sense that it can cause an error at the buffer line if I put a breakpoint near there, but then if I move the breakpoint further down, that line will run fine and it'll just break at the next breakpoint... does explain why it works when you just hit "Run" instead of doing debug mode though. No breakpoints!</p>