A Python Static Website Generator

The "simple_copy" site configuration variable uses globbing to flag pages for pass-through filtering. This commit adds "simple_copy_re" that uses regex matching to flag files.

When I execute hyde on the console, I get the following error.

Traceback (most recent call last):
File "/usr/local/bin/hyde", line 8, in <module>
    load_entry_point('hyde==0.6.0', 'console_scripts', 'hyde')()
File "/System/Library/Frameworks/Python.framework/Versions/2.6/Extras/lib/python/pkg_resources.py", line 271, in load_entry_point
    return get_distribution(dist).load_entry_point(group, name)
File "/System/Library/Frameworks/Python.framework/Versions/2.6/Extras/lib/python/pkg_resources.py", line 2174, in load_entry_point
    return ep.load()
File "/System/Library/Frameworks/Python.framework/Versions/2.6/Extras/lib/python/pkg_resources.py", line 1907, in load
    entry = __import__(self.module_name, globals(),globals(), ['__name__'])
File "/usr/local/bin/main.py", line 5, in <module>
    pkg_resources.run_script('hyde==0.6.0', 'main.py')
File "/System/Library/Frameworks/Python.framework/Versions/2.6/Extras/lib/python/pkg_resources.py", line 442, in run_script
    self.require(requires)[0].run_script(script_name, ns)
File "/System/Library/Frameworks/Python.framework/Versions/2.6/Extras/lib/python/pkg_resources.py", line 1160, in run_script
    execfile(script_filename, namespace, namespace)
File "/Library/Python/2.6/site-packages/hyde-0.6.0-py2.6.egg/EGG-INFO/scripts/main.py", line 6, in <module>
    from hyde.engine import Engine
File "/usr/local/bin/hyde.py", line 5, in <module>
File "/System/Library/Frameworks/Python.framework/Versions/2.6/Extras/lib/python/pkg_resources.py", line 442, in run_script
    self.require(requires)[0].run_script(script_name, ns)
File "/System/Library/Frameworks/Python.framework/Versions/2.6/Extras/lib/python/pkg_resources.py", line 620, in require
    needed = self.resolve(parse_requirements(requirements))
File "/System/Library/Frameworks/Python.framework/Versions/2.6/Extras/lib/python/pkg_resources.py", line 522, in resolve
    raise VersionConflict(dist,req) # XXX put more info here
pkg_resources.VersionConflict: (hyde 0.6.0 (/Library/Python/2.6/site-packages/hyde-0.6.0-py2.6.egg), Requirement.parse('hyde==0.5.3'))

