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
A usage of this would be someone trying to build a package from a read-only device (e.g. from a RO mounted volume in a docker session). Currently it will fail with an OSError if the option [tool.hatch.build.directory] is not set to some RW location, and it will work just fine (according build plugins do the right thing as well I suppose) when setting this option in the pyproject.toml file to e.g. /tmp/dist.
It would be nice to specify it from the cli (option + environment variable) so it does not requires the pyproject file to be modified to work.
The text was updated successfully, but these errors were encountered:
But I don't see the 'option from the CLI takes precedence' part in this...
Oh! the [LOCATION] parameter of the hatch build command is the output directory! Gheez I also missed that! I thought it was the path to the source directory (à lapip install)! Thanks! (but oh so yeah for #1245).
A usage of this would be someone trying to build a package from a read-only device (e.g. from a RO mounted volume in a docker session). Currently it will fail with an OSError if the option [tool.hatch.build.directory] is not set to some RW location, and it will work just fine (according build plugins do the right thing as well I suppose) when setting this option in the pyproject.toml file to e.g.
/tmp/dist
.It would be nice to specify it from the cli (option + environment variable) so it does not requires the pyproject file to be modified to work.
The text was updated successfully, but these errors were encountered: