and the entire ecosystem of packages which needs to be maintained.

Unless you think that is done by magic fairy elves

Allude to Rust without saying Rust

Oh you mean MSFT is part of Alpha-Omega foundation and their money is not green.

tl;dr;

Alpha-Omega funds Seth Larson and Mike Fiedler. Alpha-Omega is big corp grants to open source projects, except yours. Never yours.

About Anthropic

Anthropic is the AI research and development company behind Claude — the frontier model used by millions of people worldwide.

Surprised this post received no love.

Well written. Presents an intriguing argument for plain text + git + grep + plugins over SQL databases.

Too many possible paths to spend our time on and only one person, yourself, to do it.

The only objection have is with what the OP considers to be an investment. Some things oddly missing:

• cryptocurrencies

• investments outside of the Wall Street gambling dens of declining purchasing power

• precious metals

• only interact with peers is settlement of tiny debts. No investment in their enterprises or community

If everyone followed the OP’s pattern of investment, there would be no real economy.

So the article is slightly cringe worthy; reads like propaganda for indoctrinating children.

See that pretty chart going up, that is your total personal wealth losing purchasing power. Will wake up one day a trillionaire that can’t buy a loaf of bread.

This article is actually a little interesting, lets recall PSF recently rejected being funded by US govt.

Two seconds later, Germany no problem.

Hmmm …

How old is this article? There hasn’t been EnvironmentError since py33

Had to look it up.

Your point still stands, ignoring Exceptions bad. The next thing would wanna see are the unit tests. If those are nonexistent then of course the code is gonna be buggy. The hint is that you called the CLI a script. So not a package.

So it’s a good thing you have revisited the code and hopefully rewritten it as a package with a test suite.

This is the kinda news want to wake up in the morning and be presented with.

We don’t need to agree these are DEI policies. This is a risk vs reward issue. So comes down to the simple question of, where does PSF derive it's funding.

If PSF feels it’s funding is sufficient, then it’s safer to not take the funding. Pursuing the funding in the first place therefore must have been a easily foreseeable mistake.

The West however is in a hyper-inflationary or at least inflationary situation. So PSF traditional base will face financial pressure.

May have the luxury now to turn down the funding, but sit back and buckle in as the US and EU moves the dial way up to, hold my beer. During that period, securing funding may become super difficult.

Thank you Thank you Thank you for listing the PSF activities that the PSF feels might violate current administrations executive order (EO) concerning DEI.

Can completely rule out these as non-issues:

• travel grants for the conferences
• encourages local chapters (THIS IS NOT DEI)

None of these PSF activities run afoul of the EO.

Would like to add this as also a non-issue:

• the two year claw back period (just hold the funds for two years)

As long as the PSF doesn’t go out of their way to ensure the code of conduct (1) or their operations or at conferences (2) are explicitly geared towards promoting DEI policies.

PSF is concerned, correct me if i’m mistaken, so this most likely is the source of their concerns. Increasingly seems like self-inflicted tempest in a tea cup or purposefully shooting themselves in the foot.

This is my stance. You are welcome to argue points, but gaslighting is not an argument. And only white people are gaslighted for tribalism, but its ok for everyone else to use identity politics in favor of their tribe.

If there are other real causes then list them. By presenting an actual argument i might be in danger of learning something.

You are showing a pattern of using psyche, especially reframing with gamed terminology (anti-inclusion), which then i counter by using the opposite terminology (anti-white). We could play this game from now 'til the end of eternity. This psyche back and forth however is not presenting an actual argument.

And in case you lack situational/contextual awareness, we are in a programming forum. Not being able to string together a coherent or convincing argument will make world+dog wonder whether you are lost.

Expect more from my peers. Stop toying with me and win the argument already. The barrier is not high.

The affects of anti-white discrimination policies (DEI) is alienation of white people. Luckily most white people are too dumb to properly respond until they are not. White people may march towards tribalism matching the rest of the world. Expect many subgroups to close themselves off.

What you should do if you are white:

• if possible, move to a state|country that is not actively discriminating against you or taxing you into extinction. Seek a clan that wants you as a member and aligns with your goals.

• do not publish. Which also takes out the job loss threat of AI

• do the absolute minimum to support the fiat printer masters

• study from the failures of political movements and activists. There are no sides. The lessons are universal.

• participate and teach others to participate in the parallel economy

• do not offer help to those who love their fiat money printer masters

