Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.python > #74402 > unrolled thread

Twitter Client on Terminal by Python

Back to article view | Back to comp.lang.python

Contents

  Twitter Client on Terminal by Python Orakaro <nhatminh179@gmail.com> - 2014-07-13 11:00 -0700
    Re: Twitter Client on Terminal by Python Chris Angelico <rosuav@gmail.com> - 2014-07-14 04:20 +1000
      Re: Twitter Client on Terminal by Python Orakaro <nhatminh179@gmail.com> - 2014-07-13 19:18 -0700
        Re: Twitter Client on Terminal by Python Chris Angelico <rosuav@gmail.com> - 2014-07-14 13:51 +1000
          Re: Twitter Client on Terminal by Python Orakaro <nhatminh179@gmail.com> - 2014-07-13 21:24 -0700
        Re: Twitter Client on Terminal by Python Terry Reedy <tjreedy@udel.edu> - 2014-07-14 16:36 -0400
          Re: Twitter Client on Terminal by Python Orakaro <nhatminh179@gmail.com> - 2014-07-15 19:59 -0700
    Re: Twitter Client on Terminal by Python Omar Abou Mrad <omar.aboumrad@gmail.com> - 2014-07-15 09:27 +0300
      Re: Twitter Client on Terminal by Python Orakaro <nhatminh179@gmail.com> - 2014-07-15 20:30 -0700

#74402 — Twitter Client on Terminal by Python

Hello!

I'm @dtvd88 on Twitter and very new here.
I read from python.org that anything Python-related can be discussed, and not sure if I can share my OSS package here to get feedback or not ?

I just wrote a Twitter Client on Terminal by Python, it has very beautiful display and even can display image on terminal. Check it out and maybe you guys will love it :)

Homepage: http://www.rainbowstream.org/
Github: https://github.com/DTVD/rainbowstream

Thanks for any feedback and sorry if this kind of topics is not tolerated here.

[toc] | [next] | [standalone]

#74403

On Mon, Jul 14, 2014 at 4:00 AM, Orakaro <nhatminh179@gmail.com> wrote:
> Thanks for any feedback and sorry if this kind of topics is not tolerated here.

No no, announcements of this sort are perfectly welcome here!

I notice you have both README.md and README.rst - is there a reason for that?

What Python versions does rainbowstream support? Your README hints
that both 2.x and 3.x are supported, but I can't see a specific set of
versions (eg "2.6+, 3.3+").

ChrisA

[toc] | [prev] | [next] | [standalone]

#74411

On Monday, July 14, 2014 3:20:43 AM UTC+9, Chris Angelico wrote:
> On Mon, Jul 14, 2014 at 4:00 AM, Orakaro <nhatminh179@gmail.com> wrote:
> 
> > Thanks for any feedback and sorry if this kind of topics is not tolerated here.
> 
> 
> 
> No no, announcements of this sort are perfectly welcome here!
> 
> 
> 
> I notice you have both README.md and README.rst - is there a reason for that?
> 
> 
> 
> What Python versions does rainbowstream support? Your README hints
> 
> that both 2.x and 3.x are supported, but I can't see a specific set of
> 
> versions (eg "2.6+, 3.3+").
> 
> 
> 
> ChrisA

Hi Angelico 

I use README.md for Github and README.rst for PyPi. Is there a way to use only one file for both sites ?

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 ?

Thanks very much. 

[toc] | [prev] | [next] | [standalone]

#74413

On Mon, Jul 14, 2014 at 12:18 PM, Orakaro <nhatminh179@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 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.

ChrisA

[toc] | [prev] | [next] | [standalone]

#74414

On Monday, July 14, 2014 12:51:29 PM UTC+9, Chris Angelico wrote:
> On Mon, Jul 14, 2014 at 12:18 PM, Orakaro <nhatminh179@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 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.
> 
> 
> 
> ChrisA

 Angelico, Thank you very much!

[toc] | [prev] | [next] | [standalone]

#74435

On 7/13/2014 11:51 PM, Chris Angelico wrote:
> On Mon, Jul 14, 2014 at 12:18 PM, Orakaro <nhatminh179@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

