Copier behaves strangely about copier-python HOT 7 CLOSED

Maybe I'll set up a VSCode task in the main template that sets up copier-python-init, instead of the latter bootstrapping the former. I'm probably introducing some strange caching behavior where Copier thinks the template is one or the other.

from copier-python.

Okay I've done this, but it doesn't help. Now I can successfully and reliably reproduce an issue over at blakeNaccarato/copier-python-test where if I run .tools/scripts/init_template.ps1 it fails. Copier says that it has successfully copied the first-time-template files over, but it hasn't really done so. And it also tickles .gitignore despite having no reason to? Will have to look into this another time.

from copier-python.

A workaround is to answer all the same questions from scratch in a totally different folder for copier-python-init, then manually port over those files to the desired project.

Clearly something is going on in the copier update pathway, resulting in a "second-fiddle" template not being able to write files to the project. Perhaps this is related to copier-org/copier#429, where the template thinks it doesn't have a right to make any changes here upon updating.

Also possible that copier-org/copier#288 is tangentially related?

Something is definitely going on. A minimally reproducible example should be developed and posted as an issue upstream.

from copier-python.

Okay now in the commit below, the updated workflow isn't overwritten either, despite Copier output at the terminal saying "overwritten". Very strange...

blakeNaccarato/gradedoc@1b5a779

from copier-python.

Copying from a local copy of the repo actually copies properly. There is some breakage when updating a copier template that references a GitHub remote.

from copier-python.

So the files that are "created" and "updated" actually clearly do show up in the repository, but only momentarily. So I will need to run Copier in debug mode and see at which point the files are scrubbed.

from copier-python.

So, running copier copy gh:blakeNaccarato/copier-python . seems to always properly copy the project, whereas copier -f doesn't always properly copy it! The only downside is that you must press "Enter" repeatedly to finish bumping the template through the copier copy gh:blakeNaccarato/copier-python . approach. It will do for now.

from copier-python.