RequestHunt is a community-driven platform that collects and curates feature requests from X (Twitter), Reddit, and GitHub. We help product teams discover what features real users are asking for, making it easier to validate product ideas and prioritize feature development based on actual user demand.

How does RequestHunt collect feature requests?

RequestHunt uses AI-powered extraction to automatically collect feature requests from social media platforms including X, Reddit, and GitHub. The platform monitors discussions, issues, and posts to identify genuine user feature requests, extracting key information like the requested feature, product mentioned, and user sentiment.

Who uses RequestHunt?

RequestHunt is used by product managers, founders, developers, and product teams who want to discover what features real users are requesting. It's particularly valuable for startups looking to validate ideas, established companies prioritizing their roadmap, and developers building products that solve real user problems.

Is RequestHunt free to use?

Yes, browsing and searching feature requests on RequestHunt is completely free. We also offer API access for developers who want to integrate feature request data into their own applications. Check our pricing page for API plan details.

How often is RequestHunt data updated?

RequestHunt continuously collects feature requests from Reddit, X (Twitter), and GitHub. You can also trigger on-demand scraping via the API or web interface to get the freshest data for any topic.

[Freezegun] Allow timezone differences for frozen datetime.now() and utcnow()

The user expects datetime.now() and datetime.utcnow() to reflect different timezones even when time is frozen by Freezegun, similar to their behavior without Freezegun. They believe the current behavior of returning the exact same frozen time for both is not ideal.

Original Source

@@homeworkprod | 11 pts | 3/9/2015

Excerpt from the docs: "[…] all calls to `datetime.datetime.now()`, `datetime.datetime.utcnow()`, […] will return the time that has been frozen." But this is not the behaviour I expect. Example code: ``` python from datetime import datetime def test_something(): print('now(): ', datetime.now()) print('utcnow():', datetime.utcnow()) ``` Output without Freezegun (system timezone is "Europe/Berlin"): ``` now(): 2015-03-10 00:46:40.465879 utcnow(): 2015-03-09 23:46:40.466031 ``` Output with Freezegun (method decorated with `@freeze_time('2012-03-11 19:21:23')`): ``` now(): 2012-03-11 19:21:23 utcnow(): 2012-03-11 19:21:23 ``` However, I expected the output with Freezegun to reflect the offset (one hour, in this case) and, thus, to return two different date/time instances.

Discussion

Loading comments...