[toc] | [prev] | [next] | [standalone]

#74524

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@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.

[toc] | [prev] | [next] | [standalone]

#74470

[Multipart message — attachments visible in raw view] — view raw

Dear Orakaro,

Cool app you have there. Please consider the following comments as feedback
in the most positive sense possible:

- I didn't care for the figlet, it's noise beyond anything else, if you
drop it, you would drop the pyfiglet dependency as well
- What's with the SQLAlchemy dependency? I checked your table definitions
and if I'm not mistaken all you're using is Theme, Message, Tweet. My first
question on that front is why are message and tweet stored locally? Are you
doing local caching to speed things up? What about theme?

Good job and take care!

Regards,

Omar


On Sun, Jul 13, 2014 at 9:00 PM, Orakaro <nhatminh179@gmail.com> wrote:

> Hello!
>
> I'm @dtvd88 on Twitter and very new here.
> I read from python.org that anything Python-related can be discussed, and
> not sure if I can share my OSS package here to get feedback or not ?
>
> I just wrote a Twitter Client on Terminal by Python, it has very beautiful
> display and even can display image on terminal. Check it out and maybe you
> guys will love it :)
>
> Homepage: http://www.rainbowstream.org/
> Github: https://github.com/DTVD/rainbowstream
>
> Thanks for any feedback and sorry if this kind of topics is not tolerated
> here.
> --
> https://mail.python.org/mailman/listinfo/python-list
>

[toc] | [prev] | [next] | [standalone]

#74526

On Tuesday, July 15, 2014 3:27:15 PM UTC+9, Omar Abou Mrad wrote:
> Dear Orakaro,
> 
> 
> Cool app you have there. Please consider the following comments as feedback in the most positive sense possible:
> 
> 
> - I didn't care for the figlet, it's noise beyond anything else, if you drop it, you would drop the pyfiglet dependency as well
> 
> - What's with the SQLAlchemy dependency? I checked your table definitions and if I'm not mistaken all you're using is Theme, Message, Tweet. My first question on that front is why are message and tweet stored locally? Are you doing local caching to speed things up? What about theme?
> 
> 
> 
> Good job and take care!
> 
> 
> Regards,
> 
> 
> Omar
> 
> 
> 
> On Sun, Jul 13, 2014 at 9:00 PM, Orakaro <nhatm...@gmail.com> wrote:
> 
> Hello!
> 
> 
> 
> I'm @dtvd88 on Twitter and very new here.
> 
> I read from python.org that anything Python-related can be discussed, and not sure if I can share my OSS package here to get feedback or not ?
> 
> 
> 
> I just wrote a Twitter Client on Terminal by Python, it has very beautiful display and even can display image on terminal. Check it out and maybe you guys will love it :)
> 
> 
> 
> Homepage: http://www.rainbowstream.org/
> 
> Github: https://github.com/DTVD/rainbowstream
> 
> 
> 
> Thanks for any feedback and sorry if this kind of topics is not tolerated here.
> 
> --
> 
> https://mail.python.org/mailman/listinfo/python-list

Hi Omar.
Thanks about the feedback. 

- The ascii art character... seems interesting to some people and not to others. Maybe I should add a config option for ignoring it.

- I used 2 python process, ones handle the streaming API, ones listens to user's input as well as executes REST API and they need to share some variables. After tried ctypes, SyncManage or Queue, I found out that a database solution is easier and less buggy. So SQLAlchemy exists.

  - I only store Tweet and Message ID (not the content) locally and delete all when program exit. The reason is Twitter API's Tweet/Message ID is too long for user to type a command like "rep 489242568104095234 also like it!". In DB Tweet/Message ID is a small number which map 1-by-1 to the "real" Tweet/Message ID.

  - 2 process need to know the new theme when user type a command to change their current theme. So Theme exists in DB.

Sorry for the long reply. Hope that there is a smarter solution and thanks very much again

Regards

[toc] | [prev] | [standalone]

Back to top | Article view | comp.lang.python

csiph-web