pycatia3dx 0.1__tar.gz

pycatia3dx-0.1/.gitignore

@@ -0,0 +1,216 @@
+# Byte-compiled / optimized / DLL files
+__pycache__/
+*.py[codz]
+*$py.class
+
+# C extensions
+*.so
+
+# Distribution / packaging
+.Python
+build/
+develop-eggs/
+dist/
+downloads/
+eggs/
+.eggs/
+lib/
+lib64/
+parts/
+sdist/
+var/
+wheels/
+share/python-wheels/
+*.egg-info/
+.installed.cfg
+*.egg
+MANIFEST
+
+# PyInstaller
+#  Usually these files are written by a python script from a template
+#  before PyInstaller builds the exe, so as to inject date/other infos into it.
+*.manifest
+*.spec
+
+# Installer logs
+pip-log.txt
+pip-delete-this-directory.txt
+
+# Unit test / coverage reports
+htmlcov/
+.tox/
+.nox/
+.coverage
+.coverage.*
+.cache
+nosetests.xml
+coverage.xml
+*.cover
+*.py.cover
+.hypothesis/
+.pytest_cache/
+cover/
+
+# Translations
+*.mo
+*.pot
+
+# Django stuff:
+*.log
+local_settings.py
+db.sqlite3
+db.sqlite3-journal
+
+# Flask stuff:
+instance/
+.webassets-cache
+
+# Scrapy stuff:
+.scrapy
+
+# Sphinx documentation
+docs/_build/
+
+# PyBuilder
+.pybuilder/
+target/
+
+# Jupyter Notebook
+.ipynb_checkpoints
+
+# IPython
+profile_default/
+ipython_config.py
+
+# pyenv
+#   For a library or package, you might want to ignore these files since the code is
+#   intended to run in multiple environments; otherwise, check them in:
+# .python-version
+
+# pipenv
+#   According to pypa/pipenv#598, it is recommended to include Pipfile.lock in version control.
+#   However, in case of collaboration, if having platform-specific dependencies or dependencies
+#   having no cross-platform support, pipenv may install dependencies that don't work, or not
+#   install all needed dependencies.
+#Pipfile.lock
+
+# UV
+#   Similar to Pipfile.lock, it is generally recommended to include uv.lock in version control.
+#   This is especially recommended for binary packages to ensure reproducibility, and is more
+#   commonly ignored for libraries.
+#uv.lock
+
+# poetry
+#   Similar to Pipfile.lock, it is generally recommended to include poetry.lock in version control.
+#   This is especially recommended for binary packages to ensure reproducibility, and is more
+#   commonly ignored for libraries.
+#   https://python-poetry.org/docs/basic-usage/#commit-your-poetrylock-file-to-version-control
+#poetry.lock
+#poetry.toml
+
+# pdm
+#   Similar to Pipfile.lock, it is generally recommended to include pdm.lock in version control.
+#   pdm recommends including project-wide configuration in pdm.toml, but excluding .pdm-python.
+#   https://pdm-project.org/en/latest/usage/project/#working-with-version-control
+#pdm.lock
+#pdm.toml
+.pdm-python
+.pdm-build/
+
+# pixi
+#   Similar to Pipfile.lock, it is generally recommended to include pixi.lock in version control.
+#pixi.lock
+#   Pixi creates a virtual environment in the .pixi directory, just like venv module creates one
+#   in the .venv directory. It is recommended not to include this directory in version control.
+.pixi
+
+# PEP 582; used by e.g. github.com/David-OConnor/pyflow and github.com/pdm-project/pdm
+__pypackages__/
+
+# Celery stuff
+celerybeat-schedule
+celerybeat.pid
+
+# SageMath parsed files
+*.sage.py
+
+# Environments
+.env
+.envrc
+.venv
+env/
+venv/
+ENV/
+env.bak/
+venv.bak/
+
+# Spyder project settings
+.spyderproject
+.spyproject
+
+# Rope project settings
+.ropeproject
+
+# mkdocs documentation
+/site
+
+# mypy
+.mypy_cache/
+.dmypy.json
+dmypy.json
+
+# Pyre type checker
+.pyre/
+
+# pytype static type analyzer
+.pytype/
+
+# Cython debug symbols
+cython_debug/
+
+# PyCharm
+#  JetBrains specific template is maintained in a separate JetBrains.gitignore that can
+#  be found at https://github.com/github/gitignore/blob/main/Global/JetBrains.gitignore
+#  and can be added to the global gitignore or merged into this file.  For a more nuclear
+#  option (not recommended) you can uncomment the following to ignore the entire idea folder.
+#.idea/
+
+# Abstra
+# Abstra is an AI-powered process automation framework.
+# Ignore directories containing user credentials, local state, and settings.
+# Learn more at https://abstra.io/docs
+.abstra/
+
+# Visual Studio Code
+#  Visual Studio Code specific template is maintained in a separate VisualStudioCode.gitignore 
+#  that can be found at https://github.com/github/gitignore/blob/main/Global/VisualStudioCode.gitignore
+#  and can be added to the global gitignore or merged into this file. However, if you prefer, 
+#  you could uncomment the following to ignore the entire vscode folder
+# .vscode/
+
+# Ruff stuff:
+.ruff_cache/
+
+# PyPI configuration file
+.pypirc
+
+# Cursor
+#  Cursor is an AI-powered code editor. `.cursorignore` specifies files/directories to
+#  exclude from AI features like autocomplete and code analysis. Recommended for sensitive data
+#  refer to https://docs.cursor.com/context/ignore-files
+.cursorignore
+.cursorindexingignore
+
+# Marimo
+marimo/_static/
+marimo/_lsp/
+__marimo__/
+
+.idea/
+
+__reference_scripts__
+__junk__
+
+temp*.py
+
+docs/generated/

