PyTg

Version 0.4.1

A Python package that communicates with the Telegram messenger CLI.
Note: I am currently heavily working on an interface supporting the cli via socket (as before), the CLI via it build in python (aka. tgl) and brand new, the Telegram bot api as well. Receiving messages is already possible with all three (even simultaneously)

Works with Python 2.7 and 3

I really recommend to use Python 3, because of it's build in unicode support. Python 2 uses ascii only bytestrings, causing much, much trouble when dealing with characters like öäüß or emojis. (Trust me, I've been there)
~ luckydonald

URL Changes or "How to update?"##

Well, lot has happened recently. A huge change for the original users: merges, new functions, renames and and finally the changed url. Here is how to update your local git clone. If you have not used pytg before, just skip to the Install part.

# navigate into the clone
cd pytg	 # not pytg/pytg!
# change to the new url
git remote set-url origin https://github.com/luckydonald/pytg.git
# download the changes
git pull
# don't forget to install the newest official cli: https://github.com/vysheng/tg

If that failes at some point, just Install it from scratch.

Install##

Dependencies

Install the Telegram CLI (from @vysheng), follow the official Instructions

Pytg

(Beta versions are in the development branch)

a) Get the latest pytg code from github.

git clone https://github.com/luckydonald/pytg.git && cd pytg

b) To update already existing code, navigate to the root inside the pytg folder, then git pull
Install
```
sudo python setup.py install 
```
- The dependency "DictObject" should be installed automatically by this. If not, it is available on PyPI
  sudo pip install DictObject

Done.

Usage

Start telegram

Create a Telegram Instance. This will manage the CLI process, and registers the Sender and Receiver for you.

from pytg import Telegram
tg = Telegram(
	telegram="/path/to/tg/bin/telegram-cli",
	pubkey_file="/path/to/tg/tg-server.pub")
receiver = tg.receiver
sender = tg.sender

If you don't want pytg to start the cli for you, start it yourself with --json -P 4458 (port 4458). You can then use the Receiver and/or the Sender like this:

from pytg.sender import Sender
from pytg.receiver import Receiver
receiver = Receiver(host="localhost", port=4458)
sender = Sender(host="localhost", port=4458)

Send a message

sender.send_msg("username", "Hello World!")
# Easy huh?

Receiving messages

You need a function as main loop.

@coroutine # from pytg.utils import coroutine
def main_loop():
	while not QUIT:
		msg = (yield) # it waits until it got a message, stored now in msg.
		print("Message: ", msg.text)
		# do more stuff here!
	#
#

Last step is to register that function:

# start the Receiver, so we can get messages!
receiver.start()

# let "main_loop" get new message events.
# You can supply arguments here, like main_loop(foo, bar).
receiver.message(main_loop())
# now it will call the main_loop function and yield the new messages.

That's the basics. Have a look into the examples folder. For starters, I recommend:

dump.py * is usefull to see, how the messages look like.
ping.py * is usefull to see how to interact with pytg, send messages etc.

New in Version 0.4.1

It is named "pytg" again. Hooray!

New in Version 0.4.0

No need for telejson any more, you can now run with the offical telegram-cli! Connecting to the cli for sending will now surrender after given retrys, and not loop forever. Also added a CHANGELOG file.

New in Version 0.3.1

Updates for telejson beta compatibility. This version never got offically released before the telejson fork got replaced by vysheng's native json implementation.

New in Version 0.3.0

Pytg2 (now since V0.4.1 called Pytg again) got overhauled to version 0.3.0, which will restructure heavily, BUT will decrease the CPU usage to around nothing. While the old versions need to parse the cli output directly, resuling in easy ways to exploit it, now it is safe, using json internal. Without the parsing we don't have to poll for new output ("Hey, got anything yet? And yet? And yet? ...") but just block until we got new output. The retrieval of new messaged is multitheaded, so you won't lose any messages if you do heavy and/or long operations between messages.

Also a nice new feature is an automatic download of files. (more about this, as soon as I get time to edit this...)

Look at the examples

See some example scripts to start with. They are in the examples folder

dump.py * is usefull to see, how the messages look like.
ping.py * is usefull to see how to interact with pytg, send messages etc.
dialog_list.py * shows you how to interact with the CLI and function returning stuff.

Contribute

You can help

with testing
by reporting issues
by commiting patches

Thanks!

akvladimir/pytg