Sit back and enjoy the show. All this tech is not written and maintained by retarts. Taking white people out of the equation, the tech maintenance collapse comes sooner.

wreck can. It’s venv aware. Takes full advantage of hierarchical requirement files. Is intuitive. The learning curve is minimal. Written in Python.

[[tool.wreck.venvs]]
venv_base_path = '.venv'
reqs = [
    'requirements/pip',
    'requirements/pip-tools',
    'requirements/prod',
    'requirements/dev',
    'requirements/manage',
    'requirements/kit',
    'requirements/mypy',
    'requirements/tox',
]
[[tool.wreck.venvs]]
venv_base_path = '.doc/.venv'
reqs = [
    'docs/requirements',
    'docs/pip-tools',
]

[tool.setuptools.dynamic]
dependencies = { file = ['requirements/prod.unlock'] }
optional-dependencies.pip = { file = ['requirements/pip.lock'] }
optional-dependencies.pip_tools = { file = ['requirements/pip-tools.lock'] }
optional-dependencies.dev = { file = ['requirements/dev.lock'] }
optional-dependencies.manage = { file = ['requirements/manage.lock'] }
optional-dependencies.docs = { file = ['docs/requirements.lock'] }

reqs fix --venv-relpath='.venv'

reqs fix --venv-relpath='.doc/.venv'

From *.in requirements files would produce *.unlock and *.lock files for venv .venv. Package versions are sync’ed within all requirements files within that venv.

spoiler alert: Python isn’t written in fortran, cobol, pascal, assembly, VBA, Java, javascript, or Rust (ignoring clunky pypy). uv is written in Rust.

spoiler alert: Don’t have to be a C coder to use Python

That means it can’t be maintained by the community it’s serving. For those skilled in both Rust and Python can understand why it would appear as the best thing since sliced bread.

What about for those not skilled in Rust? Should we also learn 15 other coding languages while we are at it?

wreck is written in Python and manages dependencies. via hierarchy of requirements files, not TOML. It’s venv aware. For Python package authors.

This has nothing to do with Python. Why post it here? Blockchain solves SPAM like this ^^

Not everyone is a C or a Rust coder. In C, sending in a pointer, know it’s pass by reference, not pass by value.

In Python, depends if it’s immutable or mutable. Python coders eventually become hyper aware of the difference.

Python coders that want direct access to C libraries can use Cython CPython or ctypes. Probably missing a few options. Maybe others can chime in. This comes at the expense of much more complicated packaging.

Any package author that has underlying C code in their package automagically gains rock star status.

This is what i get when click Play button

Traceback (most recent call last):
  File "/lib/python3.12/site-packages/micropip/_commands/install.py", line 142, in install
    await transaction.gather_requirements(requirements)
  File "/lib/python3.12/site-packages/micropip/transaction.py", line 55, in gather_requirements
    await asyncio.gather(*requirement_promises)
  File "/lib/python3.12/site-packages/micropip/transaction.py", line 62, in add_requirement
    return await self.add_requirement_inner(Requirement(req))
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/lib/python3.12/site-packages/micropip/transaction.py", line 151, in add_requirement_inner
    await self._add_requirement_from_package_index(req)
  File "/lib/python3.12/site-packages/micropip/transaction.py", line 186, in _add_requirement_from_package_index
    metadata = await package_index.query_package(
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/lib/python3.12/site-packages/micropip/package_index.py", line 286, in query_package
    raise ValueError(
ValueError: Can't fetch metadata for 'memory-graph'. Please make sure you have entered a correct package name and correctly specified index_urls (if you changed them).
Traceback (most recent call last):
  File "/lib/python3.12/site-packages/micropip/_commands/install.py", line 142, in install
    await transaction.gather_requirements(requirements)
  File "/lib/python3.12/site-packages/micropip/transaction.py", line 55, in gather_requirements
    await asyncio.gather(*requirement_promises)
  File "/lib/python3.12/site-packages/micropip/transaction.py", line 62, in add_requirement
    return await self.add_requirement_inner(Requirement(req))
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/lib/python3.12/site-packages/micropip/transaction.py", line 151, in add_requirement_inner
    await self._add_requirement_from_package_index(req)
  File "/lib/python3.12/site-packages/micropip/transaction.py", line 186, in _add_requirement_from_package_index
    metadata = await package_index.query_package(
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/lib/python3.12/site-packages/micropip/package_index.py", line 286, in query_package
    raise ValueError(
ValueError: Can't fetch metadata for 'memory-graph'. Please make sure you have entered a correct package name and correctly specified index_urls (if you changed them).

From console

Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://static.cloudflareinsights.com/beacon.min.js/vcd15cbe7772f49c399c6a5babf22c1241717689176015. (Reason: CORS request did not succeed). Status code: (null).

None of the “sha512” hashes in the integrity attribute match the content of the subresource. The computed hash is “z4PhNX7vuL3xVChQ1m2AB9Yg5AULVxXcg/SpIdNs6c5H0NE8XYXysP+DGNKHfuwvY7kxvUdBeoGlODJ6+SfaPg==”. memory-graph.com
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://static.cloudflareinsights.com/beacon.min.js/vcd15cbe7772f49c399c6a5babf22c1241717689176015. (Reason: CORS request did not succeed). Status code: (null).

None of the “sha512” hashes in the integrity attribute match the content of the subresource. The computed hash is “z4PhNX7vuL3xVChQ1m2AB9Yg5AULVxXcg/SpIdNs6c5H0NE8XYXysP+DGNKHfuwvY7kxvUdBeoGlODJ6+SfaPg==”. memory-graph.com
Content-Security-Policy: The report URI (about:blank) should be an HTTP or HTTPS URI. memory-graph.com
Content-Security-Policy: (Report-Only policy) The page’s settings would block a worker script (worker-src) at https://memory-graph.com/py_worker.js from being executed because it violates the following directive: “worker-src 'none'” memory-graph.com
Loading micropip, packaging pyodide.asm.js:10:95312
Loaded micropip, packaging pyodide.asm.js:10:95608
PythonError: pyodide.asm.js:10:52088

For those with:

• ancient browsers that won’t run that memory graph web debugger

• the attention span of a pigeon and can’t be bothered to read a long explanation that doesn’t address this particular pycon

>>> import copy
>>>
>>> a = [[0]]
>>> c1 = a
>>> c2 = a[:]
>>> c3 = list(a)
>>> c4 = a.copy()
>>> c5 = copy.copy(a)
>>> c6 = copy.deepcopy(a)
>>> 
>>> c1[0].append(1)
>>> c2[0].append(2)
>>> c3[0].append(3)
>>> c4[0].append(4)
>>> c5[0].append(5)
>>> c6[0].append(6)
>>> 
>>> print(a)
[[0, 1, 2, 3, 4, 5]]

copy.deepcopy makes a separate memory copy into c6. So appending to c6 affects c6, but not a

The point about avoiding legal action is a risk that has to be weighed against the reward. And if you wrote the article, carefully quantifying the risks and associated costs. Would be a much higher degree of difficulty to argue against. Also would leave the impression that you’d make a great Project Manager.

However that is just not PSF argument nor position.

The PR articles make exactly two points:

1. PSF leadership supports DEI
2. the claw back risk is scary

Have already addressed both issues the PSF has with moving forward and accepting funding.

PSF can drop their DEI religious tenant, which is not virtuous, or continue to not be funded.

Eventually the emperor has no clothes, would become obvious to all, that the current PSF leadership stance causes unfortunate and completely avoidable consequences.

There is another unstated risk, explained best by Donald Rumsfield, the unknown unknowns. The west is at war with Russia. During wartime, govts can do unspeakable things. By being funded by govt, that squarely puts team PSF within the Wests or NATOs good graces. PSF is betting the eye of Sauron never comes their way. So accepting funding can be a positive risk with an associated absolutely huge opportunity reward. Not just the $1.5M, but US govt tends to throw money at problems especially during wartime. If US govt sees Python as a strategic resource, we might look back at that small $1.5M with nostalgia.

The PSF is a relatively small organization, operating with an annual budget of around $5 million per year, with a staff of just 14. $1.5 million over two years would have been quite a lot of money for us, and easily the largest grant we’d ever received.

source

Also thank you mod for censoring all my comments. You must prefer an echo chamber where open debate is stifled. This is also how the PSF operates. If a position cannot stand up to scrutiny, the go to tactic is to censor all opposing voices.

So the comments deleting mod has proven my point beyond any reasonable doubt.

Blockchain solves this!

Group think is a disease. The US gov’t is in the right to defund the disease of DEI. And the PSF laughably is cooperating rather than adapting.

i oppose the group think that produced those articles proudly virtue signaling their failure and reframing it as a moral victory.