معرفی شرکت ها


emaillib-1.0.0


Card image cap
تبلیغات ما

مشتریان به طور فزاینده ای آنلاین هستند. تبلیغات می تواند به آنها کمک کند تا کسب و کار شما را پیدا کنند.

مشاهده بیشتر
Card image cap
تبلیغات ما

مشتریان به طور فزاینده ای آنلاین هستند. تبلیغات می تواند به آنها کمک کند تا کسب و کار شما را پیدا کنند.

مشاهده بیشتر
Card image cap
تبلیغات ما

مشتریان به طور فزاینده ای آنلاین هستند. تبلیغات می تواند به آنها کمک کند تا کسب و کار شما را پیدا کنند.

مشاهده بیشتر
Card image cap
تبلیغات ما

مشتریان به طور فزاینده ای آنلاین هستند. تبلیغات می تواند به آنها کمک کند تا کسب و کار شما را پیدا کنند.

مشاهده بیشتر
Card image cap
تبلیغات ما

مشتریان به طور فزاینده ای آنلاین هستند. تبلیغات می تواند به آنها کمک کند تا کسب و کار شما را پیدا کنند.

مشاهده بیشتر

توضیحات

A simple library to ease the sending of emails with utf8 and attachments.
ویژگی مقدار
سیستم عامل -
نام فایل emaillib-1.0.0
نام emaillib
نسخه کتابخانه 1.0.0
نگهدارنده []
ایمیل نگهدارنده []
نویسنده Costas Tyfoxylos
ایمیل نویسنده costas.tyf@gmail.com
آدرس صفحه اصلی https://github.com/costastf/emaillib
آدرس اینترنتی https://pypi.org/project/emaillib/
مجوز MIT
======== emaillib ======== A simple library to ease the sending of emails with utf8 and attachments. * Documentation: https://emaillib.readthedocs.org/en/latest Development Workflow ==================== The workflow supports the following steps * lint * test * build * document * upload * graph These actions are supported out of the box by the corresponding scripts under _CI/scripts directory with sane defaults based on best practices. Sourcing setup_aliases.ps1 for windows powershell or setup_aliases.sh in bash on Mac or Linux will provide with handy aliases for the shell of all those commands prepended with an underscore. The bootstrap script creates a .venv directory inside the project directory hosting the virtual environment. It uses pipenv for that. It is called by all other scripts before they do anything. So one could simple start by calling _lint and that would set up everything before it tried to actually lint the project Once the code is ready to be delivered the _tag script should be called accepting one of three arguments, patch, minor, major following the semantic versioning scheme. So for the initial delivery one would call $ _tag --minor which would bump the version of the project to 0.1.0 tag it in git and do a push and also ask for the change and automagically update HISTORY.rst with the version and the change provided. So the full workflow after git is initialized is: * repeat as necessary (of course it could be test - code - lint :) ) * code * lint * test * commit and push * develop more through the code-lint-test cycle * tag (with the appropriate argument) * build * upload (if you want to host your package in pypi) * document (of course this could be run at any point) Important Information ===================== This template is based on pipenv. In order to be compatible with requirements.txt so the actual created package can be used by any part of the existing python ecosystem some hacks were needed. So when building a package out of this **do not** simple call $ python setup.py sdist bdist_egg **as this will produce an unusable artifact with files missing.** Instead use the provided build and upload scripts that create all the necessary files in the artifact. Project Features ================ * Handles subject and message body as utf-8 by default * Handles html and plain text * Handles attachments either as list or comma delimited value arguments * Supports CC and BCC * Simply validates the provided recipient addresses History ------- 0.0.1 (16-09-2017) --------------------- * First code creation 1.0.0 (07-07-2021) ------------------ * Dropped support for python2.7, updated the template and setup a pipeline for release.


نحوه نصب


نصب پکیج whl emaillib-1.0.0:

    pip install emaillib-1.0.0.whl


نصب پکیج tar.gz emaillib-1.0.0:

    pip install emaillib-1.0.0.tar.gz