
GITHUB . COM {
}
Detected CMS Systems:
- Wordpress (2 occurrences)
Title:
[BUG] setuptools 75.7.0 and CFLAGS Β· Issue #4836 Β· pypa/setuptools
Description:
setuptools version 75.7.0 Python version 3.12.8 OS ALTLinux Additional environment information No response Description With pypa/distutils#299 (merged to setuptools 75.7.0) the CFLAGS behavior changed. Docs are not updated to that change...
Website Age:
17 years and 9 months (reg. 2007-10-09).
Matching Content Categories {π}
- Technology & Computing
- Environment
- Non-Profit & Charity
Content Management System {π}
What CMS is github.com built with?
Github.com is based on WORDPRESS.
Traffic Estimate {π}
What is the average monthly size of github.com audience?
ππ Tremendous Traffic: 10M - 20M visitors per month
Based on our best estimate, this website will receive around 10,000,019 visitors per month in the current month.
However, some sources were not loaded, we suggest to reload the page to get complete results.
check SE Ranking
check Ahrefs
check Similarweb
check Ubersuggest
check Semrush
How Does Github.com Make Money? {πΈ}
Subscription Packages {π³}
We've located a dedicated page on github.com that might include details about subscription plans or recurring payments. We identified it based on the word pricing in one of its internal links. Below, you'll find additional estimates for its monthly recurring revenues.How Much Does Github.com Make? {π°}
Subscription Packages {π³}
Prices on github.com are in US Dollars ($).
They range from $4.00/month to $21.00/month.
We estimate that the site has approximately 5,013,426 paying customers.
The estimated monthly recurring revenue (MRR) is $21,056,387.
The estimated annual recurring revenues (ARR) are $252,676,649.
Wordpress Themes and Plugins {π¨}
What WordPress theme does this site use?
It is strange but we were not able to detect any theme on the page.
What WordPress plugins does this website use?
It is strange but we were not able to detect any plugins on the page.
Keywords {π}
cflags, setuptools, change, build, thesamesam, bug, stanislavlevin, additional, docs, options, flags, cpython, code, projects, issue, python, behavior, compiler, append, commented, sign, changed, distutils, update, happened, mypy, buggy, issues, closed, environment, variable, overrides, supply, added, status, contributor, completely, wasnt, possibly, building, commit, elischwartz, default, built, dndebug, bad, thing, personal, experience, reflect,
Topics {βοΈ}
io/en/latest/userguide/ext_modules access cpersistentobject refcounts eli-schwartz edits contributor sysconfig variable cflags thesamesam edits contributor supply additional flags c9acd9a cjwatson mentioned update cflags docs bug projects reflect distutils change check buggy code pass additional flags setuptools change made personal subjective experience environment variables cflags ${cflags} -fwhatever-i hardcodes/calcifies cflags cc people relevant misguided report based assume good faith extensive experience packaging avoiding unexpected behaviour allowing python packages comment metadata assignees triage issues projects milestone commit message consistency python packages building buggy code setuptools change cflags behavior changed response description bug reports default iff pass cflags= sysconfig cflags specific project compiler flags behavior change cxxflags possibly change set cflags behaviour matches bug linker-options options provided options passed issue python ecosystem building cpython
Payment Methods {π}
- Braintree
Questions {β}
- Already have an account?
- It's completely possible to supply additional flags?
Schema {πΊοΈ}
DiscussionForumPosting:
context:https://schema.org
headline:[BUG] setuptools 75.7.0 and CFLAGS
articleBody:### setuptools version
75.7.0
### Python version
3.12.8
### OS
ALTLinux
### Additional environment information
_No response_
### Description
With https://github.com/pypa/distutils/issues/299 (merged to `setuptools` `75.7.0`) the `CFLAGS` behavior changed.
Docs are not updated to that change and describe the previous state.
https://setuptools.pypa.io/en/latest/userguide/ext_modules.html#compiler-and-linker-options
> The compiler options appear in the command line in the following order:
> - first, the options provided by the sysconfig variable CFLAGS,
> - then, the options provided by the environment variables CFLAGS and CPPFLAGS,
This is the behavior used for RPM build for long time. `CFLAGS` was/is used to append additional distro-specific options to the `CPython`'s ones.
After the aforementioned change `CFLAGS` env variable overrides `sysconfig`s `CFLAGS` and it's no longer possible to supply additional flags.
So it's a behavior change.
### Expected behavior
There should be a way to pass `additional` flags for compilers according to documentation.
### How to Reproduce
Try to build an extension with `CFLAGS` and without to see the difference in compiler flags.
### Output
```console
```
author:
url:https://github.com/stanislavlevin
type:Person
name:stanislavlevin
datePublished:2025-02-18T11:36:58.000Z
interactionStatistic:
type:InteractionCounter
interactionType:https://schema.org/CommentAction
userInteractionCount:17
url:https://github.com/4836/setuptools/issues/4836
context:https://schema.org
headline:[BUG] setuptools 75.7.0 and CFLAGS
articleBody:### setuptools version
75.7.0
### Python version
3.12.8
### OS
ALTLinux
### Additional environment information
_No response_
### Description
With https://github.com/pypa/distutils/issues/299 (merged to `setuptools` `75.7.0`) the `CFLAGS` behavior changed.
Docs are not updated to that change and describe the previous state.
https://setuptools.pypa.io/en/latest/userguide/ext_modules.html#compiler-and-linker-options
> The compiler options appear in the command line in the following order:
> - first, the options provided by the sysconfig variable CFLAGS,
> - then, the options provided by the environment variables CFLAGS and CPPFLAGS,
This is the behavior used for RPM build for long time. `CFLAGS` was/is used to append additional distro-specific options to the `CPython`'s ones.
After the aforementioned change `CFLAGS` env variable overrides `sysconfig`s `CFLAGS` and it's no longer possible to supply additional flags.
So it's a behavior change.
### Expected behavior
There should be a way to pass `additional` flags for compilers according to documentation.
### How to Reproduce
Try to build an extension with `CFLAGS` and without to see the difference in compiler flags.
### Output
```console
```
author:
url:https://github.com/stanislavlevin
type:Person
name:stanislavlevin
datePublished:2025-02-18T11:36:58.000Z
interactionStatistic:
type:InteractionCounter
interactionType:https://schema.org/CommentAction
userInteractionCount:17
url:https://github.com/4836/setuptools/issues/4836
Person:
url:https://github.com/stanislavlevin
name:stanislavlevin
url:https://github.com/stanislavlevin
name:stanislavlevin
InteractionCounter:
interactionType:https://schema.org/CommentAction
userInteractionCount:17
interactionType:https://schema.org/CommentAction
userInteractionCount:17
External Links {π}(3)
Analytics and Tracking {π}
- Site Verification - Google
Libraries {π}
- Clipboard.js
- D3.js
- GSAP
- Lodash
Emails and Hosting {βοΈ}
Mail Servers:
- aspmx.l.google.com
- alt1.aspmx.l.google.com
- alt2.aspmx.l.google.com
- alt3.aspmx.l.google.com
- alt4.aspmx.l.google.com
Name Servers:
- dns1.p08.nsone.net
- dns2.p08.nsone.net
- dns3.p08.nsone.net
- dns4.p08.nsone.net
- ns-1283.awsdns-32.org
- ns-1707.awsdns-21.co.uk
- ns-421.awsdns-52.com
- ns-520.awsdns-01.net