Ben Mares

Ok, I can put together a repodata patch to make it retroactive on conda-forge. The first step is to add it to our pyproject.toml, and ideally make a release containing...

On the conda-forge side I wrote a repodata patch, and then when I tested it didn't actually do anything... Happily, in terms of Numpy, the conda-forge infrastructure currently automatically pins...

I'm weakly :-1:. I don't see any technical obstacles. But is there any benefit beyond saving users a few keystrokes? This would introduce yet another layer of indirection. It's already...

> Importing from source is fine for dev work but not user work, such as Jupyter notebook workflows. Ya, that's actually a really good argument. I've been doing too much...

Just to brainstorm likely-bad ideas, I wonder if it would make sense to flip the `statsmodels` pattern upside down. Make the top-level `pytensor` namespace the user API. Then in order...

Friendly note that it will be necessary to revert 1235d08b1c75aa1458beb9f978d7ba3dfe3424db on the next rebase in order to unpin `numpy

Thanks a lot for the clear explanation. I feel for you on the quirky legacy codebase. All that callback nonsense is totally out of control. It'd be great to eventually...

Thanks @synapticarbors for the feedback, it's really valuable, especially since I haven't found the time to investigate these details myself! Regarding your question, someone asked something very similar [here](https://discord.com/channels/1082332781146800168/1214169703811907604/1214198318205509674) and...

In general I agree, but for me personally, not all packages I'm using are 2.x compatible. https://github.com/Unidata/siphon/issues/703#issuecomment-1622664691

Note that 2.17.1 is from October. All subsequent versions [explicitly require](https://github.com/pymc-devs/pytensor/blob/0666fd564d2d67384051c5bb6e0c09e713e0329c/pyproject.toml#L15) Python