pola-rs/polars · error

activate feature dtype-date

Error message

activate feature dtype-date

What it means

Series::into_date is compiled only when the 'dtype-date' cargo feature is on; with the feature disabled the function body unconditionally panics with this build-configuration message. Fix by rebuilding polars-core/polars with feature dtype-date enabled.

Source

Thrown at crates/polars-core/src/series/mod.rs:946

    #[cfg(feature = "dtype-time")]
    pub fn into_time(self) -> Series {
        match self.dtype() {
            DataType::Int64 => self.i64().unwrap().clone().into_time().into_series(),
            DataType::Time => self
                .time()
                .unwrap()
                .physical()
                .clone()
                .into_time()
                .into_series(),
            dt => panic!("date not implemented for {dt:?}"),
        }
    }

    pub fn into_date(self) -> Series {
        #[cfg(not(feature = "dtype-date"))]
        {
            panic!("activate feature dtype-date")
        }
        #[cfg(feature = "dtype-date")]
        match self.dtype() {
            DataType::Int32 => self.i32().unwrap().clone().into_date().into_series(),
            DataType::Date => self
                .date()
                .unwrap()
                .physical()
                .clone()
                .into_date()
                .into_series(),
            dt => panic!("date not implemented for {dt:?}"),
        }
    }

    #[allow(unused_variables)]
    pub fn into_datetime(self, timeunit: TimeUnit, tz: Option<TimeZone>) -> Series {
        #[cfg(not(feature = "dtype-datetime"))]

View on GitHub (pinned to 68506541d2)

Solutions

1. Enable the `dtype-date` cargo feature to use Date dtype.
2. Store the values as Datetime or Int32 days if the feature cannot be enabled.

When it happens

Trigger: This panic/expect fires when execution reaches an unguarded state described by: "activate feature dtype-date". Typical triggers: unsupported dtype or feature-gated code path reached at runtime, invalid user input or environment variable value, calling API methods in the wrong order or on mismatched types, or data (lengths, offsets, ranges) violating the function's preconditions.

Common situations: Encountered when input data or configuration does not meet the preconditions of the throwing code path ("activate feature dtype-date"). Common cases: missing Cargo feature flags, mismatched dtypes/lengths between arrays or series, out-of-range temporal values, malformed environment variables, or operations on unsupported/complex nested types.

AI-assisted analysis of pola-rs/polars@68506541d2 (2026-08-19). Data as JSON: /api/errors/4335c26994433273. Report an issue: GitHub.