Skip to content

Conversation

@jfaldanam
Copy link
Contributor

@jfaldanam jfaldanam commented Sep 16, 2025

This branch will not be ready to be merge until all breaking changes we want to implement for v1 are ready, in the meantime you can test it by setting your dependency as follows (Example from https://github.com/Bigdata-com/bigdata-thematic-screener):

[project]
name = "bigdata_thematic_screener"
version = "2.1.0"
description = "Discover corporate exposure to any theme or event, grounded on thousands of sources provided by Bigdata.com"
authors = [{name = "jaldana", email = "jaldana@ravenpack.com"}]
readme = "README.md"
license-files = ["LICENSE"]
requires-python = ">=3.11"

dependencies = [
    "pydantic>=2.10.6",
    "pydantic-settings>=2.2.1",
    "jinja2==3.1.6",
    "structlog>=25.4.0",
    "fastapi>=0.116.1",
    "uvicorn>=0.35.0",
    "bigdata-client==2.19.0",
    # Direct reference to the v1 branch in github while v1.0.0 is being developed
    "bigdata-research-tools @ git+https://github.com/Bigdata-com/bigdata-research-tools@preparation_for_v1",
    "sqlmodel>=0.0.24",
]

[dependency-groups]
dev = [
    "pytest==8.1.1",
    "pytest-cov==5.0.0",
]

[tool.hatch.build.targets.wheel]
packages = ["bigdata_thematic_screener"]

# Note that this metadata is required if you are using hatchling as a build system
[tool.hatch.metadata]
allow-direct-references = true

[build-system]
requires = ["hatchling"]
build-backend = "hatchling.build"

@jfaldanam jfaldanam self-assigned this Sep 16, 2025
@jfaldanam jfaldanam linked an issue Oct 3, 2025 that may be closed by this pull request
@jfaldanam jfaldanam marked this pull request as ready for review November 19, 2025 16:36
@jfaldanam jfaldanam merged commit 37704ae into main Nov 21, 2025
4 checks passed
@jfaldanam jfaldanam deleted the preparation_for_v1 branch November 21, 2025 13:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Inconsistent naming of parameter frequency

4 participants