Twitter Client on Terminal by Python

[Orakaro]

On Tuesday, July 15, 2014 5:36:40 AM UTC+9, Terry Reedy wrote:
> On 7/13/2014 11:51 PM, Chris Angelico wrote:
> 
> > On Mon, Jul 14, 2014 at 12:18 PM, Orakaro <nhatminh179 at gmail.com> wrote:
> 
> >> I use README.md for Github and README.rst for PyPi. Is there a way to use only one file for both sites ?
> 
> >
> 
> > Ah. I don't know; check the docs for one or the other and see what they'll do.
> 
> >
> 
> >> I tested my package on Python 2.7 and Python 3.4 But do I have to install all Python 2.6, Python 3.* in my system and test in all environment for sure ?
> 
> 
> 
> You don't *have* do anything for free. However, if your package works on 
> 
> 2.7 and 3.4, it *probably* works as is for 3.2 and 3.3. On Windows at 
> 
> least, installing multiple versions is trivial (5 minutes for each).
> 
> 
> 
> The more important issue, I think, is what system you have tested on. Up 
> 
> to 3.2, including all 2.x, Python had 'wide' and 'narrow' unicode 
> 
> builds. On narrow builds (Windows, some *nix), astral (non-BMP) chars 
> 
> count as 2. Given Twitter's 140 char limitation, this bug (solved in 
> 
> 3.3) could affect a Twitter client by giving the length of a 140 char 
> 
> tweet as more than 140 chars.
> 
> 
> 
> > You can state that it supports 2.7 and 3.4, without testing on any
> 
> > other versions. Those are the two current versions - my example was
> 
> > showing support for more than just the one latest, but that was just
> 
> > an example, nothing more. When Python 3.5 comes out, you'll probably
> 
> > want to test on that (and then say "supports 2.7 and 3.4+"), but at
> 
> > the moment, "2.7 and 3.4" is fine. If people want to use this with,
> 
> > say, 3.3, then they're welcome to try, but they'll know not to presume
> 
> > that it'll work.
> 
> 
> 
> Even if you test on, say, 2.6, it is up to you whether you want to 
> 
> 'support' 2.6 with bugfixes, in case a patch for 2.7 does not work on 2.6.
> 
> 
> 
> -- 
> 
> Terry Jan Reedy

Hi Terry.

Thanks so much for pointing all this out. I didn't know anything about the unicode builds problem. Will try to reproduce this bug even for self-learning purpose.

By the way, I tested this app on Mac OSX and only one Linux distro (CentOS 5). Maybe Window is next.

Regards.