<?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>idea Improve ArcPy List Functions Documentation: Explain Wildcard Position in Python Ideas</title>
    <link>https://community.esri.com/t5/python-ideas/improve-arcpy-list-functions-documentation-explain/idi-p/1675233</link>
    <description>&lt;P&gt;The current ArcPy documentation for List functions (ListWorkspaces, ListFeatureClasses, etc.) only briefly mentions that the wildcard * represents “zero or more characters” and is case-insensitive. However, it does not explain how the position of the wildcard (start, end, or both) affects the results.&lt;/P&gt;&lt;P&gt;The example below demonstrates the difference between patterns '*.gdb', 'ALI_BIO*', and '*ALI*'. Adding such examples to the documentation would help users understand wildcard behavior and avoid confusion.&lt;/P&gt;&lt;LI-CODE lang="python"&gt;import arcpy

# Set the workspace
arcpy.env.workspace = r"C:\GIS\Projects"

# Example 1: Any item ending with .gdb
ending_gdb = arcpy.ListWorkspaces("*.gdb")
print("Pattern '*.gdb' matches:", ending_gdb)

# Example 2: Any item starting with ALI_BIO
starting_ref = arcpy.ListWorkspaces("ALI_BIO*")
print("Pattern 'ALI_BIO*' matches:", starting_ref)

# Example 3: Any item containing ALI anywhere
contains_tpt = arcpy.ListWorkspaces("*ALI*")
print("Pattern '*ALI*' matches:", contains_tpt)
 &lt;/LI-CODE&gt;</description>
    <pubDate>Tue, 30 Dec 2025 00:57:59 GMT</pubDate>
    <dc:creator>AliTalaat22</dc:creator>
    <dc:date>2025-12-30T00:57:59Z</dc:date>
    <item>
      <title>Improve ArcPy List Functions Documentation: Explain Wildcard Position</title>
      <link>https://community.esri.com/t5/python-ideas/improve-arcpy-list-functions-documentation-explain/idi-p/1675233</link>
      <description>&lt;P&gt;The current ArcPy documentation for List functions (ListWorkspaces, ListFeatureClasses, etc.) only briefly mentions that the wildcard * represents “zero or more characters” and is case-insensitive. However, it does not explain how the position of the wildcard (start, end, or both) affects the results.&lt;/P&gt;&lt;P&gt;The example below demonstrates the difference between patterns '*.gdb', 'ALI_BIO*', and '*ALI*'. Adding such examples to the documentation would help users understand wildcard behavior and avoid confusion.&lt;/P&gt;&lt;LI-CODE lang="python"&gt;import arcpy

# Set the workspace
arcpy.env.workspace = r"C:\GIS\Projects"

# Example 1: Any item ending with .gdb
ending_gdb = arcpy.ListWorkspaces("*.gdb")
print("Pattern '*.gdb' matches:", ending_gdb)

# Example 2: Any item starting with ALI_BIO
starting_ref = arcpy.ListWorkspaces("ALI_BIO*")
print("Pattern 'ALI_BIO*' matches:", starting_ref)

# Example 3: Any item containing ALI anywhere
contains_tpt = arcpy.ListWorkspaces("*ALI*")
print("Pattern '*ALI*' matches:", contains_tpt)
 &lt;/LI-CODE&gt;</description>
      <pubDate>Tue, 30 Dec 2025 00:57:59 GMT</pubDate>
      <guid>https://community.esri.com/t5/python-ideas/improve-arcpy-list-functions-documentation-explain/idi-p/1675233</guid>
      <dc:creator>AliTalaat22</dc:creator>
      <dc:date>2025-12-30T00:57:59Z</dc:date>
    </item>
    <item>
      <title>Re: Improve ArcPy List Functions Documentation: Explain Wildcard Position</title>
      <link>https://community.esri.com/t5/python-ideas/improve-arcpy-list-functions-documentation-explain/idc-p/1675264#M564</link>
      <description>&lt;P&gt;&lt;a href="https://community.esri.com/t5/user/viewprofilepage/user-id/961005"&gt;@AliTalaat22&lt;/a&gt;&amp;nbsp;, wildcard behavior is fairly standard across programming/scripting languages and commands.&amp;nbsp; Is there specific wildcard behavior that you are finding unexpected?&amp;nbsp; If so, can you provide an example?&lt;/P&gt;</description>
      <pubDate>Tue, 30 Dec 2025 14:04:19 GMT</pubDate>
      <guid>https://community.esri.com/t5/python-ideas/improve-arcpy-list-functions-documentation-explain/idc-p/1675264#M564</guid>
      <dc:creator>JoshuaBixby</dc:creator>
      <dc:date>2025-12-30T14:04:19Z</dc:date>
    </item>
    <item>
      <title>Re: Improve ArcPy List Functions Documentation: Explain Wildcard Position</title>
      <link>https://community.esri.com/t5/python-ideas/improve-arcpy-list-functions-documentation-explain/idc-p/1675267#M565</link>
      <description>&lt;P&gt;many of the use cases are contained within the code samples, for example from&lt;/P&gt;&lt;P&gt;&lt;A href="https://pro.arcgis.com/en/pro-app/latest/arcpy/functions/listdatasets.htm" target="_blank"&gt;ListDatasets—ArcGIS Pro | Documentation&lt;/A&gt;&lt;/P&gt;&lt;LI-CODE lang="python"&gt;# Print all the feature datasets in the workspace that start with the letter c
# or f.
datasets1 = list(set(arcpy.ListDatasets("c*", "Feature")) |
                 set(arcpy.ListDatasets("f*", "Feature")))
print(datasets1)&lt;/LI-CODE&gt;&lt;P&gt;or&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="python"&gt;# Print all the feature datasets in the workspace that contain both the letter c
# and f.
datasets3 = list(set(arcpy.ListDatasets("*c*", "Feature")) &amp;amp;
                 set(arcpy.ListDatasets("*f*", "Feature")))
print(datasets3)&lt;/LI-CODE&gt;&lt;P&gt;so yes, specific examples of unexpected behaviour would be useful&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 30 Dec 2025 14:19:40 GMT</pubDate>
      <guid>https://community.esri.com/t5/python-ideas/improve-arcpy-list-functions-documentation-explain/idc-p/1675267#M565</guid>
      <dc:creator>DanPatterson</dc:creator>
      <dc:date>2025-12-30T14:19:40Z</dc:date>
    </item>
  </channel>
</rss>

