Pyfilesystem2 implementation for Imap
Project description
# fs.imapfs
Pyfilesystem2 implementation for Imap
Intro
=====
This is the first release of the library. The implemantation is at its early stage. The module is not jet ready to be installed: setup module is missing and no opener implemented. Apart from that, the module is fully working.
The library has been inspired from the implementation of the FTSFS and use internally the imapclient library (see Reference).
It's working and tested with some IMAP server.
IMAP server use a sort of file system structure and implementing the library has been done for now some assumption that fall out of the box of the standard when you think about a file system, specially on file creation and file name.
IMAP server indeed, when uploading a new data (an e-mail), assign to this new massage a new UID. This UID is then used as the file name.
This means that when you upload new content using the fs API, you specify the file name, but this will be considered, as example see:
```python
imap_fs.tree()
`-- INBOX
|-- Archivie
|-- Draft
|-- Posta Indesiderata
|-- Spedite
|-- TEST
|-- Trash
|-- 2.eml
`-- 5.eml
imap_fs.setbytes(path='INBOX/TEST/2.eml', contents=b'Test')
imap_fs.tree()
`-- INBOX
|-- Archivie
|-- Draft
|-- Posta Indesiderata
|-- Spedite
|-- TEST
| `-- 1.eml
|-- Trash
|-- 2.eml
`-- 5.eml
```
The new file has received UID == 1 because was the first one into that folder.
References
----------
* [pyfilesystem2](https://github.com/PyFilesystem/pyfilesystem2)
* [imapclient](https://github.com/mjs/imapclient)
Pyfilesystem2 implementation for Imap
Intro
=====
This is the first release of the library. The implemantation is at its early stage. The module is not jet ready to be installed: setup module is missing and no opener implemented. Apart from that, the module is fully working.
The library has been inspired from the implementation of the FTSFS and use internally the imapclient library (see Reference).
It's working and tested with some IMAP server.
IMAP server use a sort of file system structure and implementing the library has been done for now some assumption that fall out of the box of the standard when you think about a file system, specially on file creation and file name.
IMAP server indeed, when uploading a new data (an e-mail), assign to this new massage a new UID. This UID is then used as the file name.
This means that when you upload new content using the fs API, you specify the file name, but this will be considered, as example see:
```python
imap_fs.tree()
`-- INBOX
|-- Archivie
|-- Draft
|-- Posta Indesiderata
|-- Spedite
|-- TEST
|-- Trash
|-- 2.eml
`-- 5.eml
imap_fs.setbytes(path='INBOX/TEST/2.eml', contents=b'Test')
imap_fs.tree()
`-- INBOX
|-- Archivie
|-- Draft
|-- Posta Indesiderata
|-- Spedite
|-- TEST
| `-- 1.eml
|-- Trash
|-- 2.eml
`-- 5.eml
```
The new file has received UID == 1 because was the first one into that folder.
References
----------
* [pyfilesystem2](https://github.com/PyFilesystem/pyfilesystem2)
* [imapclient](https://github.com/mjs/imapclient)
Project details
Release history Release notifications | RSS feed
Download files
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
Source Distribution
fs.imapfs-0.1.2.tar.gz
(8.3 kB
view hashes)
Built Distribution
Close
Hashes for fs.imapfs-0.1.2-py2.py3-none-any.whl
Algorithm | Hash digest | |
---|---|---|
SHA256 | 1b15a03104299da26e2dc3a672aa32952535fc1c6e99ba27df05163eef771834 |
|
MD5 | cdc238fa94641ec7f88eb1e2f5239a87 |
|
BLAKE2b-256 | bdb4f7616c1b58bb50fce3d536479f3dac17184eac9f953cb3b9fa8b092deff2 |