That sounds like a fair reason as to why an exception was used, even simply from a Pythonic perspective, irrespective of webservice involvement. Is the webservice allowing the error message through? We do have a mechanism to allow that.
The only other thought I have is perhaps exporting two APIs, ``checkUpload`` with the current behavior and ``canUpload`` with the requested behavior. That said, someone annoyed by the ``checkUpload`` behavior could simply wrap it with a helper function for what I proposed for the ``canUpload`` behavior, and move on. If I had to choose one of those two behaviors from the webservice itself, I'd choose the current one.
I'll ask Leonard and/or Benji to weigh in, in case they have any other ideas.
That sounds like a fair reason as to why an exception was used, even simply from a Pythonic perspective, irrespective of webservice involvement. Is the webservice allowing the error message through? We do have a mechanism to allow that.
The only other thought I have is perhaps exporting two APIs, ``checkUpload`` with the current behavior and ``canUpload`` with the requested behavior. That said, someone annoyed by the ``checkUpload`` behavior could simply wrap it with a helper function for what I proposed for the ``canUpload`` behavior, and move on. If I had to choose one of those two behaviors from the webservice itself, I'd choose the current one.
I'll ask Leonard and/or Benji to weigh in, in case they have any other ideas.