conda-rattler-solver 0.2.0__tar.gz

conda_rattler_solver-0.2.0/.authors.yml

@@ -0,0 +1,67 @@
+- name: Daniel Holth
+  email: dholth@anaconda.com
+  alternate_emails:
+  - 208018+dholth@users.noreply.github.com
+  github: dholth
+  num_commits: 2
+  first_commit: 2026-01-23 10:06:36
+- name: Dan Yeaw
+  email: dan@yeaw.me
+  github: danyeaw
+  num_commits: 8
+  first_commit: 2026-01-23 13:23:50
+- name: Sophia Castellarin
+  email: scastellarin@openteams.com
+  github: soapy1
+  num_commits: 12
+  first_commit: 2026-05-13 12:46:15
+- name: Jannis Leidel
+  email: jannis@leidel.info
+  github: jezdez
+  num_commits: 15
+  first_commit: 2025-10-20 04:49:07
+- name: conda-bot
+  email: 18747875+conda-bot@users.noreply.github.com
+  github: conda-bot
+  num_commits: 14
+  first_commit: 2026-06-10 15:19:32
+- name: jaimergp
+  email: jaimergp@users.noreply.github.com
+  github: jaimergp
+  num_commits: 30
+  first_commit: 2023-10-12 14:16:23
+- name: Jakov Smolić
+  email: jsmolic@gentoo.org
+  github: jsmolic
+  num_commits: 1
+  first_commit: 2026-05-29 03:12:39
+- name: dependabot[bot]
+  email: 49699333+dependabot[bot]@users.noreply.github.com
+  github: dependabot[bot]
+  num_commits: 10
+  first_commit: 2026-06-22 22:35:32
+- name: Mahe Iram Khan
+  email: 65779580+ForgottenProgramme@users.noreply.github.com
+  github: ForgottenProgramme
+  num_commits: 2
+  first_commit: 2026-08-13 16:25:05
+- name: Ryan Keith
+  email: rkeith@anaconda.com
+  github: ryanskeith
+  num_commits: 1
+  first_commit: 2026-09-09 14:16:17
+- name: Ken Odegard
+  email: kodegard@anaconda.com
+  github: kenodegard
+  num_commits: 4
+  first_commit: 2026-07-09 16:51:56
+- name: Agriya Khetarpal
+  email: 74401230+agriyakhetarpal@users.noreply.github.com
+  github: agriyakhetarpal
+  num_commits: 2
+  first_commit: 2026-09-21 16:10:16
+- name: Travis Hathaway
+  email: travis.j.hathaway@gmail.com
+  github: travishathaway
+  num_commits: 2
+  first_commit: 2026-09-23 08:26:56

conda_rattler_solver-0.2.0/.devcontainer/apt-deps.txt

@@ -0,0 +1,5 @@
+git
+less
+htop
+nano
+ssh

conda_rattler_solver-0.2.0/.devcontainer/conda-forge/devcontainer.json

@@ -0,0 +1,41 @@
+// For format details, see https://aka.ms/devcontainer.json. For config options, see the
+{
+    "name": "Miniforge (default-channel=conda-forge)",
+    "image": "condaforge/miniforge3:latest",
+
+    // Features to add to the dev container. More info: https://containers.dev/features.
+    // "features": {},
+
+    // Use 'forwardPorts' to make a list of ports inside the container available locally.
+    // "forwardPorts": [],
+    "mounts": [
+        "source=${localWorkspaceFolder}/../conda,target=/workspaces/conda,type=bind,consistency=cached",
+    ],
+    // Use 'postCreateCommand' to run commands after the container is created.
+    "postCreateCommand": "bash /workspaces/conda-rattler-solver/.devcontainer/post_create.sh",
+    // Use 'postStartCommand' to run commands after the container is started.
+    "postStartCommand": "bash /workspaces/conda-rattler-solver/.devcontainer/post_start.sh",
+
+    // Configure tool-specific properties.
+    "customizations": {
+        "vscode": {
+            "settings": {
+                "python.defaultInterpreterPath": "/opt/conda/bin/python",
+                "python.testing.pytestArgs": [
+                    "tests"
+                ],
+                "python.testing.unittestEnabled": false,
+                "python.testing.pytestEnabled": true
+            },
+            "extensions": [
+                "charliermarsh.ruff",
+                "eamodio.gitlens",
+                "ms-toolsai.jupyter"
+            ]
+        }
+    }
+
+    // Adjust to connect as non-root instead. More info: https://aka.ms/dev-containers-non-root.
+    // "remoteUser": "root",
+
+}

conda_rattler_solver-0.2.0/.devcontainer/post_create.sh

@@ -0,0 +1,39 @@
+#!/bin/bash
+
+# This script assumes we are running in a Miniconda container where:
+# - /opt/conda is the Miniconda or Miniforge installation directory
+# - https://github.com/conda/conda is mounted at /workspaces/conda
+# - https://github.com/conda/conda-rattler-solver is mounted at
+#   /workspaces/conda-rattler-solver
+
+set -euo pipefail
+
+HERE=$(dirname $0)
+BASE_CONDA=${BASE_CONDA:-/opt/conda}
+SRC_CONDA=${SRC_CONDA:-/workspaces/conda}
+SRC_CONDA_RATTLER_SOLVER=${SRC_CONDA_RATTLER_SOLVER:-/workspaces/conda-rattler-solver}
+
+if which apt-get > /dev/null; then
+    echo "Installing system dependencies"
+    apt-get update
+    DEBIAN_FRONTEND=noninteractive xargs -a "$HERE/apt-deps.txt" apt-get install -y
+fi
+
+
+if [ ! -f "$SRC_CONDA/pyproject.toml" ]; then
+    echo "https://github.com/conda/conda not found! Please clone or mount to $SRC_CONDA"
+    exit 1
+fi
+
+# Clear history to avoid unneeded conflicts
+echo "Clearing base history..."
+echo '' > "$BASE_CONDA/conda-meta/history"
+
+echo "Installing dev & test dependencies..."
+"$BASE_CONDA/bin/conda" install -n base --yes --quiet \
+    --file="$SRC_CONDA/tests/requirements.txt" \
+    --file="$SRC_CONDA/tests/requirements-ci.txt" \
+    --file="$SRC_CONDA/tests/requirements-Linux.txt" \
+    --file="$SRC_CONDA/tests/requirements-s3.txt" \
+    --file="$SRC_CONDA_RATTLER_SOLVER/dev/requirements.txt" \
+    --file="$SRC_CONDA_RATTLER_SOLVER/tests/requirements.txt"

conda_rattler_solver-0.2.0/.devcontainer/post_start.sh

@@ -0,0 +1,28 @@
+#!/bin/bash
+
+# This script assumes we are running in a Miniconda container where:
+# - /opt/conda is the Miniconda or Miniforge installation directory
+# - https://github.com/conda/conda is mounted at /workspaces/conda
+# - https://github.com/conda/conda-rattler-solver is mounted at
+#   /workspaces/conda-rattler-solver
+# - https://github.com/mamba-org/mamba is (optionally) mounted at
+#   /workspaces/mamba
+
+set -euo pipefail
+
+BASE_CONDA=${BASE_CONDA:-/opt/conda}
+SRC_CONDA=${SRC_CONDA:-/workspaces/conda}
+SRC_CONDA_RATTLER_SOLVER=${SRC_CONDA_RATTLER_SOLVER:-/workspaces/conda-rattler-solver}
+
+cd "$SRC_CONDA"
+echo "Initializing conda in dev mode..."
+"$BASE_CONDA/bin/python" -m conda init --dev bash
+cd -
+
+echo "Installing conda-rattler-solver in dev mode..."
+"$BASE_CONDA/bin/python" -m pip install -e "$SRC_CONDA_RATTLER_SOLVER" --no-deps
+
+set -x
+conda list -p "$BASE_CONDA"
+conda info
+conda config --show-sources

conda_rattler_solver-0.2.0/.github/CODEOWNERS

@@ -0,0 +1,3 @@
+# Syntax for this file at https://help.github.com/articles/about-codeowners/
+
+*       @conda/conda-maintainers

conda_rattler_solver-0.2.0/.github/ISSUE_TEMPLATE/0_bug.yml

