Hi,
Oh? Hmm that's odd, the blender_multimail pyc file is still old, so it
would appear that one wasn't called yet, or it's pyc file would have been
recreated after I edited the py file:
-rwxr-xr-x 1 git git 85296 Aug 20 06:01 blender_multimail.py*
-rw-r--r-- 1 git git 78850 Jun 8 201
Nope, emails still don't seem to be getting sent, but I also didn't see any
warnings about python2 when pushing, so at least we're seeing some progress
now ;)
On Mon, Aug 20, 2018 at 4:07 PM Dan McGrath wrote:
> Hi Joshua,
>
> Ah, that's probably the cause then. I was wondering why git wasn't
>
Hi Joshua,
Ah, that's probably the cause then. I was wondering why git wasn't
relinking properly. Sure enough, the shebang for the mailhook blender uses
had `env python2` instead of `python2.7`. I've updated the mailhook for
now. Try a commit and see how that goes?
The more modern approach I thin
Hi Dan,
Hmm... interesting. Maybe this is why most commit messages from the last
day or so don't seem to have been coming through on the mailing list. The
last ones were from Aug 18th.
Regards,
Joshua
On Mon, Aug 20, 2018 at 3:52 PM Dan McGrath wrote:
> Hi,
>
> Try again? Recently switched fr
Hi,
Try again? Recently switched from py2.7 to py3.6 in there, but apparently
it still thinks git should be linked to 2.7 for some reason. Worst case I
can symlink, but lets see if reinstalling ports helps. Let me know, thanks.
Dan
On Sun, Aug 19, 2018 at 8:08 PM Ray Molenkamp wrote:
> All,
>
All,
Not sure who to poke for this, but since a few days when committing through git
push
git it now spits back a python related warning/error
k:\BlenderGit\blender>git push
Counting objects: 6, done.
Delta compression using up to 8 threads.
Compressing objects: 100% (6/6), done.
Writing object