TGTGInsighttelegram intelligenceLIVE / telegram public index
← GZ学习频道

TGINSIGHT SIMILAR POSTS

Find similar content

Source channel @olddriverGDstudy · Post #29 · Mar 17

搜索使用说明 #搜索指南 因为电报软件对中文搜索支持不好,大队特别对队内资源搜索进行了整理汇集,使用方法说明如下: 1.1 原理: 电报对中文搜索支持不佳,汉字只有在前后含有asic码字符的前提下可以被正确搜索出,如 _广州修车大队_ (“_”指代空格)、(广州修车大队);等形式可以搜索“广州修车大队”搜索出相关信息;搜索“广州”等未被asic码间隔的汉字无法正确显示。 为正确搜索,在编制频道资源时,对重要信息可以采取Hashtag的形式已方便搜索,即以"#"字符开头,接汉字,以“空格字符”结尾的形式,点击一个hashtag即可快速定位该频道或聊天群内所有相同标签,建议所有管理在编辑重要资料包括ls信息、广播台、学习频道时正确使用hashtag。 !!注意标签不要随意编写,要参考搜索指南中有的标签类型!! 1.2 JS资源定位: JS目前支持 Hasgtag(#K老师)、数字标签(#GZ003)的搜索方式,在对应榜单和报告区中试用上述方式均可查找到JS的相关信息。 使用举例:在“广州公开榜”或“广州修车大队”的搜索栏中输入 #K老师 或 #GZ003,均可定位到K老师资料页;在报告区的搜索栏中输入#K老师 或 #GZ003,均可定位到K老师的验证报告。这两者是快速了解JS基本信息和评价的便捷办法。 1.3 标签查找 公榜榜单目前均支持标签查找,可以快速定位某种类型或地区的所有JS,目前仅支持Hashtag查找,目前常用标签解释如下: 地区标签: 一定要使用一级标签,例如 #天河区(注意不要有错别字) #颜值: 不解释 #服务: 评价中92、95的,有场子出身花式水平的,均会归入此类; #大胸: 不解释,一般D以上归入此类; #长腿: 不解释,一般168以上归入此类; #身材: 不解释,较为宽松; #嫩妹: 22岁以下或者长相很嫩的,白小纯的,loli系的,cos系的归入此类; #熟女: 30岁以上风韵犹存的,归入此类; #特服: 提供3p、3t、wt、字母等特殊服务的JS归入此类。 使用举例:在红榜的搜索栏中输入 #长腿,可以快速查看“莉贝伦”等8位长腿JS。 类型标签评价目前非常主观,有不妥之处请队内私信 JackJack 或其他管理人员修改。 1.4 资料查找 目前学习频道中试用hashtag来快速定位资料,目前使用的标签有如下几种: #安全CJ#素质CJ#卫生CJ #搜索指南 #大队玩法 #语录#秀哥语录 #技巧#知识

Results

6 similar posts found

Search: #cpython

当前筛选 #cpython清除筛选
djangoproject

@djangoproject · Post #131 · 09/01/2016, 03:27 AM

http://www.lfd.uci.edu/~gohlke/pythonlibs/ This page provides 32- and 64-bit Windows binaries of many scientific open-source extension #packages for the official #CPython distribution of the #Python programming language. The files are unofficial (meaning: informal, unrecognized, personal, unsupported, no warranty, no liability, provided "as is") and made available for testing and evaluation purposes.

djangoproject

@djangoproject · Post #164 · 09/17/2016, 10:20 AM

https://www.buzzfeed.com/andrewkelleher/deep-exploration-into-python-lets-review-the-dict-module?utm_term=.rhDeZBxA8#.bgB5DM0Z9 In this series, we’ll take a look at various modules and pieces of functionality of the #Python language. We’ll look at design choices, their impact, and their evolution. We’ll also look at the design of the language itself and learn about the operations of the interpreter as it parses the language all the way to the main eval loop. Finally, we’ll attempt to give practical takeaways that fall out of a deeper understanding of the language. The #cpython implementation of Python (which is the standard on most machines) has been ported over to GitHub from its home in Mercurial. I think it also had a time under #SVN, but the engineers managed to preserve (for the most part) the commit logs.

AIGC

@aigcrubbish · Post #6 · 08/23/2024, 06:57 AM

CPython zipfile 模块高危漏洞 CVE-2024-8088 CPython 的 zipfile 模块存在一个高危漏洞,编号为 CVE-2024-8088。该漏洞会导致在处理恶意构造的 zip 档案时,程序陷入无限循环。具体来说,当使用 zipfile.Path 类及其方法(如 namelist()`、`iterdir()`、`extractall() 等)遍历 zip 档案条目名称时,可能会触发无限循环。 此漏洞的根本原因在于 zipfile._path._ancestry() 方法中的路径处理不当。具体来说,代码中的 path.rstrip(posixpath.sep) 和 while 循环条件未正确处理路径,导致无限循环。例如,`posixpath.split("//") 返回 ("//", ""),而 "//" != posixpath.sep` 导致循环无法退出。 该漏洞已被修复,建议更新 CPython 并加强输入验证,以防止潜在的拒绝服务攻击。 原文链接:https://www.openwall.com/lists/oss-security/2024/08/22/1https://www.openwall.com/lists/oss-security/2024/08/22/4 标签:#CPython#漏洞#zipfile#无限循环 #AIGC

djangoproject

@djangoproject · Post #156 · 09/06/2016, 01:43 AM

https://wiki.python.org/moin/GlobalInterpreterLock In #CPython, the #global#interpreter lock, or #GIL, is a mutex that prevents multiple native #threads from executing Python bytecodes at once. This lock is necessary mainly because CPython's memory management is not thread-safe. (However, since the GIL exists, other features have grown to depend on the guarantees that it enforces.)

djangoproject

@djangoproject · Post #551 · 01/23/2018, 04:28 PM

http://lxml.de/ #lxml is the most feature-rich and easy-to-use library for processing #XML and #HTML in the Python language. The lxml XML toolkit is a Pythonic binding for the #C libraries #libxml2 and #libxslt. It is unique in that it combines the speed and XML feature completeness of these libraries with the simplicity of a native Python #API, mostly compatible but superior to the well-known ElementTree API. The latest release works with all #CPython versions from 2.6 to 3.6. See the introduction for more information about background and goals of the lxml project. Some common questions are answered in the FAQ.

djangoproject

@djangoproject · Post #523 · 12/13/2017, 08:27 PM

http://www.jaggedverge.com/2017/11/how-a-web-page-request-makes-it-down-to-the-metal/ How a web page request makes it down to the metal by : Janis Posted in : Tutorials, work-in-progess Tags : #NGINX, #Python No Comments The other day I was interested in how many steps occur between sending a #POST or #GET#request from a website to the actual processing that happens on the CPU of the #server. I figured that I knew bits and pieces of the puzzle but I wanted to see the complete path from the highest levels of abstraction all the way to the lowest without missing anything too big in-between. It turns out that in a modern web system there are a lot of steps. I have been really fascinated by this much like the explorer that wants to find a path from one known place to another. If you are interested in better understanding how your computer works you might find walking along this path with your tech stack helpful. Frontend prelude: GET request Browser page #rendering POST request sidenote: #CSRF#token Network stack sidenote: The Internet #TCP sidenote: more comprehensive treatment of network stack Backend Handling web request #WSGI #Django Django URL routing Django views Python implementations #CPython CPython bytecode CPython bytecode execution details Machine Code CPython to machine code Machine code execution Hardware implementation details Microcode Processor #pipeline Silicon implementation of addition Silicon adder unit AND gate Transistor