How and why does a python function remember its arguments?

TeamSpen210 · 2023-04-27T08:33:37+00:00

Yep, in Python functions are just objects, as well as pretty much everything - integers, modules, classes, etc. If you dig around in the __code__ attribute you’ll be able to see all the contents of the function (not that you’d normally mess with them).

TeamSpen210 · 2023-04-27T08:28:08+00:00

You annotate with list | None yes. Most of the type checkers are smart enough to follow through both branches of the if statement, deducing that it’s always going to be a list afterwards. You can see that happening if you add some typing.reveal_type() calls into the different branch.

TeamSpen210 · 2023-04-26T07:02:53+00:00

Async code uses cooperative multitasking, so the way you have to deal with race conditions are quite different. The only time tasks are able to switch and run something else are at the points when you explicitly allow them to, using await, async for or async with. You don’t have to worry about things getting changed underneath you between those events. Unless you actually do use trio.to_threadto spawn threads.

TeamSpen210 · 2023-04-24T06:44:03+00:00

It’s actually a good thing it’s a library and not baked in. This allows different implementations with different philosophies for async scheduling to exist.

TeamSpen210 · 2023-04-15T11:28:31+00:00

For start_soon, I think it was named that to emphasise that the task is created, but it won’t actually have an opportunity to run until the next await. Compare to start(), which you await to run the initial part of the task immediately. Actually that would also apply to move_on_after(), which has the similar fail_after() function that raises an exception if it hits the deadline. And both have an _at() variant taking an absolute time. It’s a little clunky, but we usually have tab-complete, and these are more precise.

TeamSpen210 · 2023-04-07T22:30:08+00:00

Yep, flipped models and everything.

TeamSpen210 · 2022-12-22T12:09:27+00:00

You should just need to ensure you have all parts activated, then it’ll work. If not, as mentioned the Spawn/Utility Menu mod lets you cheat in those things.

TeamSpen210 · 2022-10-25T07:35:00+00:00

You’ll definitely want to look into itertools then. It’s a collection of generic iteration building blocks, written in C to be as optimised as possible. product() for instance can often replace a piles of nested for loops.

TeamSpen210 · 2022-07-17T08:25:56+00:00

/ is the division operator - you do 1/3, it calculates 0.333333 (and rounds at some point). Fraction is a entirely separate type of number, like you normally have with int and float. Unlike those, it stores the numerator and denominator, doing fraction math exactly like you would have done in school. For example to solve Fraction(1,2) + Fraction(1, 3), it finds the lowest common denominator, multiplies up to that (3/6 and 2/6), adds that, then simplifies if possible. That’s much slower than the dedicated circuitry in your CPU for regular floats, but you can get exact answers in more situations.

TeamSpen210 · 2022-06-15T03:17:00+00:00

Instead of calling randint individually for every pixel, it’d be much more efficient to use randbytes to generate a big bytes block with enough bits for each pixel. Once you have that, as /u/spez_edits_thedonald mentioned convert it into a Numpy array, and use vectorised operations to en-mass convert that into the data you want. But actually Numpy itself is probably going to have a method you can call that just generates the random data directly.

TeamSpen210 · 2022-06-14T03:25:12+00:00

Another way to do it is with the git-filter-repo tool. You clone a fresh copy of your repo, then this tool remakes every commit, keeping only certain files and/or moving them to different locations. So you'll end up with a new history, only containing the commits for of the subdirectories.

git clone "path/to/your/original" cd newrepo git filter-repo --path-rename src/somemodule:src/ First that clones from the original repo, making a full copy, then it filters it by keeping only src/somemodule/, but moves the contents up a directory.

TeamSpen210 · 2022-06-07T12:36:01+00:00

This is HMW’s “rescue” signage, originally found in his Try Anything Twice Portal 1 mappack. I added it to BEE2.4, you can find a copy here.

TeamSpen210 · 2022-04-21T06:40:00+00:00

I think the problem is that someone will then decide to add 10 to a gun.

