bestform/shorty

shorty is a python library for dealing with url shortening services.

shorty's Issues

handles of bit.ly

i think the handles of bit.ly links are depending on what api key and login is used so the test for bit.ly should fail if the testing person doesn't edit the test file and test the resolved url by himself manually

i'm not really sure if that is an issue but i wanted to write it down before i forget about it ;) - have to check this

Get rid of settings.py

At the moment, you have to set a login and api key for bit.ly in the settings.py file in order to be able to use this service.
This is bad because you don't want to maintain a settings file when using a library.
On the other hand I don't want the user to know beforehand, which type of url he is about to handle and therefore setting credentials before calling the "shorten" method of the shortener he received from shorty. I want the shortener implementations to behave exactly the same for every service.

I haven't come up with a smart solution for this problem and am open for suggestions.

Until now my only suggestion would be to set optional credentials when initializing the shorty class. It's not pretty but in my opinion it's the only way to provide a pleasant and unified usage of the library.

Use setuptools

We really should add a setup.py utilizing the setuptools of python.
This is a long term goal and shouldn't be done until we found a solution for issue #2 (#2) for obvious reasons.