Wala shell

Advanced PHP File Manager

Server IP: 127.0.0.1 | PHP Version: 8.3.30 | Domains Hosted: 54

Name	Size	Last Modified	Actions
📁 ..	-	2024-10-09 06:13
📄 faq.rst Frequently asked questions =========================== Is UTF-8 everywhere already? ---------------------------- Not really, that is a dangerous assumption. Looking at https://w3techs.com/technologies/overview/character_encoding may seem like encoding detection is a thing of the past but not really. Solo based on 33k websites, you will find 3,4k responses without predefined encoding. 1,8k websites were not UTF-8, merely half! This statistic (w3techs) does not offer any ponderation, so one should not read it as "I have a 97 % chance of hitting UTF-8 content on HTML content". (2021 Top 1000 sites from 80 countries in the world according to Data for SEO) https://github.com/potiuk/test-charset-normalizer First of all, neither requests, chardet or charset-normalizer are dedicated to HTML content. The detection concern every text document, like SubRip Subtitle files for instance. And by my own experiences, I never had a single database using full utf-8, many translated subtitles are from another era and never updated. It is so hard to find any stats at all regarding this matter. Users' usages can be very dispersed, so making assumptions are unwise. The real debate is to state if the detection is an HTTP client matter or not. That is more complicated and not my field. Some individuals keep insisting that the whole Internet is UTF-8 ready. Those are absolutely wrong and very Europe and North America-centered, In my humble experience, the countries in the world are very disparate in this evolution. And the Internet is not just about HTML content. Having a thorough analysis of this is very scary. Should I bother using detection? -------------------------------- In the last resort, yes. You should use well-established standards, eg. predefined encoding, at all times. When you are left with no clue, you may use the detector to produce a usable output as fast as possible. Is it backward-compatible with Chardet? --------------------------------------- If you use the legacy `detect` function, Then this change is mostly backward-compatible, exception of a thing: - This new library support way more code pages (x3) than its counterpart Chardet. - Based on the 30-ich charsets that Chardet support, expect roughly 80% BC results We do not guarantee this BC exact percentage through time. May vary but not by much. Isn't it the same as Chardet? ----------------------------- The objective is the same, provide you with the best answer (charset) we can given any sequence of bytes. The method actually differs. We do not "train" anything to build a probe for a specific encoding. In addition to finding any languages (intelligent design) by some rudimentary statistics (character frequency ordering) we built a mess detector to assist the language detection. Any code page supported by your cPython is supported by charset-normalizer! It is that simple, no need to update the library. It is as generic as we could do. I can't build standalone executable ----------------------------------- If you are using ``pyinstaller``, ``py2exe`` or alike, you may be encountering this or close to: ModuleNotFoundError: No module named 'charset_normalizer.md__mypyc' Why? - Your package manager picked up a optimized (for speed purposes) wheel that match your architecture and operating system. - Finally, the module ``charset_normalizer.md__mypyc`` is imported via binaries and can't be seen using your tool. How to remedy? If your bundler program support it, set up a hook that implicitly import the hidden module. Otherwise, follow the guide on how to install the vanilla version of this package. (Section: Optional speedup extension)	3.59 KB	2024-10-09 06:13
📄 featured.rst Featured projects ================= Did you liked how ``charset-normalizer`` perform? and its quality? You may be interested in those other project maintained by the same authors. We aim to serve the opensource community the best and as inclusively as we can, no matter your level or opinions. Niquests -------- Started as a simple though.. IE 11 has built-in HTTP/2 support while Requests 2.32 does not! Most of our programs that interact with HTTP server are built with ``requests`` and we aren't likely to switch without a substantial effort. We just might die at any moment, no notice whatsoever, knowingly that as a Python developer, we never interacted with a HTTP/2 over TCP or HTTP/3 over QUIC capable server in 2023... .. image:: https://dabuttonfactory.com/button.png?t=Get+Niquests+Now&f=Ubuntu-Bold&ts=26&tc=fff&hp=45&vp=20&c=11&bgt=unicolored&bgc=15d798&be=1 :target: https://github.com/jawah/niquests It is a fork of ``requests`` and no breaking changes are to be expected. We made sure that your migration is effortless and safe. httpie-next ----------- Easy solution are cool, let us introduce you to HTTPie but with built-in support for HTTP/2 and HTTP/3. It is made available as a plugin, no effort required beside installing the said plugin. Enjoy HTTPie refreshed! .. image:: https://dabuttonfactory.com/button.png?t=Get+HTTPie-Next+Now&f=Ubuntu-Bold&ts=26&tc=fff&hp=45&vp=20&c=11&bgt=unicolored&bgc=15d798&be=1 :target: https://github.com/Ousret/httpie-next Wassima ------- Did you ever wonder how would it feel like to leave the headache with root CAs (certificate authority)? Well, you may, starting today, use your operating system trusted root CAs to verify peer certificates with the at most comfort. It is enabled by default in Niquests, but you can use that awesome feature by itself. .. image:: https://dabuttonfactory.com/button.png?t=OS+root+CAs+for+Python&f=Ubuntu-Bold&ts=26&tc=fff&hp=45&vp=20&c=11&bgt=unicolored&bgc=15d798&be=1 :target: https://github.com/jawah/wassima The solution is universal and served for (almost) every possible case. You may remove the certifi package, let it rest in peace.	2.11 KB	2024-10-09 06:13
📄 speedup.rst Optional speedup extension ========================== Why? ---- charset-normalizer will always remain pure Python, meaning that a environment without any build capabilities will run this program without any additional requirements. Nonetheless, starting from the version 3.0 we introduce and publish some platform specific wheels including a pre-built extension. Most of the time is spent in the module `md.py` so we decided to "compile it" using Mypyc. (1) It does not require to have a separate code base (2) Our project code base is rather simple and lightweight (3) Mypyc is robust enough today (4) Four times faster! How? ---- If your platform and/or architecture is not served by this swift optimization you may compile it easily yourself. Following those instructions (provided you have the necessary toolchain installed): :: export CHARSET_NORMALIZER_USE_MYPYC=1 pip install mypy build wheel pip install charset-normalizer --no-binary :all: How not to? ----------- You may install charset-normalizer without the speedups by directly using the universal wheel (most likely hosted on PyPI or any valid mirror you use) with ``--no-binary``. E.g. when installing ``requests`` and you don't want to use the ``charset-normalizer`` speedups, you can do: :: pip install requests --no-binary charset-normalizer When installing `charset-normalizer` by itself, you can also pass ``:all:`` as the specifier to ``--no-binary``. :: pip install charset-normalizer --no-binary :all:	1.48 KB	2024-10-09 06:13
📄 why_migrate.rst Why should I migrate to Charset-Normalizer? =========================================== There is so many reason to migrate your current project. Here are some of them: - Remove ANY license ambiguity/restriction for projects bundling Chardet (even indirectly). - X10 faster than Chardet in average and X6 faster in 99% of the cases AND support 3 times more encoding. - Never return a encoding if not suited for the given decoder. Eg. Never get UnicodeDecodeError! - Actively maintained, open to contributors. - Have the backward compatible function ``detect`` that come from Chardet. - Truly detect the language used in the text. - It is, for the first time, really universal! As there is no specific probe per charset. - The package size is X2~X4 lower than Chardet's (5.0)! (Depends on your arch) - Propose much more options/public kwargs to tweak the detection as you sees fit! - Using static typing to ease your development. - Detect Unicode content better than Chardet or cChardet does. And much more..! What are you waiting for? Upgrade now and give us a feedback. (Even if negative)	1.07 KB	2024-10-09 06:13

Terminal