@@ -0,0 +1,41 @@
+# edit this in https://github.com/conda/infrastructure
+
+name: Bug Report
+description: Create a bug report.
+labels:
+  - type::bug
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Because processing new bug reports is time-consuming, we would like to ask you to fill out the following form to the best of your ability and as completely as possible.
+
+        > [!NOTE]
+        > Bug reports that are incomplete or missing information may be closed as inactionable.
+
+        Since there are already a lot of open issues, please also take a moment to search existing ones to see if your bug has already been reported. If you find something related, please upvote that issue and provide additional details as necessary.
+
+        💐 Thank you for helping to make `conda/conda-rattler-solver` better. We would be unable to improve `conda/conda-rattler-solver` without our community!
+  - type: checkboxes
+    id: checks
+    attributes:
+      label: Checklist
+      description: Please confirm and check all of the following options.
+      options:
+        - label: I added a descriptive title
+          required: true
+        - label: I searched open reports and couldn't find a duplicate
+          required: true
+  - type: textarea
+    id: what
+    attributes:
+      label: What happened?
+      description: What should have happened instead? Please provide as many details as possible. The more information provided, the more likely we are able to replicate your problem and offer a solution.
+    validations:
+      required: true
+
+  - type: textarea
+    id: context
+    attributes:
+      label: Additional Context
+      description: Include any additional information (or screenshots) that you think would be valuable.

conda_rattler_solver-0.2.0/.github/ISSUE_TEMPLATE/1_feature.yml

@@ -0,0 +1,50 @@
+# edit this in https://github.com/conda/infrastructure
+
+name: Feature Request
+description: Create a feature request.
+labels:
+  - type::feature
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Because processing new feature requests is time-consuming, we would like to ask you to fill out the following form to the best of your ability and as completely as possible.
+
+        > [!NOTE]
+        > Feature requests that are incomplete or missing information may be closed as inactionable.
+
+        Since there are already a lot of open issues, please also take a moment to search existing ones to see if your feature request has already been submitted. If you find something related, please upvote that issue and provide additional details as necessary.
+
+        💐 Thank you for helping to make `conda/conda-rattler-solver` better. We would be unable to improve `conda/conda-rattler-solver` without our community!
+  - type: checkboxes
+    id: checks
+    attributes:
+      label: Checklist
+      description: Please confirm and check all of the following options.
+      options:
+        - label: I added a descriptive title
+          required: true
+        - label: I searched open requests and couldn't find a duplicate
+          required: true
+  - type: textarea
+    id: idea
+    attributes:
+      label: What is the idea?
+      description: Describe what the feature is and the desired state.
+    validations:
+      required: true
+  - type: textarea
+    id: why
+    attributes:
+      label: Why is this needed?
+      description: Who would benefit from this feature? Why would this add value to them? What problem does this solve?
+  - type: textarea
+    id: what
+    attributes:
+      label: What should happen?
+      description: What should be the user experience with the feature? Describe from a user perspective what they would do and see.
+  - type: textarea
+    id: context
+    attributes:
+      label: Additional Context
+      description: Include any additional information that you think would be valuable.

conda_rattler_solver-0.2.0/.github/ISSUE_TEMPLATE/2_documentation.yml

@@ -0,0 +1,38 @@
+# edit this in https://github.com/conda/infrastructure
+
+name: Documentation
+description: Create a documentation related issue.
+labels:
+  - type::documentation
+body:
+  - type: markdown
+    attributes:
+      value: |
+        > [!NOTE]
+        > Documentation requests that are incomplete or missing information may be closed as inactionable.
+
+        Since there are already a lot of open issues, please also take a moment to search existing ones to see if your bug has already been reported. If you find something related, please upvote that issue and provide additional details as necessary.
+
+        💐 Thank you for helping to make conda better. We would be unable to improve conda without our community!
+  - type: checkboxes
+    id: checks
+    attributes:
+      label: Checklist
+      description: Please confirm and check all of the following options.
+      options:
+        - label: I added a descriptive title
+          required: true
+        - label: I searched open reports and couldn't find a duplicate
+          required: true
+  - type: textarea
+    id: what
+    attributes:
+      label: What happened?
+      description: Mention here any typos, broken links, or missing, incomplete, or outdated information, etc. that you have noticed in the conda docs or CLI help.
+    validations:
+      required: true
+  - type: textarea
+    id: context
+    attributes:
+      label: Additional Context
+      description: Include any additional information (or screenshots) that you think would be valuable.

conda_rattler_solver-0.2.0/.github/ISSUE_TEMPLATE/epic.yml