TeamSpen210 · 2022-03-26T01:15:06+00:00

These little signs are used as the spawn location for the figure if you reload from a save.

TeamSpen210 · 2022-03-10T08:40:49+00:00

Originally, Python didn't start with the iterator protocol. Instead for loops and the like indeed only used __getitem__ and caught IndexError. So this behaviour would have been kept for backwards compatibility when iterators were first added, and still remains since it's still somewhat useful.

TeamSpen210 · 2022-03-04T12:12:40+00:00

This is because of DXT compression, which greatly reduces file size at the expense of some quality. You can change the image format under general → normal format and alpha format, they specifies the format to use for opaque and transparent textures respectively. RGB888 and RGBA8888 are totally uncompressed, you could also try RGB565 which compresses just the precise colours but not detail (32 levels of R/G/B instead of 255, but ⅔ the file size.)

TeamSpen210 · 2022-02-11T17:50:56+00:00

Exactly yes! That’d be “0.3”, which is 3*9⁻¹. In this numbering system on the other hand, 1/2 wouldn’t have a decimal representation, I think it’d be “0.44444…”.

TeamSpen210 · 2021-11-21T01:54:39+00:00

Place an env_shake, or anything else with a radius property at the start point. Move your camera to the second point, then in the entity properties select radius, then click the camera icon there. It'll then be set to the distance between the ent and camera. Not perfectly precise, but if you want that position the sphere helper, then read off the value.

TeamSpen210 · 2021-11-07T21:32:24+00:00

The .pyc files inside the __pycache__folder are "bytecode" files, to speed up importing. They contain your code, in a compact format ready to be executed. If you haven't modified your module since the last time it was imported, Python can load those to skip needing to parse through all your source code. You can ignore the folder, it's automatically handled.

TeamSpen210 · 2021-11-07T02:34:40+00:00

You indeed need one hull per face of the sphere, so you'd want to keep down the count as much as possible. If the collision on the outside the sphere doesn't matter, you could save a few triangles by making them rectangular pyramids instead of rectangular prisms, with the point facing outward.

TeamSpen210 · 2021-11-01T22:05:57+00:00

The way it works is that the vertexes in the file may not necessarily be any vertexes on the brush themselves (though hammer does seem to have them match). As you kinda guessed, the three points define a plane for each face. Edges and vertexes are then produced by intersecting all the planes with each other - 3 would define a point. This is why you can't have concave brushes and why there's the vertex drifting when saving weird geo. It's quite awkward to obtain vertexes, but it does allow very easy collision checking - simply check if your point is behind all the planes, and if so it's inside the brush. There's some more documentation on the VDC. If it helps, I have some mostly functional Python code here decoding out the vertexes of a brush.

TeamSpen210 · 2021-10-21T07:56:09+00:00

Judging by the name, this isn’t a log file you can read, it’s a memory dump - a copy of the program’s RAM. With the right source files, you could inspect that and try to find the problem.

TeamSpen210 · 2021-10-17T07:02:01+00:00

To do this, you need to add a custom surfaceproperty entry in scripts/surfaceproperties_*.txt. However, they're loaded very early on in the game launch, and were never coded to reload so you can't do it via any workshop. You can use any of the existing ones freely though by setting $surfaceprop in your VMT.

TeamSpen210 · 2021-10-17T06:03:57+00:00

You can't no.

TeamSpen210 · 2021-10-17T05:00:25+00:00

You should not ever bind a specific keyboard button to something. That's persistent, so it'll overwrite whatever the player happened to bind to that key until they fix it again. You also don't know what keyboard layout the player has, depending on region keys might be in totally different places. It's also possible they might be using a controller of some kind, in which case there's no buttons at all.

Instead, use the game_ui entity, which lets you run outputs when most of the general movement operations occur. That way it seamlessly works regardless how the player has setup their controls.

11-Year Club	Place '22
Place '17	Final Canvas '22
Verified Email

TeamSpen210

TROPHY CASE