getdaft
getdaft is now daft
What it is and what it does
getdaft is a deprecated package that has been renamed to daft. The package itself contains no active functionality—it exists only to inform users that they should install daft instead. The fact sheet indicates the package is inactive and has not been maintained for over a year.
If you encounter getdaft in a dependency list or documentation, you should replace it with daft. Installing getdaft will not provide the dataframe functionality or any other features; it is a shell pointing users to the correct package name.
Use it for:
- Migrating legacy code that references getdaft to use the renamed daft package instead
- Resolving dependency conflicts when getdaft appears in old requirements files
- Understanding that getdaft is no longer maintained and daft is the active successor
Worth the install?
AI-flagged interpretation of the facts on this page — verify before relying
This package is a deprecated redirect to the renamed `daft` package and should not be installed directly.
No. Do not install getdaft. This package is inactive and deprecated. Install daft instead, which is the active renamed successor. Using getdaft will not provide any functionality and leaves you on an unmaintained package.
Install
getdaft on PyPI
pip
pip install getdaftuv
uv add getdaftpoetry
poetry add getdaftInstalling getdaft
Before you install
The package is marked as Inactive (Development Status 7) and has not been updated in 378 days. It exists only as a redirect to its renamed successor, daft. Installing this package will not provide active maintenance or support.
License in practice
License information is not available for this package, making it impossible to assess licensing obligations or compatibility with your project.
Quickstart
# Do not install getdaft. Instead:
# pip install daft
# Then use daft directly in your code.
This package is deprecated and should not be used; install daft instead.
Verify before relying
- Whether installing getdaft automatically installs or redirects to daft, or if manual migration is required
- Whether getdaft has any breaking changes or deprecation warnings when imported
Package facts
| License | not declared (unclear) |
| Python support | not specified |
| Install friction | low — pure-Python wheel |
| Runtime dependencies | 1 — daft |
| Maintenance | aging — 378 days since the last release |
| First released | |
| Downloads | 190,650/month — #9,904 on PyPI (30-day window, as of 2026-08-14) |
| Known vulnerabilities | none known (OSV.dev, checked 2026-08-14) |
Evidence: getdaft-0.5.0-py3-none-any.whl
Tags
Similar packages
This package is a deprecated alias that…
unclear · top 15,000 on PyPI
lia-weblia-web is a deprecated shim package that…
permissive · top 15,000 on PyPI
daftDaft is a distributed dataframe engine for…
unclear · top 5,000 on PyPI
neptune-fetcherQueries and fetches experiment metadata, runs,…
permissive · top 5,000 on PyPI
google-cloudA deprecated umbrella package that once…
permissive · top 5,000 on PyPI
pinecone-clientThis package is deprecated and should not be…
permissive · top 5,000 on PyPI
imblearnThis package is a deprecated stub that…
unclear · top 5,000 on PyPI
pandas-profilingThis package is deprecated; it redirects users…
permissive · top 15,000 on PyPI
fastapi-slimThis package is a deprecated migration shim…
permissive · top 15,000 on PyPI
apify-sharedApify Shared Python is a deprecated package…
permissive · top 5,000 on PyPI