From: Muhammad Rizki <[email protected]>
To: Ammar Faizi <[email protected]>
Cc: Muhammad Rizki <[email protected]>,
GNU/Weeb Mailing List <[email protected]>
Subject: [PATCH v1 09/11] Move prepare for patch and clean up patch functions
Date: Mon, 18 Jul 2022 18:20:05 +0700 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
I want these function is separate into the utils or utility file, I'm
the type of person who likes to separate the utility function into the
utility file.
Signed-off-by: Muhammad Rizki <[email protected]>
---
daemon/scraper/utils.py | 35 +++++++++++++++++++++++++++++++++++
1 file changed, 35 insertions(+)
diff --git a/daemon/scraper/utils.py b/daemon/scraper/utils.py
index 10fe956..5335fe2 100644
--- a/daemon/scraper/utils.py
+++ b/daemon/scraper/utils.py
@@ -6,10 +6,12 @@
from email.message import Message
from typing import Dict
+from slugify import slugify
import hashlib
import uuid
import os
import re
+import shutil
def get_email_msg_id(mail):
@@ -190,6 +192,39 @@ def create_template(thread: Message, to=None, cc=None):
return ret, files, is_patch
+def prepare_send_patch(mail, text, url):
+ tmp = gen_temp(url)
+ fnm = str(mail.get("subject"))
+ sch = re.search(PATCH_PATTERN, fnm, re.IGNORECASE)
+
+ nr_patch = sch.group(1)
+ if not nr_patch:
+ nr_patch = 1
+ else:
+ nr_patch = int(nr_patch)
+
+ num = "%04d" % nr_patch
+ fnm = slugify(sch.group(3)).replace("_", "-")
+ file = f"{tmp}/{num}-{fnm}.patch"
+ cap = text.split("\n\n")[0]
+
+ with open(file, "wb") as f:
+ f.write(bytes(text, encoding="utf8"))
+
+ caption = (
+ "#patch #ml\n" +
+ cap.rstrip()
+ .replace("<", "<")
+ .replace(">",">")
+ .replace("�"," ")
+ )
+ return tmp, file, caption, url
+
+
+def clean_up_after_send_patch(tmp):
+ shutil.rmtree(tmp)
+
+
EMAIL_MSG_ID_PATTERN = r"<([^\<\>]+)>"
def extract_email_msg_id(msg_id):
ret = re.search(EMAIL_MSG_ID_PATTERN, msg_id)
--
Muhammad Rizki
next prev parent reply other threads:[~2022-07-18 11:20 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-18 11:19 [PATCH v1 00/11] Plan to redesign code Muhammad Rizki
2022-07-18 11:19 ` [PATCH v1 01/11] Fix __send_patch_msg function parameter Muhammad Rizki
2022-07-18 12:45 ` Ammar Faizi
2022-07-18 11:19 ` [PATCH v1 02/11] Fix import problem Muhammad Rizki
2022-07-18 11:19 ` [PATCH v1 03/11] Add default temporary directory Muhammad Rizki
2022-07-18 11:31 ` Ammar Faizi
2022-07-18 11:20 ` [PATCH v1 04/11] Move the Telegram bot session into the storage directory Muhammad Rizki
2022-07-18 11:20 ` [PATCH v1 05/11] daemon: Fix raw lore URL on the inline keyboard button Muhammad Rizki
2022-07-18 11:20 ` [PATCH v1 06/11] Add traceback to get the error detail Muhammad Rizki
2022-07-18 11:27 ` Ammar Faizi
2022-07-18 12:24 ` Kiizuha
2022-07-18 11:20 ` [PATCH v1 07/11] Re-design send email message to Telegram Muhammad Rizki
2022-07-18 12:49 ` Ammar Faizi
2022-07-18 11:20 ` [PATCH v1 08/11] Move ____send_patch_msg Muhammad Rizki
2022-07-18 11:20 ` Muhammad Rizki [this message]
2022-07-18 11:20 ` [PATCH v1 10/11] Create fix_utf8_chars function Muhammad Rizki
2022-07-18 11:20 ` [PATCH v1 11/11] Recode some codes Muhammad Rizki
2022-07-18 11:33 ` Ammar Faizi
2022-07-18 11:28 ` [PATCH v1 00/11] Plan to redesign code Ammar Faizi
2022-07-18 11:34 ` Ammar Faizi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox