Skip to content

wechaty/python-wechaty-getting-started

View on GitHub ↗Related repositories →

mine Python Wechaty Starter Project Template that Works Out-of-the-Box

active 2023-08-292025-04-13 (UTC)

Complete coverage26,346 / 26,346 hourly files (100%) · 2 absent upstream2023-08-152026-08-16 (UTC)
Events
70
Pushes
0
Pull requests
0
Issues
9
Stars
43
Forks
8

Activity over time

Daily event counts in the loaded window

Line chart, 594 days from 2023-08-29 to 2025-04-13. Pushes: 0 total, peak 0 in a day. Pull requests: 0 total, peak 0 in a day. Issues: 9 total, peak 2 in a day. Comments: 10 total, peak 1 in a day. Stars: 43 total, peak 2 in a day.

  • Pushes
  • Pull requests
  • Issues
  • Comments
  • Stars

Stars, PRs, issues and forks are under-captured in the later part of this window. GH Archive progressively stopped capturing non-push events during 2026 — −95% or worse by the end of the window. Every series here except Pushes fades for that reason, so a decline above reflects the archive, not this repository. Pushes stay reliable throughout, so read them, and the contributor counts derived from them, as the real signal. Data health has the measurements.

Top contributors

Pushes, PRs, issues, reviews and comments — stars and forks excluded, so this is contribution rather than popularity

ContributorContributionsPushesPRsComments
huan3001
mandxy2001
wenmj1001
aGVsZWk1001
Jicming1000
YuanKyL1000
cnarte1000
iKeepo1000
logiccao1001
lizihao0011001
shavingha1001
RolloTomasiii1000
jiaqianjing1001
suxiaobei10241000
Pengchengistaken1001
AurganicSubstance1001

Recent activity

Latest issues, pull requests and releases

  • Issue#99huan2024-11-28 22:05
    wechaty已死,需要iPad协议的微信API组件(稳定、功能多)联系我 wx: AIYLWL
  • Issue#99RolloTomasiii2024-11-28 06:18
    wechaty已死,需要iPad协议的微信API组件(稳定、功能多)联系我 wx: AIYLWL
  • Issue#98cnarte2024-05-25 07:06
    Whatsapp puppet support with python?
  • Issue comment#97huan2024-05-22 07:26
    【wechaty问题交流微信群】一起讨论,吐槽,解决wechaty中遇到的坑
  • Issue#97huan2024-05-22 07:26
    【wechaty问题交流微信群】一起讨论,吐槽,解决wechaty中遇到的坑
  • Issue#97suxiaobei10242024-05-22 04:19
    【wechaty问题交流微信群】一起讨论,吐槽,解决wechaty中遇到的坑
  • Issue#96YuanKyL2024-05-20 07:25
    给对应群聊发送消息还能发吗,为什么我不能发了
  • Issue comment#82wenmj2024-04-06 13:48
    连接失败
  • Issue comment#88lizihao0012024-03-12 10:00
    Wechaty - ERROR - internal error <>
  • Issue#95Jicming2024-01-16 09:53
    internal error
  • Issue comment#94AurganicSubstance2024-01-14 08:54
    运行bot py 报错can"t fetch endpoint from chatie server. You can try it later, or make sure that your pc can connect to heroku server
  • Issue comment#94aGVsZWk2023-12-19 09:20
    运行bot py 报错can"t fetch endpoint from chatie server. You can try it later, or make sure that your pc can connect to heroku server
  • Issue comment#77shavingha2023-11-30 06:31
    WechatyOptions.name设置的json文件在哪里?
  • Issue#94mandxy2023-10-31 11:45
    运行bot py 报错can"t fetch endpoint from chatie server. You can try it later, or make sure that your pc can connect to heroku server
  • Issue comment#86mandxy2023-10-31 10:53
    遇到问题:wechaty_puppet.exceptions.WechatyPuppetGrpcError: WechatyPuppetGrpcError('can"t fetch endpoint from chatie server. You can try it later, or make sure that your pc can connect to heroku server ', None, None)
  • Issue comment#86jiaqianjing2023-10-25 09:36
    遇到问题:wechaty_puppet.exceptions.WechatyPuppetGrpcError: WechatyPuppetGrpcError('can"t fetch endpoint from chatie server. You can try it later, or make sure that your pc can connect to heroku server ', None, None)
  • Issue comment#88Pengchengistaken2023-10-22 05:45
    Wechaty - ERROR - internal error <>
  • Issue#93iKeepo2023-10-11 06:27
    WechatyPuppetConfigurationError: WechatyPuppetConfigurationError("can't not ping endpoint: 116.233.2.210:8788", None, None)
  • Issue comment#86logiccao2023-09-15 03:11
    遇到问题:wechaty_puppet.exceptions.WechatyPuppetGrpcError: WechatyPuppetGrpcError('can"t fetch endpoint from chatie server. You can try it later, or make sure that your pc can connect to heroku server ', None, None)

Totals cover only the window loaded into ClickHouse and count events, not GitHub's lifetime totals — 43 stars here means stars gained during the window, not the repo's star count.