Skip to main content

Import JSON/YAML/INI/XML like .py files

Project description


|Build Status| |Supported Python versions| |PyPI version| |Coverage

ezcf stands for **easy configuration**, it allows you to import
JSON/YAML/INI/XML like .py files. It is useful whenever you need to read
from these formats, especially for reading configuration files.

OK, stop talking, show us some code!

On the left is what you'll normally do, on the right is the ezcf way.
**All you need is ``import ezcf`` first, then ``import filename``
without extension.** Nothing else!

.. figure::

For instance, here we want to load file ``config.json``. With a single
line of code ``from config import *``, everything is done and you're



pip install ezcf

If you run into ``error: yaml.h: No such file or directory``, don't
worry, you can still use ezcf without any problem.

Supported File Types

ezcf supports ``JSON``, ``YAML``, ``INI`` and ``XML`` with extension
``json``, ``yaml``, ``yml``, ``ini``, ``xml``.

Sample Usage

Let's start with an easy case:


└── sample1.json

```` and ``sample1.json`` are in the same directory. We want
to read ``sample1.json`` in ````, here's how:

.. code:: python

# sample1.json
"hello": "world"

import ezcf
from sample1 import hello

print(hello) # 'world'

It's that easy.

That's cool, but we usually put config files in a separate folder. Can
ezcf deal with that?


├── conf
│ ├──
│   └── sample2.yaml

Why not?

.. code:: python

Time: 2001-11-23 15:02:31 -5
User: ed
This is a warning.
- file:
line: 23
code: |
x = MoreObject("345\n")
- file:
line: 58
code: |-
foo = bar

import ezcf
from conf.sample2 import Time, User, warning, Stack

Time # datetime.datetime(2001, 11, 23, 20, 2, 31)
User # ed
warning # This is a warning.
Stack # [{'line': 23, 'code': 'x = MoreObject("345\\n")\n', 'file': ''}, {'line': 58, 'code': 'foo = bar', 'file': ''}]

ezcf supports all kinds of valid import statements. These statements are

.. code:: python

from conf.sample2 import Time, User, warning, Stack
from conf.sample2 import *
import conf.sample2 # then use conf.sample2.Time/User/warning/Stack
import conf.sample2 as cs # then use cs.Time/User/warning/Stack

In a word, you can assume they're just regular python files.(Currently
ezcf only supports files with utf-8 encoding)

What about relative import? Yes, ezcf supports relative import, as long
as you use it *correctly*.


1. Be careful importing YAML which contains multiple documents: if there
exists keys with the same name, only one of them will be loaded. So
it's better not to use multiple documents;
2. All values in ``.ini`` files are kept as it is and loaded as a
3. Since XML only allows single root, the whole xml will be loaded as
one dict with root's name as variable name;
4. Use `**valid variable
names** <>`__,
this means key strings in JSON/YAML/INI/XML should be valid Python
variable name. Invalid variable name won't do any harm to your
program nor will it crash, but you can't use them as expected.

Run Tests


python test


- [x] Use dot to seperate folder/subfolder/file
- [x] Unicode support
- [x] JSON support
- [x] YAML support
- [x] INI support
- [x] XML support
- [ ] Auto encoding detect?
- [x] CI
- [x] coverage
- [x] pypi



.. |Build Status| image::
.. |Supported Python versions| image::
.. |PyPI version| image::
.. |Coverage Status| image::

Project details

Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution (13.5 kB view hashes)

Uploaded source

Built Distribution

ezcf-0.2.1-py2.py3-none-any.whl (10.5 kB view hashes)

Uploaded 2 7

Supported by

AWS AWS Cloud computing and Security Sponsor Datadog Datadog Monitoring Fastly Fastly CDN Google Google Download Analytics Microsoft Microsoft PSF Sponsor Pingdom Pingdom Monitoring Sentry Sentry Error logging StatusPage StatusPage Status page