pola-rs/polars · error

activate feature dtype-datetime

Error message

activate feature dtype-datetime

What it means

Series::into_datetime requires the 'dtype-datetime' cargo feature; when the crate is built without it, the guard panics immediately regardless of the series' dtype. This is a compile-time feature flag error — rebuild with the feature enabled.

Source

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

        #[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"))]
        {
            panic!("activate feature dtype-datetime")
        }

        #[cfg(feature = "dtype-datetime")]
        match self.dtype() {
            DataType::Int64 => self
                .i64()
                .unwrap()
                .clone()
                .into_datetime(timeunit, tz)
                .into_series(),
            DataType::Datetime(_, _) => self
                .datetime()
                .unwrap()
                .physical()
                .clone()
                .into_datetime(timeunit, tz)
                .into_series(),
            dt => panic!("into_datetime not implemented for {dt:?}"),

View on GitHub (pinned to 68506541d2)

Solutions

1. Enable the `dtype-datetime` cargo feature to use Datetime dtype.
2. Store timestamps as Int64 with an explicit unit 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-datetime". 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-datetime"). 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/dfe2575759f8ba8a. Report an issue: GitHub.