@@ -0,0 +1,108 @@
+# edit this in https://github.com/conda/infrastructure
+
+name: Epic
+description: A collection of related tickets.
+labels:
+  - epic
+body:
+  - type: markdown
+    attributes:
+      value: |
+        This form is intended for grouping and collecting together related tickets to better gauge the scope of a problem/feature.
+
+        If you are attempting to report a bug, propose a new feature, or some other code change please use one of the other forms available.
+
+        > [!NOTE]
+        > Epics that are incomplete or missing information may be closed as inactionable.
+
+        Since there are already a lot of open issues, please also take a moment to search existing ones to see if a similar epic has already been opened. If you find something related, please upvote that issue and provide additional details as necessary.
+
+        💐 Thank you for helping to make `conda/conda-rattler-solver` better. We would be unable to improve `conda/conda-rattler-solver` without our community!
+
+  - type: checkboxes
+    id: checks
+    attributes:
+      label: Checklist
+      description: Please confirm and check all of the following options.
+      options:
+        - label: I added a descriptive title
+          required: true
+        - label: I searched open issues and couldn't find a duplicate
+          required: true
+
+  - type: textarea
+    id: what
+    attributes:
+      label: What?
+      description: >-
+        What feature or problem will be addressed in this epic?
+      placeholder: Please describe here.
+    validations:
+      required: true
+
+  - type: textarea
+    id: why
+    attributes:
+      label: Why?
+      description: >-
+        Why is the reported issue(s) a problem, or why is the proposed feature needed?
+        (Research and spike issues can be linked here.)
+      value: |
+        - [ ] <supporting issue from user, research, or spike>
+      placeholder: Please describe here and/or link to relevant supporting issues.
+    validations:
+      required: true
+
+  - type: textarea
+    id: user_impact
+    attributes:
+      label: User impact
+      description: >-
+        In what specific way(s) will users benefit from this change? (e.g. use cases or performance improvements)
+      placeholder: Please describe here.
+    validations:
+      required: true
+
+  - type: textarea
+    id: goals
+    attributes:
+      label: Goals
+      description: >-
+        What goal(s) should this epic accomplish?
+      value: |
+        - [ ] <goal>
+    validations:
+      required: true
+
+  - type: textarea
+    id: tasks
+    attributes:
+      label: Tasks
+      description: >-
+        What needs to be done to implement this change?
+      value: |
+        - [ ] <task or PR>
+    validations:
+      required: false
+
+  - type: textarea
+    id: blocked_by
+    attributes:
+      label: 'This epic is blocked by:'
+      description: >-
+        Epics and issues that block this epic.
+      value: |
+        - [ ] <dependency epic or issue>
+    validations:
+      required: false
+
+  - type: textarea
+    id: blocks
+    attributes:
+      label: 'This epic blocks:'
+      description: >-
+        Epics and issues that are blocked by this epic.
+      value: |
+        - [ ] <dependency epic or issue>
+    validations:
+      required: false

