microlens-submit 0.16.0__tar.gz → 0.16.1__tar.gz

{microlens_submit-0.16.0/microlens_submit.egg-info → microlens_submit-0.16.1}/PKG-INFO

@@ -1,6 +1,6 @@
-Metadata-Version: 2.1
+Metadata-Version: 2.4
 Name: microlens-submit
-Version: 0.16.0
+Version: 0.16.1
 Summary: A tool for managing and submitting microlensing solutions
 Home-page: https://github.com/AmberLee2427/microlens-submit
 Author: Amber Malpas
@@ -41,6 +41,10 @@ Requires-Dist: isort; extra == "dev"
 Requires-Dist: sphinx; extra == "dev"
 Requires-Dist: sphinx_rtd_theme; extra == "dev"
 Requires-Dist: importlib_resources; extra == "dev"
+Dynamic: author
+Dynamic: home-page
+Dynamic: license-file
+Dynamic: requires-python
 
 <p align="center">
   <a href="https://github.com/AmberLee2427/microlens-submit">
@@ -52,11 +56,7 @@ Requires-Dist: importlib_resources; extra == "dev"
 
 *A stateful submission toolkit for the RGES-PIT Microlensing Data Challenge.*
 
-[![PyPI - v0.16.0](https://img.shields.io/pypi/v/microlens-submit.svg)](https://pypi.org/project/microlens-submit/)
-[![PyPI - Python Version](https://img.shields.io/pypi/pyversions/microlens-submit.svg)](https://pypi.org/project/microlens-submit/)
-[![PyPI - License](https://img.shields.io/pypi/l/microlens-submit.svg)](https://pypi.org/project/microlens-submit/)
-[![CI](https://github.com/AmberLee2427/microlens-submit/actions/workflows/ci.yml/badge.svg)](https://github.com/AmberLee2427/microlens-submit/actions/workflows/ci.yml)
-[![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT)
+[![PyPI - v0.16.0](https://img.shields.io/pypi/v/microlens-submit.svg)](https://pypi.org/project/microlens-submit/)[![Read the Docs](https://readthedocs.org/projects/microlens-submit/badge/?version=latest)](https://microlens-submit.readthedocs.io/en/latest/?badge=latest)[![CI](https://github.com/AmberLee2427/microlens-submit/actions/workflows/ci.yml/badge.svg)](https://github.com/AmberLee2427/microlens-submit/actions/workflows/ci.yml)[![PyPI - Python Version](https://img.shields.io/pypi/pyversions/microlens-submit.svg)](https://pypi.org/project/microlens-submit/)[![License](https://img.shields.io/badge/license-MIT-blue.svg)](https://opensource.org/licenses/MIT)
 
 <br>
 
@@ -93,8 +93,21 @@ The CLI is the recommended way to interact with your submission project.
 
 You can pass ``--no-color`` to any command if your terminal does not support ANSI colors.
 
-1. Initialize your project: `microlens-submit init --team-name "Planet Pounders" --tier "advanced"`
+1. Initialize your project:
+
+   ```bash
+   microlens-submit init --team-name "Planet Pounders" --tier "advanced"
+   # if a project directory was provided to `init`, you should now `cd` into that project
+   ```
+
+   To pass validation, you need to have provided a `repo_url` and `hardware_info` to the project and have a git project initialized in your sumission-project directory.
+
+   ```bash
+   microlens-submit set-repo-url <url> ./
+   microlens-submit set-hardware-info --cpu-details "intel i7 xxx" --ram-gb 32 ./
+   ```
 2. Add a new solution to an event:
+
    ```bash
    microlens-submit add-solution ogle-2025-blg-0042 1S2L \
        --param t0=555.5 \
@@ -102,18 +115,28 @@ You can pass ``--no-color`` to any command if your terminal does not support ANS
        --param tE=25.0 \
        --notes "This is a great fit!"
    ```
+
    Model types must be one of `1S1L`, `1S2L`, `2S1L`, `2S2L`, `1S3L`, `2S3L`, or `other`.
    This will create a new solution and print its unique `solution_id`.
+
    You can run the same command with `--dry-run` first to verify the
    parsed input without saving anything.
+
 3. **Bulk import multiple solutions from a CSV file:**
+
    ```bash
    microlens-submit import-solutions tests/data/test_import.csv --dry-run
    ```
-   See the file `tests/data/test_import.csv` for a comprehensive example covering all features and edge cases. You can use this file as a template for your own imports.
+
+   See the file `tests/data/test_import.csv` for a comprehensive example covering all features and edge cases.
+   You can use this file as a template for your own imports.
+
 4. Deactivate a solution that didn't work out: `microlens-submit deactivate <solution_id>`
+
 5. List all solutions for an event: `microlens-submit list-solutions ogle-2025-blg-0042`
+
 6. Validate solutions and check for issues: `microlens-submit validate-solution <solution_id>`
+
 7. Export your final submission: `microlens-submit export final_submission.zip`
 
 **Note:** When you add a solution, it's automatically validated and any warnings are displayed. Use `--dry-run` to check validation without saving.

{microlens_submit-0.16.0 → microlens_submit-0.16.1}/README.md

@@ -8,11 +8,7 @@
 
 *A stateful submission toolkit for the RGES-PIT Microlensing Data Challenge.*
 
-[![PyPI - v0.16.0](https://img.shields.io/pypi/v/microlens-submit.svg)](https://pypi.org/project/microlens-submit/)
-[![PyPI - Python Version](https://img.shields.io/pypi/pyversions/microlens-submit.svg)](https://pypi.org/project/microlens-submit/)
-[![PyPI - License](https://img.shields.io/pypi/l/microlens-submit.svg)](https://pypi.org/project/microlens-submit/)
-[![CI](https://github.com/AmberLee2427/microlens-submit/actions/workflows/ci.yml/badge.svg)](https://github.com/AmberLee2427/microlens-submit/actions/workflows/ci.yml)
-[![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT)
+[![PyPI - v0.16.0](https://img.shields.io/pypi/v/microlens-submit.svg)](https://pypi.org/project/microlens-submit/)[![Read the Docs](https://readthedocs.org/projects/microlens-submit/badge/?version=latest)](https://microlens-submit.readthedocs.io/en/latest/?badge=latest)[![CI](https://github.com/AmberLee2427/microlens-submit/actions/workflows/ci.yml/badge.svg)](https://github.com/AmberLee2427/microlens-submit/actions/workflows/ci.yml)[![PyPI - Python Version](https://img.shields.io/pypi/pyversions/microlens-submit.svg)](https://pypi.org/project/microlens-submit/)[![License](https://img.shields.io/badge/license-MIT-blue.svg)](https://opensource.org/licenses/MIT)
 
 <br>
 
@@ -49,8 +45,21 @@ The CLI is the recommended way to interact with your submission project.
 
 You can pass ``--no-color`` to any command if your terminal does not support ANSI colors.
 
-1. Initialize your project: `microlens-submit init --team-name "Planet Pounders" --tier "advanced"`
+1. Initialize your project:
+
+   ```bash
+   microlens-submit init --team-name "Planet Pounders" --tier "advanced"
+   # if a project directory was provided to `init`, you should now `cd` into that project
+   ```
+
+   To pass validation, you need to have provided a `repo_url` and `hardware_info` to the project and have a git project initialized in your sumission-project directory.
+
+   ```bash
+   microlens-submit set-repo-url <url> ./
+   microlens-submit set-hardware-info --cpu-details "intel i7 xxx" --ram-gb 32 ./
+   ```
 2. Add a new solution to an event:
+
    ```bash
    microlens-submit add-solution ogle-2025-blg-0042 1S2L \
        --param t0=555.5 \
@@ -58,18 +67,28 @@ You can pass ``--no-color`` to any command if your terminal does not support ANS
        --param tE=25.0 \
        --notes "This is a great fit!"
    ```
+
    Model types must be one of `1S1L`, `1S2L`, `2S1L`, `2S2L`, `1S3L`, `2S3L`, or `other`.
    This will create a new solution and print its unique `solution_id`.
+
    You can run the same command with `--dry-run` first to verify the
    parsed input without saving anything.
+
 3. **Bulk import multiple solutions from a CSV file:**
+
    ```bash
    microlens-submit import-solutions tests/data/test_import.csv --dry-run
    ```
-   See the file `tests/data/test_import.csv` for a comprehensive example covering all features and edge cases. You can use this file as a template for your own imports.
+
+   See the file `tests/data/test_import.csv` for a comprehensive example covering all features and edge cases.
+   You can use this file as a template for your own imports.
+
 4. Deactivate a solution that didn't work out: `microlens-submit deactivate <solution_id>`
+
 5. List all solutions for an event: `microlens-submit list-solutions ogle-2025-blg-0042`
+
 6. Validate solutions and check for issues: `microlens-submit validate-solution <solution_id>`
+
 7. Export your final submission: `microlens-submit export final_submission.zip`
 
 **Note:** When you add a solution, it's automatically validated and any warnings are displayed. Use `--dry-run` to check validation without saving.

{microlens_submit-0.16.0 → microlens_submit-0.16.1}/microlens_submit/__init__.py

@@ -5,7 +5,7 @@ validate, and export a challenge submission using either the Python API or
 the command line interface.
 """
 
-__version__ = "0.16.0"
+__version__ = "0.16.1"
 
 from .models import Event, Solution, Submission
 from .utils import load

{microlens_submit-0.16.0 → microlens_submit-0.16.1}/microlens_submit/dossier/dashboard.py

@@ -11,8 +11,12 @@ import webbrowser
 from datetime import datetime
 from pathlib import Path
 
-import importlib_resources
+try:  # Prefer stdlib importlib.resources when available (Python >= 3.9)
+    import importlib.resources as importlib_resources
+except ImportError:  # pragma: no cover - fallback for Python < 3.9
+    import importlib_resources
 
+from .. import __version__
 from ..models.submission import Submission
 from .utils import extract_github_repo_name, format_hardware_info
 
@@ -485,7 +489,7 @@ style="width: {progress_percentage}%"></div>
 
             <!-- Footer -->
             <div class="text-sm text-gray-500 text-center pt-8 pb-6">
-                Generated by microlens-submit v0.16.0 on
+                Generated by microlens-submit v{__version__} on
                 {datetime.now().strftime('%Y-%m-%d %H:%M:%S UTC')}
             </div>
 

{microlens_submit-0.16.0 → microlens_submit-0.16.1}/microlens_submit/dossier/event_page.py

@@ -9,6 +9,7 @@ evaluator-only visualizations.
 from datetime import datetime
 from pathlib import Path
 
+from .. import __version__
 from ..models import Event, Submission
 from .solution_page import generate_solution_page
 
@@ -357,7 +358,7 @@ Event {event.event_id}. Points colored by Relative Probability (Evaluator View).
 
             <!-- Footer -->
             <div class='text-sm text-gray-500 text-center pt-8 border-t border-gray-200 mt-10'>
-                Generated by microlens-submit v0.13.0 on {datetime.now().strftime('%Y-%m-%d %H:%M:%S UTC')}
+                Generated by microlens-submit v{__version__} on {datetime.now().strftime('%Y-%m-%d %H:%M:%S UTC')}
             </div>
 
             <!-- Regex Finish -->

{microlens_submit-0.16.0 → microlens_submit-0.16.1}/microlens_submit/dossier/solution_page.py

@@ -11,6 +11,7 @@ from pathlib import Path
 
 import markdown
 
+from .. import __version__
 from ..models.event import Event
 from ..models.solution import Solution
 from ..models.submission import Submission
@@ -521,7 +522,7 @@ def _generate_solution_page_content(solution: Solution, event: Event, submission
 
             <!-- Footer -->
             <div class='text-sm text-gray-500 text-center pt-8 border-t border-gray-200 mt-10'>
-                Generated by microlens-submit v0.16.0 on {datetime.now().strftime('%Y-%m-%d %H:%M:%S UTC')}
+                Generated by microlens-submit v{__version__} on {datetime.now().strftime('%Y-%m-%d %H:%M:%S UTC')}
             </div>
 
             <!-- Regex Finish -->

{microlens_submit-0.16.0 → microlens_submit-0.16.1/microlens_submit.egg-info}/PKG-INFO

@@ -1,6 +1,6 @@
-Metadata-Version: 2.1
+Metadata-Version: 2.4
 Name: microlens-submit
-Version: 0.16.0
+Version: 0.16.1
 Summary: A tool for managing and submitting microlensing solutions
 Home-page: https://github.com/AmberLee2427/microlens-submit
 Author: Amber Malpas
@@ -41,6 +41,10 @@ Requires-Dist: isort; extra == "dev"
 Requires-Dist: sphinx; extra == "dev"
 Requires-Dist: sphinx_rtd_theme; extra == "dev"
 Requires-Dist: importlib_resources; extra == "dev"
+Dynamic: author
+Dynamic: home-page
+Dynamic: license-file
+Dynamic: requires-python
 
 <p align="center">
   <a href="https://github.com/AmberLee2427/microlens-submit">
@@ -52,11 +56,7 @@ Requires-Dist: importlib_resources; extra == "dev"
 
 *A stateful submission toolkit for the RGES-PIT Microlensing Data Challenge.*
 
-[![PyPI - v0.16.0](https://img.shields.io/pypi/v/microlens-submit.svg)](https://pypi.org/project/microlens-submit/)
-[![PyPI - Python Version](https://img.shields.io/pypi/pyversions/microlens-submit.svg)](https://pypi.org/project/microlens-submit/)
-[![PyPI - License](https://img.shields.io/pypi/l/microlens-submit.svg)](https://pypi.org/project/microlens-submit/)
-[![CI](https://github.com/AmberLee2427/microlens-submit/actions/workflows/ci.yml/badge.svg)](https://github.com/AmberLee2427/microlens-submit/actions/workflows/ci.yml)
-[![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT)
+[![PyPI - v0.16.0](https://img.shields.io/pypi/v/microlens-submit.svg)](https://pypi.org/project/microlens-submit/)[![Read the Docs](https://readthedocs.org/projects/microlens-submit/badge/?version=latest)](https://microlens-submit.readthedocs.io/en/latest/?badge=latest)[![CI](https://github.com/AmberLee2427/microlens-submit/actions/workflows/ci.yml/badge.svg)](https://github.com/AmberLee2427/microlens-submit/actions/workflows/ci.yml)[![PyPI - Python Version](https://img.shields.io/pypi/pyversions/microlens-submit.svg)](https://pypi.org/project/microlens-submit/)[![License](https://img.shields.io/badge/license-MIT-blue.svg)](https://opensource.org/licenses/MIT)
 
 <br>
 
@@ -93,8 +93,21 @@ The CLI is the recommended way to interact with your submission project.
 
 You can pass ``--no-color`` to any command if your terminal does not support ANSI colors.
 
-1. Initialize your project: `microlens-submit init --team-name "Planet Pounders" --tier "advanced"`
+1. Initialize your project:
+
+   ```bash
+   microlens-submit init --team-name "Planet Pounders" --tier "advanced"
+   # if a project directory was provided to `init`, you should now `cd` into that project
+   ```
+
+   To pass validation, you need to have provided a `repo_url` and `hardware_info` to the project and have a git project initialized in your sumission-project directory.
+
+   ```bash
+   microlens-submit set-repo-url <url> ./
+   microlens-submit set-hardware-info --cpu-details "intel i7 xxx" --ram-gb 32 ./
+   ```
 2. Add a new solution to an event:
+
    ```bash
    microlens-submit add-solution ogle-2025-blg-0042 1S2L \
        --param t0=555.5 \
@@ -102,18 +115,28 @@ You can pass ``--no-color`` to any command if your terminal does not support ANS
        --param tE=25.0 \
        --notes "This is a great fit!"
    ```
+
    Model types must be one of `1S1L`, `1S2L`, `2S1L`, `2S2L`, `1S3L`, `2S3L`, or `other`.
    This will create a new solution and print its unique `solution_id`.
+
    You can run the same command with `--dry-run` first to verify the
    parsed input without saving anything.
+
 3. **Bulk import multiple solutions from a CSV file:**
+
    ```bash
    microlens-submit import-solutions tests/data/test_import.csv --dry-run
    ```
-   See the file `tests/data/test_import.csv` for a comprehensive example covering all features and edge cases. You can use this file as a template for your own imports.
+
+   See the file `tests/data/test_import.csv` for a comprehensive example covering all features and edge cases.
+   You can use this file as a template for your own imports.
+
 4. Deactivate a solution that didn't work out: `microlens-submit deactivate <solution_id>`
+
 5. List all solutions for an event: `microlens-submit list-solutions ogle-2025-blg-0042`
+
 6. Validate solutions and check for issues: `microlens-submit validate-solution <solution_id>`
+
 7. Export your final submission: `microlens-submit export final_submission.zip`
 
 **Note:** When you add a solution, it's automatically validated and any warnings are displayed. Use `--dry-run` to check validation without saving.

{microlens_submit-0.16.0 → microlens_submit-0.16.1}/pyproject.toml

@@ -6,7 +6,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "microlens-submit"
-version = "0.16.0"
+version = "0.16.1"
 authors = [
   { name="Amber Malpas", email="malpas.1@osu.edu" },
   {name = "Roman Science Platform Team", email = "roman-science-platform@stsci.edu"}
@@ -36,7 +36,7 @@ dependencies = [
     "rich>=13.0.0",
     "pyyaml>=6.0",
     "markdown>=3.4.0",
-    "importlib_resources>=1.0.0; python_version<\"3.9\"",
+    'importlib_resources>=1.0.0; python_version < "3.9"',
 ]
 
 [project.urls]
@@ -65,7 +65,7 @@ dev = [
 # Setuptools package configuration
 [tool.setuptools.packages.find]
 where = ["."]
-include = ["microlens_submit*"]
+include = ["microlens_submit", "microlens_submit.*"]
 exclude = ["tests*", "docs*"]
 
 [tool.setuptools.package-data]

{microlens_submit-0.16.0 → microlens_submit-0.16.1}/setup.py

@@ -8,8 +8,8 @@ from setuptools import find_packages, setup
 if __name__ == "__main__":
     setup(
         name="microlens-submit",
-        version="0.16.0",
-        packages=find_packages(),
+        version="0.16.1",
+        packages=find_packages(include=("microlens_submit", "microlens_submit.*")),
         include_package_data=True,
         package_data={
             "microlens_submit": ["assets/*"],

{microlens_submit-0.16.0 → microlens_submit-0.16.1}/tests/test_cli.py

@@ -61,20 +61,22 @@ Note:
     The test suite ensures CLI functionality matches API behavior.
 """
 
-# Install package in editable mode to ensure assets are available
+# Install package in editable mode to ensure assets are available when running tests
+import os
 import subprocess
 import sys
 
-try:
-    subprocess.run(
-        [sys.executable, "-m", "pip", "install", "-e", "."],
-        capture_output=True,
-        check=True,
-    )
-except subprocess.CalledProcessError:
-    # If we're not in the right directory or package isn't set up, continue anyway
-    # The asset check fixture will catch missing assets
-    pass
+if os.environ.get("MICROLENS_SKIP_EDITABLE_INSTALL") != "1":
+    try:
+        subprocess.run(
+            [sys.executable, "-m", "pip", "install", "-e", "."],
+            capture_output=True,
+            check=True,
+        )
+    except subprocess.CalledProcessError:
+        # If we're not in the right directory or package isn't set up, continue anyway
+        # The asset check fixture will catch missing assets
+        pass
 
 import json
 import zipfile