You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since the 0.26.0 release (specifically PR #2829), the documentation is all now out of date. The old paths (which are still in use throughout the documentation) are like:
#include"xtensor/xarray.hpp"
But due to PR #2829 in v0.26.0, these would need to be changed to, e.g.,:
#include"xtensor/containers/xarray.hpp"
@JohanMabille - it might be easier to just revert #2829 than to refactor all the docs etc. Users I'm sure would also greatly appreciate having PR #2829 reverted so as to not have to refactor all apps using xtensor as well. Developers using xtensor might also appreciate reverting back to the old header locations so as to not have to deal with problems due to downstream users having 0.25.0 installed vs 0.26.0.
The text was updated successfully, but these errors were encountered:
An additional problem caused by these changes is that it breaks xtensor-python. It is now impossible to update to the latest xtensor version if you are using xtensor-python in the same project. Not only will the docs for xtensor need updating, but xtensor-python will need to be updated.
Actually, I think all of the xtensor based language libraries and utilities will need to be updated such as xtensor-r, xtensor-zarr, xtensor-blas and more.
Since the 0.26.0 release (specifically PR #2829), the documentation is all now out of date. The old paths (which are still in use throughout the documentation) are like:
But due to PR #2829 in v0.26.0, these would need to be changed to, e.g.,:
@JohanMabille - it might be easier to just revert #2829 than to refactor all the docs etc. Users I'm sure would also greatly appreciate having PR #2829 reverted so as to not have to refactor all apps using xtensor as well. Developers using xtensor might also appreciate reverting back to the old header locations so as to not have to deal with problems due to downstream users having 0.25.0 installed vs 0.26.0.
The text was updated successfully, but these errors were encountered: