Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add support for more file types supported by the standard library #20

Open
janbrohl opened this issue Jun 11, 2019 · 5 comments
Open

Add support for more file types supported by the standard library #20

janbrohl opened this issue Jun 11, 2019 · 5 comments

Comments

@janbrohl
Copy link
Collaborator

janbrohl commented Jun 11, 2019

Add support for:

@janbrohl janbrohl changed the title Add INI support Add support for file types supported by the standard library Jun 11, 2019
@dhellmann
Copy link
Member

SQLite databases can be handled somewhat with https://github.com/sphinx-contrib/sqltable although I do like the idea of adding template support there. We may be able to simplify that code to use list tables, too, instead of generating the more complex table structure.

I'm not sure what we would do with templates and ZIP or tar archives. What did you have in mind there, iterating over the content?

@janbrohl
Copy link
Collaborator Author

For ZIP and tar iterating entries and metadata, possibly content as a single string each.

@janbrohl
Copy link
Collaborator Author

Actually the reason for the list is "because we can" without adding additional dependencies. While I am sure there are use cases, I don't have any on my mind.

@janbrohl janbrohl changed the title Add support for file types supported by the standard library Add support for more file types supported by the standard library Jun 13, 2019
@janbrohl
Copy link
Collaborator Author

#28 adds basic support for Unix "databases" but I am not quite sure if this is worth including.

@janbrohl
Copy link
Collaborator Author

If we add support for adding custom loaders more directly than via the import-module directive, this would be obsolete.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants