fix(python): Allow pl.col(pl.Enum) for selecting all Enum columns

[collinprince]

Update extract to create an empty pl.Enum so that column expressions can be extracted for the pl.Enum datatype e.g. pl.col(pl.Enum).

Also update the Enum constructor to allow/default to None for the categories param. This mirrors the logic that is used in extract for pl.Enum and operates as a convenient short-hand for the current supported logic of passing in an empty series.

Fixes #13269

[ritchie46]

This should be None, not empty.

[c-peters]

True, I would like to rework the type a bit to have a state of 'Non-Initalized Enum'. But preferably outside this PR, so this is Ok for now

[c-peters]

Enum does not accept None yet, I think this would be better in a separate PR

[c-peters]

polars/crates/polars-core/src/datatypes/dtype.rs

Line 76 in f93e450

(Categorical(_, _), Categorical(_, _)) => true,

The problem of equality check is here. We need to distinguish Enum from Categorical. Right now, if you do df.select(pl.col(Enum)) or df.select(pl.col(Categorical) you get both categorical and enum columns. We need to alter the equality check on the datatype.

[collinprince]

@c-peters @ritchie46
Updated the code to handle equality of enum vs categorical though it feels a bit awkward due to needing to support that all other revmap comparisons besides those containing enums need to be treated as true

                #[cfg(feature = "dtype-categorical")]
                (Categorical(rev_l, _), Categorical(rev_r, _)) => {
                    let is_l_enum = rev_l.as_ref().map_or(false, |x| x.is_enum());
                    let is_r_enum = rev_r.as_ref().map_or(false, |x| x.is_enum());
                    is_l_enum == is_r_enum
                },

[c-peters]

Yes, this is not ideal. I'm working on making Enums an acual datatype as to avoid this cumbersome rev_map check

[c-peters]

@collinprince , Enum is a now an actual data type, could you resolve the merge conflicts?

[collinprince]

should be good now @c-peters

[c-peters]

This test should still be valid right? We do not allow creating a series with an empty Enum type, the None is just a placeholder for all Enums

[c-peters]

If I am not mistaken, this already runs on main without any of the other changes.

[c-peters]

Because we should be able to convert the python class object to the rust datatype without hte need for None in the constructor

[c-peters]

This is supeseded by #14628. We do not allow empty Enum, because the categories should be present when defining the datatype. You can select the columns with the class itself