All tests* currently pass under Python 2.7 and Python 3.3 - 3.5. This does not mean that Python 3 support is stable, however. As a plan forward, we should encourage interested users to run Hyde with Python 3, report bugs, and submit patches. This change references the Python 3 Support issue on GitHub (#270). Once this becomes a bit more tested and stable, that issue should be closed, and Hyde should announce official, stable support for Python 3 (i.e. new changes must also support 3, issues with running hyde under 3 should be considered bugs rather than feature requests, etc.).

Changes:

• Add hyde/_compat.py for 2-to-3 compatibility helpers.
• Replace uses of 2-specific code with their hyde._compat versions.
• Tests remain largely unchanged (for good reason). The exceptions here are to print function calls, and str type usage, and compatibility imports.
• Replace explicit calls to foo.next() with next(foo). This keeps code portable between Python 2's next and Python 3's __next__ methods without the need for any compatibility functions and is the recommended API for interacting with these methods.
• Replace deprecated (and, in Python 3, removed) except Exception, e: statements with their updated except Exception as e: versions.
• Replace print statements with print function calls (because of how parentheses work in Python, this is transparently cross-version-compatible).
• Add Python 3.3, 3.4, and 3.5 to tox.ini, .travis.yml, and classifiers in setup.py.
• Add {posargs} to tox.ini command invocations to improve usage during development.
• Add Python 3 note in changelog.

* asciidoc does not support Python 3, and fixing that far beyond the scope of this task, so the test that deals with it is conditionally skipped when run using versions of Python 3.

This is what one of my content files has in it:

### First stuff
I'm in love with [hyde](https://github.com/hyde/).

This is all inside of:

{% filter markdown|typogrify -%}
{% mark post -%}
<article>
    {% block post -%}{%- endblock %}
</article>
{%- endmark %}
{%- endfilter %}

The typogrify filter works but I cannot get the markdown filter to work at all. This is hyde 0.8.5a15 on Mac OS X 10.6.8 (Snow Leopard).

When using 'git' as the value for resource.meta.created or resource.meta.modified, the Git plugin will fetch those from the git repository. But if the file was not known by git, it used to no alter the attributes, leaving them as the 'git' string.

This was causing issues because many consumers of those attributes (for instance, the xmldatetime template filter from jinja2) expect to find a datetime instance and will raise an exception if they find a string.

This patch works around this issue by falling back on the file's own ctime and mtime in case the file wasn't added to the git repository yet (which can happen for brand new entries).

added support for encoded urls to hyde server. Now it can handle urls encoded like this: "some%20url" or "%D0%9F%D1%80%D0%BE%D0%B3%D1%80%D0%B0%D0%BC%D0%BC%D0%B8%D1%80%D0%BE%D0%B2%D0%B0%D0%BD%D0%B8%D0%B5"

I have a blog post with the following text:

 {% raw %}
 {% extends "admin_tp/base.html" %}
 {% endraw %}

and it kills my template. But hyde gen doesn't throw any errors. Essentially it's processing the extends as if it weren't within raw. Other things like block and endblock are properly ignored.

On Unix-based system, the $PATH variable plays a central role at locating executables. Most of the time, you will be able to find your well-known executable easily by looking up in all the directories listed in $PATH, and you can even add an extra directory by altering the PATH variable in your shell beforehand.

For instance, in my own .bashrc file, the folllowing line is sufficient to be able to call anything I installed in my home directory: export PATH=~/.local/bin:$PATH

This is why I added support for that handy environment variable and for a default application command in hyde. This makes it possible to not do any assumptions in the site.yaml file, making it easier to edit or generate the site on several computers with a different setup (e.g. if lessc is not installed with the same path on both machines, like what happened to me when I wanted to generate your hyde-docs site).

I created a new project using hyde create and then tried to serve it using hyde serve and the server just hangs forever for http://127.0.0.1:8080 and just returns 404 for http://localhost:8080 When I accessed http://127.0.0.1:8080 I got the following traceback Exception happened during processing of request from ('127.0.0.1', 60578) Traceback (most recent call last): File "C:\Python27\Lib\SocketServer.py", line 284, in _handle_request_noblock self.process_request(request, client_address) File "C:\Python27\Lib\SocketServer.py", line 310, in process_request self.finish_request(request, client_address) File "C:\Python27\Lib\SocketServer.py", line 323, in finish_request self.RequestHandlerClass(request, client_address, self) File "C:\Python27\Lib\SocketServer.py", line 639, in init self.handle() File "C:\Python27\Lib\BaseHTTPServer.py", line 343, in handle self.handle_one_request() File "C:\Python27\Lib\BaseHTTPServer.py", line 313, in handle_one_request self.raw_requestline = self.rfile.readline(65537) File "C:\Python27\Lib\socket.py", line 476, in readline data = self._sock.recv(self._rbufsize) error: [Errno 10054] An existing connection was forcibly closed by the remote host What could be the problem?

This add a 'filter' option to the auto_extend plugin.

This option will wrap the text with {% filter XXX %} / {% endfilter XXX %}, the same way as the default_block works.

Please merge or comment.

Since all the blog-posts are written in markdown in hyde, I have come across a weird problem. I need to wrap the MARKDOWNed content within a div and provide a class and id to it.

For eg:

Why hyde
--------------

### Pros

It saves a lot of considerable amount of time rather writing from the scratch.

I want to wrap the above code as:

Why hyde
--------------

<div id="scroll" class="spyScroll">

### Pros

It saves a lot of considerable amount of time rather writing from the scratch.

</div>

But when I try the above method, Markdown inside the div doesn't work. I need this since I have to mark that content being active and show the corresponding link being highlighted in Table of Contents on the left side of blog-post.

Any help regarding the same would be highly appreciated. @lakshmivyas

Thanks!

The image plugin thumbnailer generates an error when converting JPEG to thumbnails, since it uses image mode RGBA, and as of about version 3 of Pillow this has been deprecated and then removed.

This patch tests if the image is a JPEG by checking the im.format and does no conversion if its a JPEG.

Thumbnailing JPEGs failed with a

20:44:31 hyde Error occured when calling imagethumbnails

This line:

https://github.com/hyde/hyde/blob/7f415402cc3e007a746eb2b5bc102281fdb415bd/hyde/ext/plugins/images.py#L295

hyde converts the PIL image to RGBA, but that fails with Pillow after v3.7 because it was deprecated and then removed:

https://github.com/python-pillow/Pillow/commit/193c7561392fd12c3bd93bc232d9041c89bec4f6

with the advice to convert to RGB before saving. I think the solution for hyde is to not convert to RGBA on line 295 for JPEG files.

short diff attached tests and only converts non-JPEG to RGBA.

diff.txt

(Let me know if you'd rather I did a fork and PR, but its about two lines!)

Hi I notice python-dateutil is used in hyde/ext/plugins/vcs.py. But it seems python-dateutil is not installed when "pip install hyde". So I am wondering if python-dateutil should be listed as dependency.

There is a small typo in hyde/plugin.py.

Should read utilities rather than utiltities.

Semi-automated pull request generated by https://github.com/timgates42/meticulous/blob/master/docs/NOTE.md

Currently we are relying on travis and tox to give us coverage reports. It would make more sense to use deepsource since it also has free CVE, bug risk, performance issues and anti-pattern recognition etc. built into it.