While trying to roll out this theme I ran into a problem re: collectstatic as I am running Python3+. Pelican uses Fabric<2.0 to generate their fabfiles, here is a link to the closed issue which is not Python3 compatible.
As in the comment thread they have fixed this issue for Pelican 3.8. Until that is released, I didn't see much point in downgrading to Python2 so I quickly rolled a script to collect the static resources and move them over to the output directory, shown below.
It's not perfect, but I thought I would share it here in case any other Python3+ users encounter a similar problem.
I haven't quite worked out a good place to hook it into my build process because I can't use the fabfile so I just run it manually for now.
I have updated the example included to remove the theme static resources directory in the output directory to make cleanup easier. I've also made this snippet into a gist.
Hi Frank,
While trying to roll out this theme I ran into a problem re:
collectstatic
as I am running Python3+. Pelican uses Fabric<2.0 to generate their fabfiles, here is a link to the closed issue which is not Python3 compatible.As in the comment thread they have fixed this issue for Pelican 3.8. Until that is released, I didn't see much point in downgrading to Python2 so I quickly rolled a script to collect the static resources and move them over to the output directory, shown below.
It's not perfect, but I thought I would share it here in case any other Python3+ users encounter a similar problem.
I haven't quite worked out a good place to hook it into my build process because I can't use the fabfile so I just run it manually for now.
I have updated the example included to remove the theme static resources directory in the output directory to make cleanup easier. I've also made this snippet into a gist.