conda_rattler_solver-0.2.0/.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,37 @@
+<!-- Hello! Thanks for submitting a PR! To help make things go a bit more
+     smoothly, we would appreciate it if you follow this template. -->
+
+### Description
+
+<!-- Good things to put here include:
+       - reasons for the change (please link any relevant issues!),
+       - any noteworthy (or hacky) choices to be aware of,
+       - or what the problem resolved here looked like. -->
+
+### Checklist - did you ...
+
+<!-- If any of the following items aren't relevant to your contribution,
+     please either tick them or use ~strikethrough~ so we know you've gone
+     through the checklist. -->
+
+- [ ] Add a file to the `news` directory ([using the template](https://github.com/conda/conda-rattler-solver/blob/main/news/TEMPLATE)) for the next release's release notes?
+     <!-- All "significant" changes should get an entry:
+            - user-facing changes or enhancements
+            - bug fixes
+            - deprecations
+            - documentation updates
+            - etc -->
+- [ ] Add / update necessary tests?
+- [ ] Add / update outdated documentation?
+
+
+<!-- Just as a reminder, everyone in all conda org spaces (including PRs)
+     must follow the Conda Org Code of Conduct (link below).
+
+     Finally, once again, thanks for your time and effort. If you have any
+     feedback in regards to your experience contributing here, please
+     let us know!
+
+     Helpful links:
+       - Conda Org COC: https://github.com/conda/conda-rattler-solver/blob/main/CODE_OF_CONDUCT.md
+       - Contributing docs: https://github.com/conda/conda-rattler-solver/blob/main/CONTRIBUTING.md -->

conda_rattler_solver-0.2.0/.github/dependabot.yml

@@ -0,0 +1,26 @@
+# edit this in https://github.com/conda/infrastructure
+
+version: 2
+updates:
+  - package-ecosystem: github-actions
+    directory: /.github/workflows
+    schedule:
+      interval: weekly
+    groups:
+      workflows:
+        patterns:
+          - '*'
+    cooldown:
+      default-days: 7
+      exclude:
+        - conda/actions
+  - package-ecosystem: pre-commit
+    directory: /
+    schedule:
+      interval: monthly
+    groups:
+      pre-commit:
+        patterns:
+          - '*'
+    cooldown:
+      default-days: 7

conda_rattler_solver-0.2.0/.github/template-files/config.yml

@@ -0,0 +1,69 @@
+conda/governance:
+  # [required] community files
+  - CODE_OF_CONDUCT.md
+
+conda/infrastructure:
+  # [required] general workflows
+  - .github/workflows/cla.yml
+  - .github/workflows/update.yml
+
+  # [optional] to include repo in https://github.com/orgs/conda/projects/2
+  - .github/workflows/issues.yml
+  - .github/workflows/labels.yml
+  - .github/workflows/project.yml
+
+  # [optional] stale bot workflows
+  # - .github/workflows/stale.yml
+  # - .github/workflows/lock.yml
+
+  # [optional] canary build workflow
+  - src: templates/workflows/build.yml
+    dst: .github/workflows/build.yml
+  # For noarch packages, add:
+    with:
+      noarch: true
+  # For repos whose test workflow is not named "Tests", add:
+  #   with:
+  #     tests_workflow: Test
+
+  # [optional] general processes for the conda org
+  - src: templates/HOW_WE_USE_GITHUB.md
+    dst: HOW_WE_USE_GITHUB.md
+
+  # [optional] standard issue templates
+  - src: templates/issues/bug.yml
+    dst: .github/ISSUE_TEMPLATE/0_bug.yml
+
+  - src: templates/issues/feature.yml
+    dst: .github/ISSUE_TEMPLATE/1_feature.yml
+
+  - src: templates/issues/documentation.yml
+    dst: .github/ISSUE_TEMPLATE/2_documentation.yml
+
+  - src: templates/issues/epic.yml
+    dst: .github/ISSUE_TEMPLATE/epic.yml
+
+  # [optional] standard PR template
+  - src: templates/pull_requests/news_tests_docs.md
+    dst: .github/template-files/templates/pull_request_template_details.md
+  - src: templates/pull_requests/base.md
+    dst: .github/PULL_REQUEST_TEMPLATE.md
+
+  # [optional] dependabot
+  - src: templates/dependabot.yml
+    dst: .github/dependabot.yml
+    with:
+      github_actions: true
+      pre_commit: true
+      docs: false
+
+  # [optional] on-demand release process
+  - src: templates/releases/RELEASE_ON_DEMAND.md
+    dst: RELEASE.md
+    with:
+      placeholder: MAJOR.MINOR.PATCH
+      tag_triggered_release: true
+  - src: templates/releases/rever.xsh
+    dst: rever.xsh
+  - src: templates/releases/TEMPLATE
+    dst: news/TEMPLATE

conda_rattler_solver-0.2.0/.github/template-files/templates/pull_request_template_details.md

@@ -0,0 +1,15 @@
+### Checklist - did you ...
+
+<!-- If any of the following items aren't relevant to your contribution,
+     please either tick them or use ~strikethrough~ so we know you've gone
+     through the checklist. -->
+
+- [ ] Add a file to the `news` directory ([using the template](https://github.com/conda/conda-rattler-solver/blob/main/news/TEMPLATE)) for the next release's release notes?
+     <!-- All "significant" changes should get an entry:
+            - user-facing changes or enhancements
+            - bug fixes
+            - deprecations
+            - documentation updates
+            - etc -->
+- [ ] Add / update necessary tests?
+- [ ] Add / update outdated documentation?