HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
imageworks
pystring
C++2016–2024
imageworks / pystring

pystring

C++ functions matching the interface and behavior of python string methods with std::string

3Distinct people
7Mentions
0Explicit recommenders
1.1KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

C++ functions matching the interface and behavior of python string methods with std::string

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 11:56:56 AM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year7 dated mentions

Observed mentions: 2016-02-15 12:26:13 UTC to 2024-05-15 09:22:20 UTC.

0122016-01-01 00:00:00 UTC to 2017-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments20162017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 2 mentions; 1 submissions, 1 comments2020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments20202021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2024

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20162016-01-01 00:00:00 UTC2017-01-01 00:00:00 UTC101
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC000
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC000
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC211
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC000
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC101
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC000
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC202
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC101

What Hacker News says

7 sources
pystring [1] is such a "finished" project, they even have a note in the readme that the project is not dead (I guess they got a lot of such questions too). It's a small yet complete library with a very narrow focus, so there really is nothing to change once it's done (and despite that recently merged CI pipeline having failed on macOS for some reason, it works just fine there, I make heavy use of pystring in one my projects across Windows, macOS and Linux). Quote: "Note: Despite the infrequent updates, this repo is not dead/abandoned - just stable! We use it every day at Imageworks." [1] https://github.com/imageworks/pystring
In "Is This Project Still Maintained?"
I like C much more than C++, but even with that must say that https://github.com/fmtlib/fmt is pretty nice (which is the base for std::format). Together with pystring (https://github.com/imageworks/pystring) it makes string processing in C++ somewhat bearable (pystring is slow though because it still uses the std::string type which excessively allocates, but at least it's convenient compared to 'raw' C++ string functionality).
In For processing strings, streams in C++ can be slow
> When I look at C++14 and later I can't help but throw my hands up, Why C++14? The changes were very minor and mostly about being able to declare lambda functions with auto, which is extremely useful. > Waiting for Cross-Platform standardized SIMD vector datatypes I only know of ISPC having this, but there are also lots of SIMD libraries for C++ that are small and have minimal dependencies. > Using nonstandard extensions, libraries or home-baked solutions to run computations in parallel on many cores or on different processors than the CPU std::thread, atomics, and mutexes were added in C++11 and work extremely well. OpenMP is in the top four compilers if someone wants super easy fork-join parallelism. What other languages make C++ look archaic here? > Debugging cross-platform code using couts, cerrs and printfs Both visual studio and Q
Read the rest
t Creator have made this unnecessary for a long time (if you can do step through debugging). What other language are you thinking of that makes C++ look archaic here? > Forced to use boost for even quite elementary operations on std::strings. That's completely ridiculous. It is easy to avoid boost these days (thank god). This is DEFINITELY not worth using boost for. First you can use https://github.com/imageworks/pystring on top of what C++ already has combined with regular expressions. I don't think anything you listed is actually a problem. If you had talked about not having a standard networking library or standard serialization it might have made more sense.
In All C++20 core language features with examples
Interesting side note: https://github.com/fmtlib/fmt of the same author has been aded to the C++20 standard. One of the few inclusions into the standard which (IMHO) can be universally considered to be a good thing. If you're coming from printf() or iostreams, fmtlib is a joy to use, especially together with pystring (https://github.com/imageworks/pystring). Both libs don't fix the underlying problems of std::string, but at least they reduce the pain of working with strings in C++ considerably.
In Reducing printf call overhead with variadic templates

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.