[TriPython] TriZPUG Digest, Vol 148, Issue 2
Kel C
kmcmcurtis7 at gmail.com
Fri Aug 7 18:17:59 EDT 2020
Hey Rex! No worries. I work for NC Dept of Insurance. Please go to out
website ncdoi.gov under Consumer Services and file a complaint. We can look
into it for you. Provide as much information as you can and any
documentation you can upload.
If you have any questions please let me know.
Have a great weekend!
Kelly
On Thu, Aug 6, 2020, 9:02 PM Rex Dwyer <rexadwyer at gmail.com> wrote:
> Hi everyone,
> I’m very embarrassed. I meant to send my message privately to Chris as a
> State Employee. I didn’t intend to use this group as a forum to
> bad-mouth
> Blue Cross. Not sure how that happened. Sorry.
> Rex
> On Thu, Aug 6, 2020 at 3:07 PM <[1]trizpug-request at python.org> wrote:
>
> Send TriZPUG mailing list submissions to
> [2]trizpug at python.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> [3]https://mail.python.org/mailman/listinfo/trizpug
> or, via email, send a message with subject or body 'help' to
> [4]trizpug-request at python.org
>
> You can reach the person managing the list at
> [5]trizpug-owner at python.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of TriZPUG digest..."
> Today's Topics:
>
> 1. Re: TriZPUG Digest, Vol 143, Issue 7 (Rex Dwyer)
>
> ---------- Forwarded message ----------
> From: Rex Dwyer <[6]rexadwyer at gmail.com>
> To: [7]trizpug at python.org
> Cc:
> Bcc:
> Date: Thu, 6 Aug 2020 15:06:14 -0400
> Subject: Re: [TriPython] TriZPUG Digest, Vol 143, Issue 7
> Hi Chris,
> I wondered if you have a spouse or know people who do who have
> State
> Health Plan as secondary insurance. It appears that they have been
> systematically ripping me off. I had broken leg and surgery in
> 2019.
> I
> had a gazillion claims. They were not applying primary payments to
> my
> deductible and coinsurance as required, and even discouraged
> providers
> from filing claims.
> If you know anyone in this boat, I can share details. In my case, I
> am a
> retiree and have primary from my current employer.
> Rex
> On Thu, Mar 12, 2020 at 9:36 PM Rex Dwyer <[1][8]
> rexadwyer at gmail.com>
> wrote:
>
> ... I am on vacation in Taiwan ...
> When you go into a hotel, they take your temperature and spray
> your
> hands with alcohol, also there are ir cameras scanning passers-by
> in
> other public places. I’m guessing NC will soon have more cases
> than
> Taiwan.
> On Fri, Mar 13, 2020 at 7:15 AM <[2][9]
> trizpug-request at python.org>
> wrote:
>
> Send TriZPUG mailing list submissions to
> [3][10]trizpug at python.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> [4][11]
> https://mail.python.org/mailman/listinfo/trizpug
> or, via email, send a message with subject or body 'help' to
> [5][12]trizpug-request at python.org
>
> You can reach the person managing the list at
> [6][13]trizpug-owner at python.org
>
> When replying, please edit your Subject line so it is more
> specific
> than "Re: Contents of TriZPUG digest..."
> Today's Topics:
>
> 1. Re: TriPython and early social isolation effectiveness
> (Calloway, Chris)
> 2. Re: TriPython and early social isolation effectiveness
> (Andrew Knight)
> 3. Re: TriPython and early social isolation effectiveness
> (Tobias McNulty)
>
> ---------- Forwarded message ----------
> From: "Calloway, Chris" <[7][14]cbc at unc.edu>
> To: "Triangle (North Carolina) Python Users Group (formerly
> TriZPUG)"
> <[8][15]trizpug at python.org>
> Cc:
> Bcc:
> Date: Thu, 12 Mar 2020 22:53:57 +0000
> Subject: Re: [TriPython] TriPython and early social isolation
> effectiveness
> Kevin has also given the go-ahead to cancel the next Raleigh
> Project Night
> in anticipation of a request from Red Hat to cease events.
>
>
>
> RENCI has also encouraged me to work at home during the
> foreseeable
> future. I think it would be kind of against that grain to
> continue
> meeting
> there as well for a while.
>
>
>
> Therefore, consider TriPython regular event activities
> suspended
> until
> further notice.
>
>
>
> --
>
> Sincerely,
>
>
>
> Chris Calloway
>
> Applications Analyst
>
> University of North Carolina
>
> Renaissance Computing Institute
>
> (919) 599-3530
>
>
>
>
>
> On 3/12/20, 6:16 PM, "Calloway, Chris" <[1][9][16]
> cbc at unc.edu>
> wrote:
>
>
>
> In light of developments of the last 24 hours, I have
> started
> discussions
> with TriPython's event hosts (Eric, Kevin, and Steve)
> regarding
> their
> thoughts on a suspension of TriPython events until further
> notice.
>
>
>
> While I await all the host responses, Eric and I at least
> agree
> that there
> will not be a Durham Project Night at Caktus next week. And
> I
> will
> also be
> postponing the March 26 featured speaker meeting at Caktus,
> with my
> apologies to Travis Hurant.
>
>
>
> I will keep you posted of the status of TriPython events as
> developments
> occur.
>
>
>
> --
>
> Sincerely,
>
>
>
> Chris Calloway
>
> Applications Analyst
>
> University of North Carolina
>
> Renaissance Computing Institute
>
> (919) 599-3530
>
>
>
> References
>
> Visible links
> 1. mailto:[10][17]cbc at unc.edu
>
> ---------- Forwarded message ----------
> From: Andrew Knight <[11][18]andylpk247 at gmail.com>
> To: "Triangle (North Carolina) Python Users Group (formerly
> TriZPUG)"
> <[12][19]trizpug at python.org>
> Cc:
> Bcc:
> Date: Thu, 12 Mar 2020 18:55:39 -0400
> Subject: Re: [TriPython] TriPython and early social isolation
> effectiveness
> Shucks, tough blow, but it’s for the best. Stay Python
> strong,
> everyone!
> Chris, thanks for everything.
> —Pandy
> On Thu, Mar 12, 2020 at 6:54 PM Calloway, Chris
> <[1][13][20]cbc at unc.edu> wrote:
>
> Kevin has also given the go-ahead to cancel the next
> Raleigh
> Project
> Night
> in anticipation of a request from Red Hat to cease
> events.
>
>
>
> RENCI has also encouraged me to work at home during the
> foreseeable
> future. I think it would be kind of against that grain
> to
> continue
> meeting
> there as well for a while.
>
>
>
> Therefore, consider TriPython regular event activities
> suspended
> until
> further notice.
>
>
>
> --
>
> Sincerely,
>
>
>
> Chris Calloway
>
> Applications Analyst
>
> University of North Carolina
>
> Renaissance Computing Institute
>
> (919) 599-3530
>
>
>
>
>
> On 3/12/20, 6:16 PM, "Calloway, Chris"
> <[1][2][14][21]cbc at unc.edu>
> wrote:
>
>
>
> In light of developments of the last 24 hours, I have
> started
> discussions
> with TriPython's event hosts (Eric, Kevin, and Steve)
> regarding their
> thoughts on a suspension of TriPython events until
> further
> notice.
>
>
>
> While I await all the host responses, Eric and I at
> least
> agree that
> there
> will not be a Durham Project Night at Caktus next week.
> And I
> will
> also be
> postponing the March 26 featured speaker meeting at
> Caktus,
> with my
> apologies to Travis Hurant.
>
>
>
> I will keep you posted of the status of TriPython
> events
> as
> developments
> occur.
>
>
>
> --
>
> Sincerely,
>
>
>
> Chris Calloway
>
> Applications Analyst
>
> University of North Carolina
>
> Renaissance Computing Institute
>
> (919) 599-3530
>
>
>
> References
>
> Visible links
> 1. mailto:[3][15][22]cbc at unc.edu
> _______________________________________________
> TriZPUG mailing list
> [4][16][23]TriZPUG at python.org
> [5][17][24]
> https://mail.python.org/mailman/listinfo/trizpug
> [6][18][25]http://tripython.org is the Triangle Python
> Users
> Group
>
> References
>
> Visible links
> 1. mailto:[19][26]cbc at unc.edu
> 2. mailto:[20][27]cbc at unc.edu
> 3. mailto:[21][28]cbc at unc.edu
> 4. mailto:[22][29]TriZPUG at python.org
> 5. [23][30]https://mail.python.org/mailman/listinfo/trizpug
> 6. [24][31]http://tripython.org/
>
> ---------- Forwarded message ----------
> From: Tobias McNulty <[25][32]tobias at caktusgroup.com>
> To: "Triangle (North Carolina) Python Users Group (formerly
> TriZPUG)"
> <[26][33]trizpug at python.org>
> Cc:
> Bcc:
> Date: Thu, 12 Mar 2020 19:14:55 -0400
> Subject: Re: [TriPython] TriPython and early social isolation
> effectiveness
> Thanks everyone for your understanding. This thread is
> timely
> as we
> were
> just discussing at Caktus today the need to close our space
> to
> gatherings.
> We are all working remotely whenever possible.
> I hope that everyone stays safe and well and that we can
> resume
> these get
> togethers again soon.
> Best,
>
> Tobias McNulty
> Chief Executive Officer
>
> [1][27][34]tobias at caktusgroup.com
> [2][28][35]www.caktusgroup.com
>
> On Thu, Mar 12, 2020 at 6:56 PM Andrew Knight
> <[3][29][36]andylpk247 at gmail.com>
> wrote:
>
> Shucks, tough blow, but it’s for the best. Stay Python
> strong,
> everyone!
> Chris, thanks for everything.
> —Pandy
> On Thu, Mar 12, 2020 at 6:54 PM Calloway, Chris
> <[1][4][30][37]cbc at unc.edu>
> wrote:
>
> Kevin has also given the go-ahead to cancel the
> next
> Raleigh
> Project
> Night
> in anticipation of a request from Red Hat to cease
> events.
>
>
>
> RENCI has also encouraged me to work at home
> during
> the
> foreseeable
> future. I think it would be kind of against that
> grain to
> continue
> meeting
> there as well for a while.
>
>
>
> Therefore, consider TriPython regular event
> activities
> suspended
> until
> further notice.
>
>
>
> --
>
> Sincerely,
>
>
>
> Chris Calloway
>
> Applications Analyst
>
> University of North Carolina
>
> Renaissance Computing Institute
>
> (919) 599-3530
>
>
>
>
>
> On 3/12/20, 6:16 PM, "Calloway, Chris"
> <[1][2][5][31][38]cbc at unc.edu>
> wrote:
>
>
>
> In light of developments of the last 24 hours, I
> have
> started
> discussions
> with TriPython's event hosts (Eric, Kevin, and
> Steve)
> regarding
> their
> thoughts on a suspension of TriPython events until
> further
> notice.
>
>
>
> While I await all the host responses, Eric and I
> at
> least
> agree
> that
> there
> will not be a Durham Project Night at Caktus next
> week.
> And I
> will
> also be
> postponing the March 26 featured speaker meeting
> at
> Caktus, with
> my
> apologies to Travis Hurant.
>
>
>
> I will keep you posted of the status of TriPython
> events
> as
> developments
> occur.
>
>
>
> --
>
> Sincerely,
>
>
>
> Chris Calloway
>
> Applications Analyst
>
> University of North Carolina
>
> Renaissance Computing Institute
>
> (919) 599-3530
>
>
>
> References
>
> Visible links
> 1. mailto:[3][6][32][39]cbc at unc.edu
> _______________________________________________
> TriZPUG mailing list
> [4][7][33][40]TriZPUG at python.org
>
> [5][8][34][41]https://mail.python.org/mailman/listinfo/trizpug
> [6][9][35][42]http://tripython.org is the Triangle
> Python Users
> Group
>
> References
>
> Visible links
> 1. mailto:[10][36][43]cbc at unc.edu
> 2. mailto:[11][37][44]cbc at unc.edu
> 3. mailto:[12][38][45]cbc at unc.edu
> 4. mailto:[13][39][46]TriZPUG at python.org
> 5.
> [14][40][47]https://mail.python.org/mailman/listinfo/trizpug
> 6. [15][41][48]http://tripython.org/
> _______________________________________________
> TriZPUG mailing list
> [16][42][49]TriZPUG at python.org
> [17][43][50]
> https://mail.python.org/mailman/listinfo/trizpug
> [18][44][51]http://tripython.org is the Triangle Python
> Users Group
>
> References
>
> Visible links
> 1. mailto:[45][52]tobias at caktusgroup.com
> 2. [46][53]http://www.caktusgroup.com/
> 3. mailto:[47][54]andylpk247 at gmail.com
> 4. mailto:[48][55]cbc at unc.edu
> 5. mailto:[49][56]cbc at unc.edu
> 6. mailto:[50][57]cbc at unc.edu
> 7. mailto:[51][58]TriZPUG at python.org
> 8. [52][59]https://mail.python.org/mailman/listinfo/trizpug
> 9. [53][60]http://tripython.org/
> 10. mailto:[54][61]cbc at unc.edu
> 11. mailto:[55][62]cbc at unc.edu
> 12. mailto:[56][63]cbc at unc.edu
> 13. mailto:[57][64]TriZPUG at python.org
> 14. [58][65]https://mail.python.org/mailman/listinfo/trizpug
> 15. [59][66]http://tripython.org/
> 16. mailto:[60][67]TriZPUG at python.org
> 17. [61][68]https://mail.python.org/mailman/listinfo/trizpug
> 18. [62][69]http://tripython.org/
> _______________________________________________
> TriZPUG mailing list
> [63][70]TriZPUG at python.org
> [64][71]https://mail.python.org/mailman/listinfo/trizpug
> [65][72]http://tripython.org is the Triangle Python Users
> Group
>
> --
> Rex A. Dwyer
>
> --
> Rex A. Dwyer
>
> References
>
> Visible links
> 1. mailto:[73]rexadwyer at gmail.com
> 2. mailto:[74]trizpug-request at python.org
> 3. mailto:[75]trizpug at python.org
> 4. [76]https://mail.python.org/mailman/listinfo/trizpug
> 5. mailto:[77]trizpug-request at python.org
> 6. mailto:[78]trizpug-owner at python.org
> 7. mailto:[79]cbc at unc.edu
> 8. mailto:[80]trizpug at python.org
> 9. mailto:[81]cbc at unc.edu
> 10. mailto:[82]cbc at unc.edu
> 11. mailto:[83]andylpk247 at gmail.com
> 12. mailto:[84]trizpug at python.org
> 13. mailto:[85]cbc at unc.edu
> 14. mailto:[86]cbc at unc.edu
> 15. mailto:[87]cbc at unc.edu
> 16. mailto:[88]TriZPUG at python.org
> 17. [89]https://mail.python.org/mailman/listinfo/trizpug
> 18. [90]http://tripython.org/
> 19. mailto:[91]cbc at unc.edu
> 20. mailto:[92]cbc at unc.edu
> 21. mailto:[93]cbc at unc.edu
> 22. mailto:[94]TriZPUG at python.org
> 23. [95]https://mail.python.org/mailman/listinfo/trizpug
> 24. [96]http://tripython.org/
> 25. mailto:[97]tobias at caktusgroup.com
> 26. mailto:[98]trizpug at python.org
> 27. mailto:[99]tobias at caktusgroup.com
> 28. [100]http://www.caktusgroup.com/
> 29. mailto:[101]andylpk247 at gmail.com
> 30. mailto:[102]cbc at unc.edu
> 31. mailto:[103]cbc at unc.edu
> 32. mailto:[104]cbc at unc.edu
> 33. mailto:[105]TriZPUG at python.org
> 34. [106]https://mail.python.org/mailman/listinfo/trizpug
> 35. [107]http://tripython.org/
> 36. mailto:[108]cbc at unc.edu
> 37. mailto:[109]cbc at unc.edu
> 38. mailto:[110]cbc at unc.edu
> 39. mailto:[111]TriZPUG at python.org
> 40. [112]https://mail.python.org/mailman/listinfo/trizpug
> 41. [113]http://tripython.org/
> 42. mailto:[114]TriZPUG at python.org
> 43. [115]https://mail.python.org/mailman/listinfo/trizpug
> 44. [116]http://tripython.org/
> 45. mailto:[117]tobias at caktusgroup.com
> 46. [118]http://www.caktusgroup.com/
> 47. mailto:[119]andylpk247 at gmail.com
> 48. mailto:[120]cbc at unc.edu
> 49. mailto:[121]cbc at unc.edu
> 50. mailto:[122]cbc at unc.edu
> 51. mailto:[123]TriZPUG at python.org
> 52. [124]https://mail.python.org/mailman/listinfo/trizpug
> 53. [125]http://tripython.org/
> 54. mailto:[126]cbc at unc.edu
> 55. mailto:[127]cbc at unc.edu
> 56. mailto:[128]cbc at unc.edu
> 57. mailto:[129]TriZPUG at python.org
> 58. [130]https://mail.python.org/mailman/listinfo/trizpug
> 59. [131]http://tripython.org/
> 60. mailto:[132]TriZPUG at python.org
> 61. [133]https://mail.python.org/mailman/listinfo/trizpug
> 62. [134]http://tripython.org/
> 63. mailto:[135]TriZPUG at python.org
> 64. [136]https://mail.python.org/mailman/listinfo/trizpug
> 65. [137]http://tripython.org/
> _______________________________________________
> TriZPUG mailing list
> [138]TriZPUG at python.org
> [139]https://mail.python.org/mailman/listinfo/trizpug
> [140]http://tripython.org is the Triangle Python Users Group
>
> --
> Rex A. Dwyer
>
> References
>
> Visible links
> 1. mailto:trizpug-request at python.org
> 2. mailto:trizpug at python.org
> 3. https://mail.python.org/mailman/listinfo/trizpug
> 4. mailto:trizpug-request at python.org
> 5. mailto:trizpug-owner at python.org
> 6. mailto:rexadwyer at gmail.com
> 7. mailto:trizpug at python.org
> 8. mailto:rexadwyer at gmail.com
> 9. mailto:trizpug-request at python.org
> 10. mailto:trizpug at python.org
> 11. https://mail.python.org/mailman/listinfo/trizpug
> 12. mailto:trizpug-request at python.org
> 13. mailto:trizpug-owner at python.org
> 14. mailto:cbc at unc.edu
> 15. mailto:trizpug at python.org
> 16. mailto:cbc at unc.edu
> 17. mailto:cbc at unc.edu
> 18. mailto:andylpk247 at gmail.com
> 19. mailto:trizpug at python.org
> 20. mailto:cbc at unc.edu
> 21. mailto:cbc at unc.edu
> 22. mailto:cbc at unc.edu
> 23. mailto:TriZPUG at python.org
> 24. https://mail.python.org/mailman/listinfo/trizpug
> 25. http://tripython.org/
> 26. mailto:cbc at unc.edu
> 27. mailto:cbc at unc.edu
> 28. mailto:cbc at unc.edu
> 29. mailto:TriZPUG at python.org
> 30. https://mail.python.org/mailman/listinfo/trizpug
> 31. http://tripython.org/
> 32. mailto:tobias at caktusgroup.com
> 33. mailto:trizpug at python.org
> 34. mailto:tobias at caktusgroup.com
> 35. http://www.caktusgroup.com/
> 36. mailto:andylpk247 at gmail.com
> 37. mailto:cbc at unc.edu
> 38. mailto:cbc at unc.edu
> 39. mailto:cbc at unc.edu
> 40. mailto:TriZPUG at python.org
> 41. https://mail.python.org/mailman/listinfo/trizpug
> 42. http://tripython.org/
> 43. mailto:cbc at unc.edu
> 44. mailto:cbc at unc.edu
> 45. mailto:cbc at unc.edu
> 46. mailto:TriZPUG at python.org
> 47. https://mail.python.org/mailman/listinfo/trizpug
> 48. http://tripython.org/
> 49. mailto:TriZPUG at python.org
> 50. https://mail.python.org/mailman/listinfo/trizpug
> 51. http://tripython.org/
> 52. mailto:tobias at caktusgroup.com
> 53. http://www.caktusgroup.com/
> 54. mailto:andylpk247 at gmail.com
> 55. mailto:cbc at unc.edu
> 56. mailto:cbc at unc.edu
> 57. mailto:cbc at unc.edu
> 58. mailto:TriZPUG at python.org
> 59. https://mail.python.org/mailman/listinfo/trizpug
> 60. http://tripython.org/
> 61. mailto:cbc at unc.edu
> 62. mailto:cbc at unc.edu
> 63. mailto:cbc at unc.edu
> 64. mailto:TriZPUG at python.org
> 65. https://mail.python.org/mailman/listinfo/trizpug
> 66. http://tripython.org/
> 67. mailto:TriZPUG at python.org
> 68. https://mail.python.org/mailman/listinfo/trizpug
> 69. http://tripython.org/
> 70. mailto:TriZPUG at python.org
> 71. https://mail.python.org/mailman/listinfo/trizpug
> 72. http://tripython.org/
> 73. mailto:rexadwyer at gmail.com
> 74. mailto:trizpug-request at python.org
> 75. mailto:trizpug at python.org
> 76. https://mail.python.org/mailman/listinfo/trizpug
> 77. mailto:trizpug-request at python.org
> 78. mailto:trizpug-owner at python.org
> 79. mailto:cbc at unc.edu
> 80. mailto:trizpug at python.org
> 81. mailto:cbc at unc.edu
> 82. mailto:cbc at unc.edu
> 83. mailto:andylpk247 at gmail.com
> 84. mailto:trizpug at python.org
> 85. mailto:cbc at unc.edu
> 86. mailto:cbc at unc.edu
> 87. mailto:cbc at unc.edu
> 88. mailto:TriZPUG at python.org
> 89. https://mail.python.org/mailman/listinfo/trizpug
> 90. http://tripython.org/
> 91. mailto:cbc at unc.edu
> 92. mailto:cbc at unc.edu
> 93. mailto:cbc at unc.edu
> 94. mailto:TriZPUG at python.org
> 95. https://mail.python.org/mailman/listinfo/trizpug
> 96. http://tripython.org/
> 97. mailto:tobias at caktusgroup.com
> 98. mailto:trizpug at python.org
> 99. mailto:tobias at caktusgroup.com
> 100. http://www.caktusgroup.com/
> 101. mailto:andylpk247 at gmail.com
> 102. mailto:cbc at unc.edu
> 103. mailto:cbc at unc.edu
> 104. mailto:cbc at unc.edu
> 105. mailto:TriZPUG at python.org
> 106. https://mail.python.org/mailman/listinfo/trizpug
> 107. http://tripython.org/
> 108. mailto:cbc at unc.edu
> 109. mailto:cbc at unc.edu
> 110. mailto:cbc at unc.edu
> 111. mailto:TriZPUG at python.org
> 112. https://mail.python.org/mailman/listinfo/trizpug
> 113. http://tripython.org/
> 114. mailto:TriZPUG at python.org
> 115. https://mail.python.org/mailman/listinfo/trizpug
> 116. http://tripython.org/
> 117. mailto:tobias at caktusgroup.com
> 118. http://www.caktusgroup.com/
> 119. mailto:andylpk247 at gmail.com
> 120. mailto:cbc at unc.edu
> 121. mailto:cbc at unc.edu
> 122. mailto:cbc at unc.edu
> 123. mailto:TriZPUG at python.org
> 124. https://mail.python.org/mailman/listinfo/trizpug
> 125. http://tripython.org/
> 126. mailto:cbc at unc.edu
> 127. mailto:cbc at unc.edu
> 128. mailto:cbc at unc.edu
> 129. mailto:TriZPUG at python.org
> 130. https://mail.python.org/mailman/listinfo/trizpug
> 131. http://tripython.org/
> 132. mailto:TriZPUG at python.org
> 133. https://mail.python.org/mailman/listinfo/trizpug
> 134. http://tripython.org/
> 135. mailto:TriZPUG at python.org
> 136. https://mail.python.org/mailman/listinfo/trizpug
> 137. http://tripython.org/
> 138. mailto:TriZPUG at python.org
> 139. https://mail.python.org/mailman/listinfo/trizpug
> 140. http://tripython.org/
> _______________________________________________
> TriZPUG mailing list
> TriZPUG at python.org
> https://mail.python.org/mailman/listinfo/trizpug
> http://tripython.org is the Triangle Python Users Group
>
-------------- next part --------------
Hey Rex! No worries. I work for NC Dept of Insurance. Please go to out
website [1]ncdoi.gov under Consumer Services and file a complaint. We can
look into it for you. Provide as much information as you can and any
documentation you can upload.
If you have any questions please let me know.
Have a great weekend!
Kelly
On Thu, Aug 6, 2020, 9:02 PM Rex Dwyer <[2]rexadwyer at gmail.com> wrote:
Hi everyone,
I’m very embarrassed. I meant to send my message privately to Chris
as a
State Employee. I didn’t intend to use this group as a forum to
bad-mouth
Blue Cross. Not sure how that happened. Sorry.
Rex
On Thu, Aug 6, 2020 at 3:07 PM <[1][3]trizpug-request at python.org>
wrote:
Send TriZPUG mailing list submissions to
[2][4]trizpug at python.org
To subscribe or unsubscribe via the World Wide Web, visit
[3][5]https://mail.python.org/mailman/listinfo/trizpug
or, via email, send a message with subject or body 'help' to
[4][6]trizpug-request at python.org
You can reach the person managing the list at
[5][7]trizpug-owner at python.org
When replying, please edit your Subject line so it is more specific
than "Re: Contents of TriZPUG digest..."
Today's Topics:
1. Re: TriZPUG Digest, Vol 143, Issue 7 (Rex Dwyer)
---------- Forwarded message ----------
From: Rex Dwyer <[6][8]rexadwyer at gmail.com>
To: [7][9]trizpug at python.org
Cc:
Bcc:
Date: Thu, 6 Aug 2020 15:06:14 -0400
Subject: Re: [TriPython] TriZPUG Digest, Vol 143, Issue 7
Hi Chris,
I wondered if you have a spouse or know people who do who have
State
Health Plan as secondary insurance. It appears that they have
been
systematically ripping me off. I had broken leg and surgery in
2019.
I
had a gazillion claims. They were not applying primary payments
to my
deductible and coinsurance as required, and even discouraged
providers
from filing claims.
If you know anyone in this boat, I can share details. In my
case, I
am a
retiree and have primary from my current employer.
Rex
On Thu, Mar 12, 2020 at 9:36 PM Rex Dwyer
<[1][8][10]rexadwyer at gmail.com>
wrote:
... I am on vacation in Taiwan ...
When you go into a hotel, they take your temperature and spray
your
hands with alcohol, also there are ir cameras scanning
passers-by
in
other public places. I’m guessing NC will soon have more
cases
than
Taiwan.
On Fri, Mar 13, 2020 at 7:15 AM
<[2][9][11]trizpug-request at python.org>
wrote:
Send TriZPUG mailing list submissions to
[3][10][12]trizpug at python.org
To subscribe or unsubscribe via the World Wide Web, visit
[4][11][13]https://mail.python.org/mailman/listinfo/trizpug
or, via email, send a message with subject or body 'help' to
[5][12][14]trizpug-request at python.org
You can reach the person managing the list at
[6][13][15]trizpug-owner at python.org
When replying, please edit your Subject line so it is more
specific
than "Re: Contents of TriZPUG digest..."
Today's Topics:
1. Re: TriPython and early social isolation effectiveness
(Calloway, Chris)
2. Re: TriPython and early social isolation effectiveness
(Andrew Knight)
3. Re: TriPython and early social isolation effectiveness
(Tobias McNulty)
---------- Forwarded message ----------
From: "Calloway, Chris" <[7][14][16]cbc at unc.edu>
To: "Triangle (North Carolina) Python Users Group (formerly
TriZPUG)"
<[8][15][17]trizpug at python.org>
Cc:
Bcc:
Date: Thu, 12 Mar 2020 22:53:57 +0000
Subject: Re: [TriPython] TriPython and early social
isolation
effectiveness
Kevin has also given the go-ahead to cancel the next
Raleigh
Project Night
in anticipation of a request from Red Hat to cease
events.
RENCI has also encouraged me to work at home during the
foreseeable
future. I think it would be kind of against that grain to
continue
meeting
there as well for a while.
Therefore, consider TriPython regular event activities
suspended
until
further notice.
--
Sincerely,
Chris Calloway
Applications Analyst
University of North Carolina
Renaissance Computing Institute
(919) 599-3530
On 3/12/20, 6:16 PM, "Calloway, Chris"
<[1][9][16][18]cbc at unc.edu>
wrote:
In light of developments of the last 24 hours, I have
started
discussions
with TriPython's event hosts (Eric, Kevin, and Steve)
regarding
their
thoughts on a suspension of TriPython events until
further
notice.
While I await all the host responses, Eric and I at least
agree
that there
will not be a Durham Project Night at Caktus next week.
And I
will
also be
postponing the March 26 featured speaker meeting at
Caktus,
with my
apologies to Travis Hurant.
I will keep you posted of the status of TriPython events
as
developments
occur.
--
Sincerely,
Chris Calloway
Applications Analyst
University of North Carolina
Renaissance Computing Institute
(919) 599-3530
References
Visible links
1. mailto:[10][17][19]cbc at unc.edu
---------- Forwarded message ----------
From: Andrew Knight <[11][18][20]andylpk247 at gmail.com>
To: "Triangle (North Carolina) Python Users Group (formerly
TriZPUG)"
<[12][19][21]trizpug at python.org>
Cc:
Bcc:
Date: Thu, 12 Mar 2020 18:55:39 -0400
Subject: Re: [TriPython] TriPython and early social
isolation
effectiveness
Shucks, tough blow, but it’s for the best. Stay Python
strong,
everyone!
Chris, thanks for everything.
—Pandy
On Thu, Mar 12, 2020 at 6:54 PM Calloway, Chris
<[1][13][20][22]cbc at unc.edu> wrote:
Kevin has also given the go-ahead to cancel the next
Raleigh
Project
Night
in anticipation of a request from Red Hat to cease
events.
RENCI has also encouraged me to work at home during
the
foreseeable
future. I think it would be kind of against that
grain to
continue
meeting
there as well for a while.
Therefore, consider TriPython regular event
activities
suspended
until
further notice.
--
Sincerely,
Chris Calloway
Applications Analyst
University of North Carolina
Renaissance Computing Institute
(919) 599-3530
On 3/12/20, 6:16 PM, "Calloway, Chris"
<[1][2][14][21][23]cbc at unc.edu>
wrote:
In light of developments of the last 24 hours, I
have
started
discussions
with TriPython's event hosts (Eric, Kevin, and
Steve)
regarding their
thoughts on a suspension of TriPython events until
further
notice.
While I await all the host responses, Eric and I at
least
agree that
there
will not be a Durham Project Night at Caktus next
week.
And I
will
also be
postponing the March 26 featured speaker meeting at
Caktus,
with my
apologies to Travis Hurant.
I will keep you posted of the status of TriPython
events
as
developments
occur.
--
Sincerely,
Chris Calloway
Applications Analyst
University of North Carolina
Renaissance Computing Institute
(919) 599-3530
References
Visible links
1. mailto:[3][15][22][24]cbc at unc.edu
_______________________________________________
TriZPUG mailing list
[4][16][23][25]TriZPUG at python.org
[5][17][24][26]https://mail.python.org/mailman/listinfo/trizpug
[6][18][25][27]http://tripython.org is the Triangle
Python Users
Group
References
Visible links
1. mailto:[19][26][28]cbc at unc.edu
2. mailto:[20][27][29]cbc at unc.edu
3. mailto:[21][28][30]cbc at unc.edu
4. mailto:[22][29][31]TriZPUG at python.org
5.
[23][30][32]https://mail.python.org/mailman/listinfo/trizpug
6. [24][31][33]http://tripython.org/
---------- Forwarded message ----------
From: Tobias McNulty <[25][32][34]tobias at caktusgroup.com>
To: "Triangle (North Carolina) Python Users Group (formerly
TriZPUG)"
<[26][33][35]trizpug at python.org>
Cc:
Bcc:
Date: Thu, 12 Mar 2020 19:14:55 -0400
Subject: Re: [TriPython] TriPython and early social
isolation
effectiveness
Thanks everyone for your understanding. This thread is
timely
as we
were
just discussing at Caktus today the need to close our
space to
gatherings.
We are all working remotely whenever possible.
I hope that everyone stays safe and well and that we can
resume
these get
togethers again soon.
Best,
Tobias McNulty
Chief Executive Officer
[1][27][34][36]tobias at caktusgroup.com
[2][28][35][37]www.caktusgroup.com
On Thu, Mar 12, 2020 at 6:56 PM Andrew Knight
<[3][29][36][38]andylpk247 at gmail.com>
wrote:
Shucks, tough blow, but it’s for the best. Stay
Python
strong,
everyone!
Chris, thanks for everything.
—Pandy
On Thu, Mar 12, 2020 at 6:54 PM Calloway, Chris
<[1][4][30][37][39]cbc at unc.edu>
wrote:
Kevin has also given the go-ahead to cancel the
next
Raleigh
Project
Night
in anticipation of a request from Red Hat to
cease
events.
RENCI has also encouraged me to work at home
during
the
foreseeable
future. I think it would be kind of against
that
grain to
continue
meeting
there as well for a while.
Therefore, consider TriPython regular event
activities
suspended
until
further notice.
--
Sincerely,
Chris Calloway
Applications Analyst
University of North Carolina
Renaissance Computing Institute
(919) 599-3530
On 3/12/20, 6:16 PM, "Calloway, Chris"
<[1][2][5][31][38][40]cbc at unc.edu>
wrote:
In light of developments of the last 24 hours,
I
have
started
discussions
with TriPython's event hosts (Eric, Kevin, and
Steve)
regarding
their
thoughts on a suspension of TriPython events
until
further
notice.
While I await all the host responses, Eric and
I at
least
agree
that
there
will not be a Durham Project Night at Caktus
next
week.
And I
will
also be
postponing the March 26 featured speaker
meeting at
Caktus, with
my
apologies to Travis Hurant.
I will keep you posted of the status of
TriPython
events
as
developments
occur.
--
Sincerely,
Chris Calloway
Applications Analyst
University of North Carolina
Renaissance Computing Institute
(919) 599-3530
References
Visible links
1. mailto:[3][6][32][39][41]cbc at unc.edu
_______________________________________________
TriZPUG mailing list
[4][7][33][40][42]TriZPUG at python.org
[5][8][34][41][43]https://mail.python.org/mailman/listinfo/trizpug
[6][9][35][42][44]http://tripython.org is the
Triangle
Python Users
Group
References
Visible links
1. mailto:[10][36][43][45]cbc at unc.edu
2. mailto:[11][37][44][46]cbc at unc.edu
3. mailto:[12][38][45][47]cbc at unc.edu
4. mailto:[13][39][46][48]TriZPUG at python.org
5.
[14][40][47][49]https://mail.python.org/mailman/listinfo/trizpug
6. [15][41][48][50]http://tripython.org/
_______________________________________________
TriZPUG mailing list
[16][42][49][51]TriZPUG at python.org
[17][43][50][52]https://mail.python.org/mailman/listinfo/trizpug
[18][44][51][53]http://tripython.org is the Triangle
Python
Users Group
References
Visible links
1. mailto:[45][52][54]tobias at caktusgroup.com
2. [46][53][55]http://www.caktusgroup.com/
3. mailto:[47][54][56]andylpk247 at gmail.com
4. mailto:[48][55][57]cbc at unc.edu
5. mailto:[49][56][58]cbc at unc.edu
6. mailto:[50][57][59]cbc at unc.edu
7. mailto:[51][58][60]TriZPUG at python.org
8.
[52][59][61]https://mail.python.org/mailman/listinfo/trizpug
9. [53][60][62]http://tripython.org/
10. mailto:[54][61][63]cbc at unc.edu
11. mailto:[55][62][64]cbc at unc.edu
12. mailto:[56][63][65]cbc at unc.edu
13. mailto:[57][64][66]TriZPUG at python.org
14.
[58][65][67]https://mail.python.org/mailman/listinfo/trizpug
15. [59][66][68]http://tripython.org/
16. mailto:[60][67][69]TriZPUG at python.org
17.
[61][68][70]https://mail.python.org/mailman/listinfo/trizpug
18. [62][69][71]http://tripython.org/
_______________________________________________
TriZPUG mailing list
[63][70][72]TriZPUG at python.org
[64][71][73]https://mail.python.org/mailman/listinfo/trizpug
[65][72][74]http://tripython.org is the Triangle Python
Users Group
--
Rex A. Dwyer
--
Rex A. Dwyer
References
Visible links
1. mailto:[73][75]rexadwyer at gmail.com
2. mailto:[74][76]trizpug-request at python.org
3. mailto:[75][77]trizpug at python.org
4. [76][78]https://mail.python.org/mailman/listinfo/trizpug
5. mailto:[77][79]trizpug-request at python.org
6. mailto:[78][80]trizpug-owner at python.org
7. mailto:[79][81]cbc at unc.edu
8. mailto:[80][82]trizpug at python.org
9. mailto:[81][83]cbc at unc.edu
10. mailto:[82][84]cbc at unc.edu
11. mailto:[83][85]andylpk247 at gmail.com
12. mailto:[84][86]trizpug at python.org
13. mailto:[85][87]cbc at unc.edu
14. mailto:[86][88]cbc at unc.edu
15. mailto:[87][89]cbc at unc.edu
16. mailto:[88][90]TriZPUG at python.org
17. [89][91]https://mail.python.org/mailman/listinfo/trizpug
18. [90][92]http://tripython.org/
19. mailto:[91][93]cbc at unc.edu
20. mailto:[92][94]cbc at unc.edu
21. mailto:[93][95]cbc at unc.edu
22. mailto:[94][96]TriZPUG at python.org
23. [95][97]https://mail.python.org/mailman/listinfo/trizpug
24. [96][98]http://tripython.org/
25. mailto:[97][99]tobias at caktusgroup.com
26. mailto:[98][100]trizpug at python.org
27. mailto:[99][101]tobias at caktusgroup.com
28. [100][102]http://www.caktusgroup.com/
29. mailto:[101][103]andylpk247 at gmail.com
30. mailto:[102][104]cbc at unc.edu
31. mailto:[103][105]cbc at unc.edu
32. mailto:[104][106]cbc at unc.edu
33. mailto:[105][107]TriZPUG at python.org
34. [106][108]https://mail.python.org/mailman/listinfo/trizpug
35. [107][109]http://tripython.org/
36. mailto:[108][110]cbc at unc.edu
37. mailto:[109][111]cbc at unc.edu
38. mailto:[110][112]cbc at unc.edu
39. mailto:[111][113]TriZPUG at python.org
40. [112][114]https://mail.python.org/mailman/listinfo/trizpug
41. [113][115]http://tripython.org/
42. mailto:[114][116]TriZPUG at python.org
43. [115][117]https://mail.python.org/mailman/listinfo/trizpug
44. [116][118]http://tripython.org/
45. mailto:[117][119]tobias at caktusgroup.com
46. [118][120]http://www.caktusgroup.com/
47. mailto:[119][121]andylpk247 at gmail.com
48. mailto:[120][122]cbc at unc.edu
49. mailto:[121][123]cbc at unc.edu
50. mailto:[122][124]cbc at unc.edu
51. mailto:[123][125]TriZPUG at python.org
52. [124][126]https://mail.python.org/mailman/listinfo/trizpug
53. [125][127]http://tripython.org/
54. mailto:[126][128]cbc at unc.edu
55. mailto:[127][129]cbc at unc.edu
56. mailto:[128][130]cbc at unc.edu
57. mailto:[129][131]TriZPUG at python.org
58. [130][132]https://mail.python.org/mailman/listinfo/trizpug
59. [131][133]http://tripython.org/
60. mailto:[132][134]TriZPUG at python.org
61. [133][135]https://mail.python.org/mailman/listinfo/trizpug
62. [134][136]http://tripython.org/
63. mailto:[135][137]TriZPUG at python.org
64. [136][138]https://mail.python.org/mailman/listinfo/trizpug
65. [137][139]http://tripython.org/
_______________________________________________
TriZPUG mailing list
[138][140]TriZPUG at python.org
[139][141]https://mail.python.org/mailman/listinfo/trizpug
[140][142]http://tripython.org is the Triangle Python Users Group
--
Rex A. Dwyer
References
Visible links
1. mailto:[143]trizpug-request at python.org
2. mailto:[144]trizpug at python.org
3. [145]https://mail.python.org/mailman/listinfo/trizpug
4. mailto:[146]trizpug-request at python.org
5. mailto:[147]trizpug-owner at python.org
6. mailto:[148]rexadwyer at gmail.com
7. mailto:[149]trizpug at python.org
8. mailto:[150]rexadwyer at gmail.com
9. mailto:[151]trizpug-request at python.org
10. mailto:[152]trizpug at python.org
11. [153]https://mail.python.org/mailman/listinfo/trizpug
12. mailto:[154]trizpug-request at python.org
13. mailto:[155]trizpug-owner at python.org
14. mailto:[156]cbc at unc.edu
15. mailto:[157]trizpug at python.org
16. mailto:[158]cbc at unc.edu
17. mailto:[159]cbc at unc.edu
18. mailto:[160]andylpk247 at gmail.com
19. mailto:[161]trizpug at python.org
20. mailto:[162]cbc at unc.edu
21. mailto:[163]cbc at unc.edu
22. mailto:[164]cbc at unc.edu
23. mailto:[165]TriZPUG at python.org
24. [166]https://mail.python.org/mailman/listinfo/trizpug
25. [167]http://tripython.org/
26. mailto:[168]cbc at unc.edu
27. mailto:[169]cbc at unc.edu
28. mailto:[170]cbc at unc.edu
29. mailto:[171]TriZPUG at python.org
30. [172]https://mail.python.org/mailman/listinfo/trizpug
31. [173]http://tripython.org/
32. mailto:[174]tobias at caktusgroup.com
33. mailto:[175]trizpug at python.org
34. mailto:[176]tobias at caktusgroup.com
35. [177]http://www.caktusgroup.com/
36. mailto:[178]andylpk247 at gmail.com
37. mailto:[179]cbc at unc.edu
38. mailto:[180]cbc at unc.edu
39. mailto:[181]cbc at unc.edu
40. mailto:[182]TriZPUG at python.org
41. [183]https://mail.python.org/mailman/listinfo/trizpug
42. [184]http://tripython.org/
43. mailto:[185]cbc at unc.edu
44. mailto:[186]cbc at unc.edu
45. mailto:[187]cbc at unc.edu
46. mailto:[188]TriZPUG at python.org
47. [189]https://mail.python.org/mailman/listinfo/trizpug
48. [190]http://tripython.org/
49. mailto:[191]TriZPUG at python.org
50. [192]https://mail.python.org/mailman/listinfo/trizpug
51. [193]http://tripython.org/
52. mailto:[194]tobias at caktusgroup.com
53. [195]http://www.caktusgroup.com/
54. mailto:[196]andylpk247 at gmail.com
55. mailto:[197]cbc at unc.edu
56. mailto:[198]cbc at unc.edu
57. mailto:[199]cbc at unc.edu
58. mailto:[200]TriZPUG at python.org
59. [201]https://mail.python.org/mailman/listinfo/trizpug
60. [202]http://tripython.org/
61. mailto:[203]cbc at unc.edu
62. mailto:[204]cbc at unc.edu
63. mailto:[205]cbc at unc.edu
64. mailto:[206]TriZPUG at python.org
65. [207]https://mail.python.org/mailman/listinfo/trizpug
66. [208]http://tripython.org/
67. mailto:[209]TriZPUG at python.org
68. [210]https://mail.python.org/mailman/listinfo/trizpug
69. [211]http://tripython.org/
70. mailto:[212]TriZPUG at python.org
71. [213]https://mail.python.org/mailman/listinfo/trizpug
72. [214]http://tripython.org/
73. mailto:[215]rexadwyer at gmail.com
74. mailto:[216]trizpug-request at python.org
75. mailto:[217]trizpug at python.org
76. [218]https://mail.python.org/mailman/listinfo/trizpug
77. mailto:[219]trizpug-request at python.org
78. mailto:[220]trizpug-owner at python.org
79. mailto:[221]cbc at unc.edu
80. mailto:[222]trizpug at python.org
81. mailto:[223]cbc at unc.edu
82. mailto:[224]cbc at unc.edu
83. mailto:[225]andylpk247 at gmail.com
84. mailto:[226]trizpug at python.org
85. mailto:[227]cbc at unc.edu
86. mailto:[228]cbc at unc.edu
87. mailto:[229]cbc at unc.edu
88. mailto:[230]TriZPUG at python.org
89. [231]https://mail.python.org/mailman/listinfo/trizpug
90. [232]http://tripython.org/
91. mailto:[233]cbc at unc.edu
92. mailto:[234]cbc at unc.edu
93. mailto:[235]cbc at unc.edu
94. mailto:[236]TriZPUG at python.org
95. [237]https://mail.python.org/mailman/listinfo/trizpug
96. [238]http://tripython.org/
97. mailto:[239]tobias at caktusgroup.com
98. mailto:[240]trizpug at python.org
99. mailto:[241]tobias at caktusgroup.com
100. [242]http://www.caktusgroup.com/
101. mailto:[243]andylpk247 at gmail.com
102. mailto:[244]cbc at unc.edu
103. mailto:[245]cbc at unc.edu
104. mailto:[246]cbc at unc.edu
105. mailto:[247]TriZPUG at python.org
106. [248]https://mail.python.org/mailman/listinfo/trizpug
107. [249]http://tripython.org/
108. mailto:[250]cbc at unc.edu
109. mailto:[251]cbc at unc.edu
110. mailto:[252]cbc at unc.edu
111. mailto:[253]TriZPUG at python.org
112. [254]https://mail.python.org/mailman/listinfo/trizpug
113. [255]http://tripython.org/
114. mailto:[256]TriZPUG at python.org
115. [257]https://mail.python.org/mailman/listinfo/trizpug
116. [258]http://tripython.org/
117. mailto:[259]tobias at caktusgroup.com
118. [260]http://www.caktusgroup.com/
119. mailto:[261]andylpk247 at gmail.com
120. mailto:[262]cbc at unc.edu
121. mailto:[263]cbc at unc.edu
122. mailto:[264]cbc at unc.edu
123. mailto:[265]TriZPUG at python.org
124. [266]https://mail.python.org/mailman/listinfo/trizpug
125. [267]http://tripython.org/
126. mailto:[268]cbc at unc.edu
127. mailto:[269]cbc at unc.edu
128. mailto:[270]cbc at unc.edu
129. mailto:[271]TriZPUG at python.org
130. [272]https://mail.python.org/mailman/listinfo/trizpug
131. [273]http://tripython.org/
132. mailto:[274]TriZPUG at python.org
133. [275]https://mail.python.org/mailman/listinfo/trizpug
134. [276]http://tripython.org/
135. mailto:[277]TriZPUG at python.org
136. [278]https://mail.python.org/mailman/listinfo/trizpug
137. [279]http://tripython.org/
138. mailto:[280]TriZPUG at python.org
139. [281]https://mail.python.org/mailman/listinfo/trizpug
140. [282]http://tripython.org/
_______________________________________________
TriZPUG mailing list
[283]TriZPUG at python.org
[284]https://mail.python.org/mailman/listinfo/trizpug
[285]http://tripython.org is the Triangle Python Users Group
References
Visible links
1. http://ncdoi.gov/
2. mailto:rexadwyer at gmail.com
3. mailto:trizpug-request at python.org
4. mailto:trizpug at python.org
5. https://mail.python.org/mailman/listinfo/trizpug
6. mailto:trizpug-request at python.org
7. mailto:trizpug-owner at python.org
8. mailto:rexadwyer at gmail.com
9. mailto:trizpug at python.org
10. mailto:rexadwyer at gmail.com
11. mailto:trizpug-request at python.org
12. mailto:trizpug at python.org
13. https://mail.python.org/mailman/listinfo/trizpug
14. mailto:trizpug-request at python.org
15. mailto:trizpug-owner at python.org
16. mailto:cbc at unc.edu
17. mailto:trizpug at python.org
18. mailto:cbc at unc.edu
19. mailto:cbc at unc.edu
20. mailto:andylpk247 at gmail.com
21. mailto:trizpug at python.org
22. mailto:cbc at unc.edu
23. mailto:cbc at unc.edu
24. mailto:cbc at unc.edu
25. mailto:TriZPUG at python.org
26. https://mail.python.org/mailman/listinfo/trizpug
27. http://tripython.org/
28. mailto:cbc at unc.edu
29. mailto:cbc at unc.edu
30. mailto:cbc at unc.edu
31. mailto:TriZPUG at python.org
32. https://mail.python.org/mailman/listinfo/trizpug
33. http://tripython.org/
34. mailto:tobias at caktusgroup.com
35. mailto:trizpug at python.org
36. mailto:tobias at caktusgroup.com
37. http://www.caktusgroup.com/
38. mailto:andylpk247 at gmail.com
39. mailto:cbc at unc.edu
40. mailto:cbc at unc.edu
41. mailto:cbc at unc.edu
42. mailto:TriZPUG at python.org
43. https://mail.python.org/mailman/listinfo/trizpug
44. http://tripython.org/
45. mailto:cbc at unc.edu
46. mailto:cbc at unc.edu
47. mailto:cbc at unc.edu
48. mailto:TriZPUG at python.org
49. https://mail.python.org/mailman/listinfo/trizpug
50. http://tripython.org/
51. mailto:TriZPUG at python.org
52. https://mail.python.org/mailman/listinfo/trizpug
53. http://tripython.org/
54. mailto:tobias at caktusgroup.com
55. http://www.caktusgroup.com/
56. mailto:andylpk247 at gmail.com
57. mailto:cbc at unc.edu
58. mailto:cbc at unc.edu
59. mailto:cbc at unc.edu
60. mailto:TriZPUG at python.org
61. https://mail.python.org/mailman/listinfo/trizpug
62. http://tripython.org/
63. mailto:cbc at unc.edu
64. mailto:cbc at unc.edu
65. mailto:cbc at unc.edu
66. mailto:TriZPUG at python.org
67. https://mail.python.org/mailman/listinfo/trizpug
68. http://tripython.org/
69. mailto:TriZPUG at python.org
70. https://mail.python.org/mailman/listinfo/trizpug
71. http://tripython.org/
72. mailto:TriZPUG at python.org
73. https://mail.python.org/mailman/listinfo/trizpug
74. http://tripython.org/
75. mailto:rexadwyer at gmail.com
76. mailto:trizpug-request at python.org
77. mailto:trizpug at python.org
78. https://mail.python.org/mailman/listinfo/trizpug
79. mailto:trizpug-request at python.org
80. mailto:trizpug-owner at python.org
81. mailto:cbc at unc.edu
82. mailto:trizpug at python.org
83. mailto:cbc at unc.edu
84. mailto:cbc at unc.edu
85. mailto:andylpk247 at gmail.com
86. mailto:trizpug at python.org
87. mailto:cbc at unc.edu
88. mailto:cbc at unc.edu
89. mailto:cbc at unc.edu
90. mailto:TriZPUG at python.org
91. https://mail.python.org/mailman/listinfo/trizpug
92. http://tripython.org/
93. mailto:cbc at unc.edu
94. mailto:cbc at unc.edu
95. mailto:cbc at unc.edu
96. mailto:TriZPUG at python.org
97. https://mail.python.org/mailman/listinfo/trizpug
98. http://tripython.org/
99. mailto:tobias at caktusgroup.com
100. mailto:trizpug at python.org
101. mailto:tobias at caktusgroup.com
102. http://www.caktusgroup.com/
103. mailto:andylpk247 at gmail.com
104. mailto:cbc at unc.edu
105. mailto:cbc at unc.edu
106. mailto:cbc at unc.edu
107. mailto:TriZPUG at python.org
108. https://mail.python.org/mailman/listinfo/trizpug
109. http://tripython.org/
110. mailto:cbc at unc.edu
111. mailto:cbc at unc.edu
112. mailto:cbc at unc.edu
113. mailto:TriZPUG at python.org
114. https://mail.python.org/mailman/listinfo/trizpug
115. http://tripython.org/
116. mailto:TriZPUG at python.org
117. https://mail.python.org/mailman/listinfo/trizpug
118. http://tripython.org/
119. mailto:tobias at caktusgroup.com
120. http://www.caktusgroup.com/
121. mailto:andylpk247 at gmail.com
122. mailto:cbc at unc.edu
123. mailto:cbc at unc.edu
124. mailto:cbc at unc.edu
125. mailto:TriZPUG at python.org
126. https://mail.python.org/mailman/listinfo/trizpug
127. http://tripython.org/
128. mailto:cbc at unc.edu
129. mailto:cbc at unc.edu
130. mailto:cbc at unc.edu
131. mailto:TriZPUG at python.org
132. https://mail.python.org/mailman/listinfo/trizpug
133. http://tripython.org/
134. mailto:TriZPUG at python.org
135. https://mail.python.org/mailman/listinfo/trizpug
136. http://tripython.org/
137. mailto:TriZPUG at python.org
138. https://mail.python.org/mailman/listinfo/trizpug
139. http://tripython.org/
140. mailto:TriZPUG at python.org
141. https://mail.python.org/mailman/listinfo/trizpug
142. http://tripython.org/
143. mailto:trizpug-request at python.org
144. mailto:trizpug at python.org
145. https://mail.python.org/mailman/listinfo/trizpug
146. mailto:trizpug-request at python.org
147. mailto:trizpug-owner at python.org
148. mailto:rexadwyer at gmail.com
149. mailto:trizpug at python.org
150. mailto:rexadwyer at gmail.com
151. mailto:trizpug-request at python.org
152. mailto:trizpug at python.org
153. https://mail.python.org/mailman/listinfo/trizpug
154. mailto:trizpug-request at python.org
155. mailto:trizpug-owner at python.org
156. mailto:cbc at unc.edu
157. mailto:trizpug at python.org
158. mailto:cbc at unc.edu
159. mailto:cbc at unc.edu
160. mailto:andylpk247 at gmail.com
161. mailto:trizpug at python.org
162. mailto:cbc at unc.edu
163. mailto:cbc at unc.edu
164. mailto:cbc at unc.edu
165. mailto:TriZPUG at python.org
166. https://mail.python.org/mailman/listinfo/trizpug
167. http://tripython.org/
168. mailto:cbc at unc.edu
169. mailto:cbc at unc.edu
170. mailto:cbc at unc.edu
171. mailto:TriZPUG at python.org
172. https://mail.python.org/mailman/listinfo/trizpug
173. http://tripython.org/
174. mailto:tobias at caktusgroup.com
175. mailto:trizpug at python.org
176. mailto:tobias at caktusgroup.com
177. http://www.caktusgroup.com/
178. mailto:andylpk247 at gmail.com
179. mailto:cbc at unc.edu
180. mailto:cbc at unc.edu
181. mailto:cbc at unc.edu
182. mailto:TriZPUG at python.org
183. https://mail.python.org/mailman/listinfo/trizpug
184. http://tripython.org/
185. mailto:cbc at unc.edu
186. mailto:cbc at unc.edu
187. mailto:cbc at unc.edu
188. mailto:TriZPUG at python.org
189. https://mail.python.org/mailman/listinfo/trizpug
190. http://tripython.org/
191. mailto:TriZPUG at python.org
192. https://mail.python.org/mailman/listinfo/trizpug
193. http://tripython.org/
194. mailto:tobias at caktusgroup.com
195. http://www.caktusgroup.com/
196. mailto:andylpk247 at gmail.com
197. mailto:cbc at unc.edu
198. mailto:cbc at unc.edu
199. mailto:cbc at unc.edu
200. mailto:TriZPUG at python.org
201. https://mail.python.org/mailman/listinfo/trizpug
202. http://tripython.org/
203. mailto:cbc at unc.edu
204. mailto:cbc at unc.edu
205. mailto:cbc at unc.edu
206. mailto:TriZPUG at python.org
207. https://mail.python.org/mailman/listinfo/trizpug
208. http://tripython.org/
209. mailto:TriZPUG at python.org
210. https://mail.python.org/mailman/listinfo/trizpug
211. http://tripython.org/
212. mailto:TriZPUG at python.org
213. https://mail.python.org/mailman/listinfo/trizpug
214. http://tripython.org/
215. mailto:rexadwyer at gmail.com
216. mailto:trizpug-request at python.org
217. mailto:trizpug at python.org
218. https://mail.python.org/mailman/listinfo/trizpug
219. mailto:trizpug-request at python.org
220. mailto:trizpug-owner at python.org
221. mailto:cbc at unc.edu
222. mailto:trizpug at python.org
223. mailto:cbc at unc.edu
224. mailto:cbc at unc.edu
225. mailto:andylpk247 at gmail.com
226. mailto:trizpug at python.org
227. mailto:cbc at unc.edu
228. mailto:cbc at unc.edu
229. mailto:cbc at unc.edu
230. mailto:TriZPUG at python.org
231. https://mail.python.org/mailman/listinfo/trizpug
232. http://tripython.org/
233. mailto:cbc at unc.edu
234. mailto:cbc at unc.edu
235. mailto:cbc at unc.edu
236. mailto:TriZPUG at python.org
237. https://mail.python.org/mailman/listinfo/trizpug
238. http://tripython.org/
239. mailto:tobias at caktusgroup.com
240. mailto:trizpug at python.org
241. mailto:tobias at caktusgroup.com
242. http://www.caktusgroup.com/
243. mailto:andylpk247 at gmail.com
244. mailto:cbc at unc.edu
245. mailto:cbc at unc.edu
246. mailto:cbc at unc.edu
247. mailto:TriZPUG at python.org
248. https://mail.python.org/mailman/listinfo/trizpug
249. http://tripython.org/
250. mailto:cbc at unc.edu
251. mailto:cbc at unc.edu
252. mailto:cbc at unc.edu
253. mailto:TriZPUG at python.org
254. https://mail.python.org/mailman/listinfo/trizpug
255. http://tripython.org/
256. mailto:TriZPUG at python.org
257. https://mail.python.org/mailman/listinfo/trizpug
258. http://tripython.org/
259. mailto:tobias at caktusgroup.com
260. http://www.caktusgroup.com/
261. mailto:andylpk247 at gmail.com
262. mailto:cbc at unc.edu
263. mailto:cbc at unc.edu
264. mailto:cbc at unc.edu
265. mailto:TriZPUG at python.org
266. https://mail.python.org/mailman/listinfo/trizpug
267. http://tripython.org/
268. mailto:cbc at unc.edu
269. mailto:cbc at unc.edu
270. mailto:cbc at unc.edu
271. mailto:TriZPUG at python.org
272. https://mail.python.org/mailman/listinfo/trizpug
273. http://tripython.org/
274. mailto:TriZPUG at python.org
275. https://mail.python.org/mailman/listinfo/trizpug
276. http://tripython.org/
277. mailto:TriZPUG at python.org
278. https://mail.python.org/mailman/listinfo/trizpug
279. http://tripython.org/
280. mailto:TriZPUG at python.org
281. https://mail.python.org/mailman/listinfo/trizpug
282. http://tripython.org/
283. mailto:TriZPUG at python.org
284. https://mail.python.org/mailman/listinfo/trizpug
285. http://tripython.org/
More information about the TriZPUG
mailing list