| Numéro d’ID de bogue |
BUG-000179061 |
| Envoi | August 27, 2025 |
| Dernière modification | September 11, 2025 |
| S’applique à | ArcGIS Pro |
| Version trouvée | 3.4.3 |
| Système d’exploitation | Windows OS |
| Version du système d’exploitation | N/A |
| Statut | Known Limit
Après examen par l’équipe de développement, il a été déterminé que ce problème est lié à une limitation connue du logiciel sur laquelle Esri n’a aucun contrôle. Pour d’autres explications, reportez-vous à la section Informations supplémentaires correspondant au problème.
|
Informations supplémentaires
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)
Solution de contournement
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)
Étapes pour reproduire