M. Eric Irrgang

The updates that were necessary for the tests indicate that this change will surprise some users. Some sort of release note is warranted, and perhaps some sort of update to...

> The updates that were necessary for the tests indicate that this change will surprise some users. Some sort of release note is warranted, and perhaps some sort of update...

> Thanks this is awesome. Those are long docs, if we know a place to put them, we probably should... For the release note, it would be nice to make...

> Yes, sorry, I missed where this test was, it should be elsewhere. I had just thought it looked reasonably thorough. It might also be split up, but I don't...

> `a.dtype.newbyteorder('native')` creates a new dtype instance, but the new dtype is equal to (i.e. `==`) `a.dtype`. So the dtypes of `a` and `b` are equal, but `asarray()` still created...

I suggest decoupling the change to this cookiecutter repo from the change to the generated project.

I am going to make another pass to make sure I got all of the updates. *(update: I i think we're good now)* Also, note (@Lnaden ) that we want...

The directories ignored for the MolSSI repo don't need to be coupled to those automatically ignored for generated projects. I'm not sure if the current conversation is considering them as...

> I agree mostly with this notion. Versioneer has been such a great tool for forcing semantic versioning that finding replacements that are _not_ a dependency in of themselves has...

I'll separate the PEP 517 and PEP 621 changes into separate branches for clarity. I'll also separate the versioneer->versioningit migration, to keep things simpler and clearer.