pycatia3dx-0.1/CODE_OF_CONDUCT.md

@@ -0,0 +1,93 @@
+
+# Contributor Covenant 3.0 Code of Conduct
+
+## Our Pledge
+
+We pledge to make our community welcoming, safe, and equitable for all.
+
+We are committed to fostering an environment that respects and promotes the dignity, rights, and contributions of all individuals, regardless of characteristics including race, ethnicity, caste, color, age, physical characteristics, neurodiversity, disability, sex or gender, gender identity or expression, sexual orientation, language, philosophy or religion, national or social origin, socio-economic position, level of education, or other status. The same privileges of participation are extended to everyone who participates in good faith and in accordance with this Covenant.
+
+
+## Encouraged Behaviors
+
+While acknowledging differences in social norms, we all strive to meet our community's expectations for positive behavior. We also understand that our words and actions may be interpreted differently than we intend based on culture, background, or native language.
+
+With these considerations in mind, we agree to behave mindfully toward each other and act in ways that center our shared values, including:
+
+1. Respecting the **purpose of our community**, our activities, and our ways of gathering.
+2. Engaging **kindly and honestly** with others.
+3. Respecting **different viewpoints** and experiences.
+4. **Taking responsibility** for our actions and contributions.
+5. Gracefully giving and accepting **constructive feedback**.
+6. Committing to **repairing harm** when it occurs.
+7. Behaving in other ways that promote and sustain the **well-being of our community**.
+
+
+## Restricted Behaviors
+
+We agree to restrict the following behaviors in our community. Instances, threats, and promotion of these behaviors are violations of this Code of Conduct.
+
+1. **Harassment.** Violating explicitly expressed boundaries or engaging in unnecessary personal attention after any clear request to stop.
+2. **Character attacks.** Making insulting, demeaning, or pejorative comments directed at a community member or group of people.
+3. **Stereotyping or discrimination.** Characterizing anyone’s personality or behavior on the basis of immutable identities or traits.
+4. **Sexualization.** Behaving in a way that would generally be considered inappropriately intimate in the context or purpose of the community.
+5. **Violating confidentiality**. Sharing or acting on someone's personal or private information without their permission.
+6. **Endangerment.** Causing, encouraging, or threatening violence or other harm toward any person or group.
+7. Behaving in other ways that **threaten the well-being** of our community.
+
+### Other Restrictions
+
+1. **Misleading identity.** Impersonating someone else for any reason, or pretending to be someone else to evade enforcement actions.
+2. **Failing to credit sources.** Not properly crediting the sources of content you contribute.
+3. **Promotional materials**. Sharing marketing or other commercial content in a way that is outside the norms of the community.
+4. **Irresponsible communication.** Failing to responsibly present content which includes, links or describes any other restricted behaviors.
+
+
+## Reporting an Issue
+
+Tensions can occur between community members even when they are trying their best to collaborate. Not every conflict represents a code of conduct violation, and this Code of Conduct reinforces encouraged behaviors and norms that can help avoid conflicts and minimize harm.
+
+When an incident does occur, it is important to report it promptly. To report a possible violation, **[NOTE: describe your means of reporting here.]**
+
+Community Moderators take reports of violations seriously and will make every effort to respond in a timely manner. They will investigate all reports of code of conduct violations, reviewing messages, logs, and recordings, or interviewing witnesses and other participants. Community Moderators will keep investigation and enforcement actions as transparent as possible while prioritizing safety and confidentiality. In order to honor these values, enforcement actions are carried out in private with the involved parties, but communicating to the whole community may be part of a mutually agreed upon resolution.
+
+
+## Addressing and Repairing Harm
+
+**[NOTE: The remedies and repairs outlined below are suggestions based on best practices in code of conduct enforcement. If your community has its own established enforcement process, be sure to edit this section to describe your own policies.]**
+
+If an investigation by the Community Moderators finds that this Code of Conduct has been violated, the following enforcement ladder may be used to determine how best to repair harm, based on the incident's impact on the individuals involved and the community as a whole. Depending on the severity of a violation, lower rungs on the ladder may be skipped.
+
+1) Warning
+   1) Event: A violation involving a single incident or series of incidents.
+   2) Consequence: A private, written warning from the Community Moderators.
+   3) Repair: Examples of repair include a private written apology, acknowledgement of responsibility, and seeking clarification on expectations.
+2) Temporarily Limited Activities
+   1) Event: A repeated incidence of a violation that previously resulted in a warning, or the first incidence of a more serious violation.
+   2) Consequence: A private, written warning with a time-limited cooldown period designed to underscore the seriousness of the situation and give the community members involved time to process the incident. The cooldown period may be limited to particular communication channels or interactions with particular community members.
+   3) Repair: Examples of repair may include making an apology, using the cooldown period to reflect on actions and impact, and being thoughtful about re-entering community spaces after the period is over.
+3) Temporary Suspension
+   1) Event: A pattern of repeated violation which the Community Moderators have tried to address with warnings, or a single serious violation.
+   2) Consequence: A private written warning with conditions for return from suspension. In general, temporary suspensions give the person being suspended time to reflect upon their behavior and possible corrective actions.
+   3) Repair: Examples of repair include respecting the spirit of the suspension, meeting the specified conditions for return, and being thoughtful about how to reintegrate with the community when the suspension is lifted.
+4) Permanent Ban
+   1) Event: A pattern of repeated code of conduct violations that other steps on the ladder have failed to resolve, or a violation so serious that the Community Moderators determine there is no way to keep the community safe with this person as a member.
+   2) Consequence: Access to all community spaces, tools, and communication channels is removed. In general, permanent bans should be rarely used, should have strong reasoning behind them, and should only be resorted to if working through other remedies has failed to change the behavior.
+   3) Repair: There is no possible repair in cases of this severity.
+
+This enforcement ladder is intended as a guideline. It does not limit the ability of Community Managers to use their discretion and judgment, in keeping with the best interests of our community.
+
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when an individual is officially representing the community in public or other spaces. Examples of representing our community include using an official email address, posting via an official social media account, or acting as an appointed representative at an online or offline event.
+
+
+## Attribution
+
+This Code of Conduct is adapted from the Contributor Covenant, version 3.0, permanently available at [https://www.contributor-covenant.org/version/3/0/](https://www.contributor-covenant.org/version/3/0/).
+
+Contributor Covenant is stewarded by the Organization for Ethical Source and licensed under CC BY-SA 4.0. To view a copy of this license, visit [https://creativecommons.org/licenses/by-sa/4.0/](https://creativecommons.org/licenses/by-sa/4.0/)
+
+For answers to common questions about Contributor Covenant, see the FAQ at [https://www.contributor-covenant.org/faq](https://www.contributor-covenant.org/faq). Translations are provided at [https://www.contributor-covenant.org/translations](https://www.contributor-covenant.org/translations). Additional enforcement and community guideline resources can be found at [https://www.contributor-covenant.org/resources](https://www.contributor-covenant.org/resources). The enforcement ladder was inspired by the work of [Mozilla’s code of conduct team](https://github.com/mozilla/inclusion).
+

pycatia3dx-0.1/CONTRIBUTORS.md

@@ -0,0 +1 @@
+HdCadUser

pycatia3dx-0.1/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2025 Paul Bourne
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

pycatia3dx-0.1/PKG-INFO

@@ -0,0 +1,103 @@
+Metadata-Version: 2.5
+Name: pycatia3dx
+Version: 0.1
+Summary: A python package for automation of the CATIA 3DEXPERIENCE cad application.
+Project-URL: Hompagepage, https://github.com/evereux/pycatia3dx
+Project-URL: Issues, https://github.com/evereux/pycatia3dx/issues
+Author-email: Paul Bourne <evereux@gmail.com>
+License-Expression: MIT
+License-File: LICENSE
+Classifier: Operating System :: Microsoft :: Windows :: Windows 10
+Classifier: Operating System :: Microsoft :: Windows :: Windows 11
+Classifier: Programming Language :: Python :: 3
+Requires-Python: >=3.12
+Requires-Dist: pywin32==312
+Description-Content-Type: text/markdown
+
+pycatia3dx
+==========
+
+alpha software
+--------------
+
+This is alpha software.
+
+Please report any issues with using the package on github providing a stripped
+down script.
+
+Requirements
+------------
+
+* python >= 3.12
+* **CATIA 3DExperience** running on Windows.
+* see requirements.txt
+
+Installation
+------------
+
+There is currently no pypi package available. You'll need to clone the github
+repository or download the github archive.
+
+
+Usage
+-----
+
+See the examples: https://github.com/evereux/pycatia3dx/tree/main/examples
+
+
+Links
+-----
+
+todo
+
+
+
+Examples And Scripts
+--------------------
+
+https://github.com/evereux/pycatia3dx/tree/main/examples
+
+
+Asking Questions
+----------------
+
+Please read the following with regards to raising questions: https://github.com/evereux/pycatia/issues/28
+
+
+Contributing
+------------
+
+See CONTRIBUTING.md in root of github repository.
+
+Running The Tests
+-----------------
+
+Prior to running you will need to create the test files. This script will also
+check that you have all the test files created and they are the latest version
+so it's worth running each time you upgrade pycatia3dx
+
+.. code-block:: python
+
+    python .\tests\check_test_files.py
+
+CATIA 3DExperience shall already be running and all documents are closed. If
+this isn't the case the tests will not run and you'll be presented with a
+warning.
+
+To run the tests with coverage (-v is verbosity):
+
+.. code-block:: python
+
+    py.test -v --cov-report term-missing --cov=pycatia3dx
+
+To run tests for a specific module
+
+.. code-block:: python
+
+    py.test -v tests/in/hybrid_shapes/test_hybrid_shape_factory.py
+
+To stop tests running after first failure.
+
+    py.test -vx
+
+

pycatia3dx-0.1/README.md

@@ -0,0 +1,87 @@
+pycatia3dx
+==========
+
+alpha software
+--------------
+
+This is alpha software.
+
+Please report any issues with using the package on github providing a stripped
+down script.
+
+Requirements
+------------
+
+* python >= 3.12
+* **CATIA 3DExperience** running on Windows.
+* see requirements.txt
+
+Installation
+------------
+
+There is currently no pypi package available. You'll need to clone the github
+repository or download the github archive.
+
+
+Usage
+-----
+
+See the examples: https://github.com/evereux/pycatia3dx/tree/main/examples
+
+
+Links
+-----
+
+todo
+
+
+
+Examples And Scripts
+--------------------
+
+https://github.com/evereux/pycatia3dx/tree/main/examples
+
+
+Asking Questions
+----------------
+
+Please read the following with regards to raising questions: https://github.com/evereux/pycatia/issues/28
+
+
+Contributing
+------------
+
+See CONTRIBUTING.md in root of github repository.
+
+Running The Tests
+-----------------
+
+Prior to running you will need to create the test files. This script will also
+check that you have all the test files created and they are the latest version
+so it's worth running each time you upgrade pycatia3dx
+
+.. code-block:: python
+
+    python .\tests\check_test_files.py
+
+CATIA 3DExperience shall already be running and all documents are closed. If
+this isn't the case the tests will not run and you'll be presented with a
+warning.
+
+To run the tests with coverage (-v is verbosity):
+
+.. code-block:: python
+
+    py.test -v --cov-report term-missing --cov=pycatia3dx
+
+To run tests for a specific module
+
+.. code-block:: python
+
+    py.test -v tests/in/hybrid_shapes/test_hybrid_shape_factory.py
+
+To stop tests running after first failure.
+
+    py.test -vx
+
+

pycatia3dx-0.1/docs/Makefile

@@ -0,0 +1,20 @@
+# Minimal makefile for Sphinx documentation
+#
+
+# You can set these variables from the command line, and also
+# from the environment for the first two.
+SPHINXOPTS    ?=
+SPHINXBUILD   ?= sphinx-build
+SOURCEDIR     = .
+BUILDDIR      = _build
+
+# Put it first so that "make" without argument is like "make help".
+help:
+	@$(SPHINXBUILD) -M help "$(SOURCEDIR)" "$(BUILDDIR)" $(SPHINXOPTS) $(O)
+
+.PHONY: help Makefile
+
+# Catch-all target: route all unknown targets to Sphinx using the new
+# "make mode" option.  $(O) is meant as a shortcut for $(SPHINXOPTS).
+%: Makefile
+	@$(SPHINXBUILD) -M $@ "$(SOURCEDIR)" "$(BUILDDIR)" $(SPHINXOPTS) $(O)

pycatia3dx-0.1/docs/api/index_agt.rst

@@ -0,0 +1,25 @@
+pycatia3dx.agt
+==============
+
+.. toctree::
+   :maxdepth: 1
+   :caption: Contents:
+
+
+   pycatia3dx/agt/agt_category_mngt
+   pycatia3dx/agt/agt_connector
+   pycatia3dx/agt/agt_connectors
+   pycatia3dx/agt/agt_draught_stop
+   pycatia3dx/agt/agt_draught_stops
+   pycatia3dx/agt/agt_fire_bridge
+   pycatia3dx/agt/agt_fire_bridges
+   pycatia3dx/agt/agt_insulation
+   pycatia3dx/agt/agt_insulations
+   pycatia3dx/agt/agt_material_mngt
+   pycatia3dx/agt/agt_root
+   pycatia3dx/agt/agt_sill
+   pycatia3dx/agt/agt_sills
+   pycatia3dx/agt/covering
+   pycatia3dx/agt/coverings
+   pycatia3dx/agt/wall
+   pycatia3dx/agt/walls

pycatia3dx-0.1/docs/api/index_annotation.rst

@@ -0,0 +1,30 @@
+pycatia3dx.annotation
+=====================
+
+.. toctree::
+   :maxdepth: 1
+   :caption: Contents:
+
+
+   pycatia3dx/annotation/drawing_arrow
+   pycatia3dx/annotation/drawing_arrows
+   pycatia3dx/annotation/drawing_coord_dim
+   pycatia3dx/annotation/drawing_coord_dims
+   pycatia3dx/annotation/drawing_dim_ext_line
+   pycatia3dx/annotation/drawing_dim_line
+   pycatia3dx/annotation/drawing_dim_value
+   pycatia3dx/annotation/drawing_dimension
+   pycatia3dx/annotation/drawing_dimensions
+   pycatia3dx/annotation/drawing_gdt
+   pycatia3dx/annotation/drawing_gdts
+   pycatia3dx/annotation/drawing_leader
+   pycatia3dx/annotation/drawing_leaders
+   pycatia3dx/annotation/drawing_table
+   pycatia3dx/annotation/drawing_tables
+   pycatia3dx/annotation/drawing_text
+   pycatia3dx/annotation/drawing_text_properties
+   pycatia3dx/annotation/drawing_text_range
+   pycatia3dx/annotation/drawing_texts
+   pycatia3dx/annotation/drawing_welding
+   pycatia3dx/annotation/drawing_weldings
+   pycatia3dx/annotation/enums

pycatia3dx-0.1/docs/api/index_base_interfaces.rst

@@ -0,0 +1,10 @@
+pycatia3dx.base_interfaces
+==========================
+
+.. toctree::
+   :maxdepth: 1
+   :caption: Contents:
+
+
+   pycatia3dx/base_interfaces/base_application
+   pycatia3dx/base_interfaces/pycatia3dx

pycatia3dx-0.1/docs/api/index_behaviour.rst

@@ -0,0 +1,11 @@
+pycatia3dx.behaviour
+====================
+
+.. toctree::
+   :maxdepth: 1
+   :caption: Contents:
+
+
+   pycatia3dx/behaviour/dpc_operation
+   pycatia3dx/behaviour/dpc_operation_vb_script
+   pycatia3dx/behaviour/dpc_operations

pycatia3dx-0.1/docs/api/index_composites_use.rst

@@ -0,0 +1,10 @@
+pycatia3dx.composites_use
+=========================
+
+.. toctree::
+   :maxdepth: 1
+   :caption: Contents:
+
+
+   pycatia3dx/composites_use/composites_services
+   pycatia3dx/composites_use/enums

pycatia3dx-0.1/docs/api/index_del_curve_trajectory.rst

@@ -0,0 +1,23 @@
+pycatia3dx.del_curve_trajectory
+===============================
+
+.. toctree::
+   :maxdepth: 1
+   :caption: Contents:
+
+
+   pycatia3dx/del_curve_trajectory/ctm_contour
+   pycatia3dx/del_curve_trajectory/ctm_contour_from_curves
+   pycatia3dx/del_curve_trajectory/ctm_contour_from_points
+   pycatia3dx/del_curve_trajectory/ctm_contour_from_surfaces
+   pycatia3dx/del_curve_trajectory/ctm_curve_orienter
+   pycatia3dx/del_curve_trajectory/ctm_curve_sampler
+   pycatia3dx/del_curve_trajectory/ctm_curve_sampler_distance
+   pycatia3dx/del_curve_trajectory/ctm_curve_sampler_number
+   pycatia3dx/del_curve_trajectory/ctm_curve_sampler_speed
+   pycatia3dx/del_curve_trajectory/ctm_path
+   pycatia3dx/del_curve_trajectory/ctm_path_mgt
+   pycatia3dx/del_curve_trajectory/ctm_safe_path
+   pycatia3dx/del_curve_trajectory/curve_trajectory
+   pycatia3dx/del_curve_trajectory/curve_trajectory_factory
+   pycatia3dx/del_curve_trajectory/enums

pycatia3dx-0.1/docs/api/index_del_drill_rivet_feature.rst

@@ -0,0 +1,13 @@
+pycatia3dx.del_drill_rivet_feature
+==================================
+
+.. toctree::
+   :maxdepth: 1
+   :caption: Contents:
+
+
+   pycatia3dx/del_drill_rivet_feature/dr_manufacturing_fastener
+   pycatia3dx/del_drill_rivet_feature/dr_manufacturing_pattern
+   pycatia3dx/del_drill_rivet_feature/dr_manufacturing_product
+   pycatia3dx/del_drill_rivet_feature/dr_pattern_group
+   pycatia3dx/del_drill_rivet_feature/dr_pattern_group_factory