On 06/28/2018 05:59 PM, Felix Yan wrote:
> The main reason behind this (or why I started doing this) was sometimes
> the tests run inside the sources tree made both versions' .pyc files
> into the tree itself, and finally end up in the package. I had this
> problem for several times and end up having the separated build
> directories as template for new packages.
> 
> This seems not the case for most packages now, so I agree that it should
> be avoided.

Hmm, that's quite interesting. From what I've seen, both pytest and
`python setup.py test` (at least today) use the copy of the code from
outside of build/ when running unittests, which I suppose probably makes
sense as it is running right alongside the unittests themselves.

-- 
Eli Schwartz
Bug Wrangler and Trusted User

Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to