| Bug-ID-Nummer |
BUG-000179061 |
| Eingereicht | August 27, 2025 |
| Zuletzt geändert | September 11, 2025 |
| Gilt für | ArcGIS Pro |
| Gefunden in Version | 3.4.3 |
| Betriebssystem | Windows OS |
| Betriebssystemversion | N/A |
| Status | Known Limit
Nach Überprüfung durch das Entwicklungsteam wurde festgestellt, dass dieses Problem im Zusammenhang mit einer bekannten Einschränkung der Software steht, die außerhalb der Kontrolle von Esri liegt. Weitere Erläuterungen finden Sie ggf. im Abschnitt "Zusätzliche Informationen" des jeweiligen Problems.
|
Zusätzliche Informationen
This behavior is as designed and is a known limitation. When passing only the name of a feature class to arcpy.Describe (and other functions or tools that accept a short name), it first looks for the feature class in the layers of the map. If no layer is found, it then searches in the arcpy.env.workspace. Many tools, functions, and user workflows are dependent on the software behaving this way. The documentation is updated to better represent this expected behavior.
The best practice when writing scripts is to pass through the fully qualified path of the object to the function or tool. The path can be built from prior pieces of code:
path = os.path.join(arcpy.env.workspace, ds, fc)
arcpy.Describe(path)
Workaround
Use best practices when writing scripts by passing through the fully qualified path of the object to the function or tool. The path can be built from prior pieces of code: path = os.path.join(arcpy.env.workspace, ds, fc) arcpy.Describe(path)
Schritte zur Reproduzierung