Two-arch builds
Closed this issue · 4 comments
We can't make this a true noarch package because of the pywin32 dependency. (conda-forge can do so because they have the magical pywin32-on-windows package that Anaconda does not support. That may change, but not now.)
However, what Anaconda does support are virtual packages like __unix and __win. This would allow us to build two noarch packages in parallel that cover all Python versions.
Excellent, thanks. I'll work on bringing that over here. Note that I'm thinking of this more from the perspective of testing; I want to be able to test the package in as close to its built form as possible The fact that we have noarch packages on conda-forge but we're building them arch over here is a discrepancy I don't like.
The noarch is relatively recent (conda-forge/nb_conda_kernels-feedstock#50) but the post init scripts were not called on windows, so I fixed that with the virtual packages (as suggested by ocepaf)
That raises another issue... I believe the scripts themselves can potentially be retired, at least on new-ish versions of notebook and/or jupyter_server.