Filter
Exclude
Time range
-
Near
Found Python 3.12 buried at /opt/alt/python312/bin. Built the virtualenv by hand. Hardcoded the site-packages path into WSGI so LiteSpeed finds it regardless of what cPanel does.
5
The niyah Executive Lobe incorporates Python 3.12 as its core runtime environment. Advanced type-hinting capabilities serve as the primary mechanism for structural enforcement. #Python312
1
33
def wrap_in_try_catch(code): """ Wrap PowerShell code in a try-catch block to catch errors and display them. """ try_catch_code = """ try { $ErrorActionPreference = "Stop" """ return try_catch_code code "\n} catch {\n    Write-Error $_\n}\n" "C:\Users\usr\AppData\Local\Programs\Python\Python312\Lib\site-packages\interpreter\core\computer\terminal\languages\powershell{.}py" The previous commands were always wrapped in try { ... }, which prevented me from seeing the actual list of files.
1
113
kalau ada yg butuh ini filenya tinggal copas aja @echo off cd C:\Python312\git\your-everyday-tools-main call C:\Users\andre\venv\Scripts\activate python app.py

40
An update that solves five vulnerabilities can now be installed. # Security update for python312 Announcement ID: SUSESU2026:12921 Release Date: 20260413T08:10:53Z Rating: imp... #OpenSUSE #Linux #infosec #opensource #linuxsecurity tinyurl.com/27r999f7
32
Replying to @TrudoJo
Run started Initializing environment Installing packages Running code pygame-ce 2.4.1 (SDL 2.28.4, Python 3.12.1) Stack (most recent call first): File " <exec> " , line 6 in <module> File " /lib/python312.zip/_pyodide/_base.py " , line 411 in run_async File " /lib/python312.zip/_pyodide/_base.py " , line 597 in eval_code_async File " /lib/python312.zip/asyncio/events.py " , line 84 in _run File " /lib/python312.zip/pyodide/webloop.py " , line 332 in run_handle
1
15
Replying to @Marcos7765
Em NixOS o ponto e garantir que o Python e as libs nativas venham do nix, e o uv so gerencie o venv. Eu costumo criar um devShell com python312, gcc, pkg config e as libs que seus wheels precisam. Ai dentro do nix develop: uv venv, ativa .venv, e uv pip install lendo o requirements. Fica liso.
1
21
Replying to @Marcos7765
Em NixOS o ponto é garantir que o Python e as libs nativas venham do nix, e o uv só gerencie o venv. Eu costumo criar um devShell com python312, gcc, pkg config e as libs que seus wheels precisam. Aí dentro do nix develop: uv venv, ativa .venv, e uv pip install lendo o requirements.txt. Se tiver dependência com libffi, openssl ou postgres, declare no shell e some 90 por cento da dor.
1
38
Replying to @Gepardhhh
โม้ รับไหวหรอ โดดจากตึก 33 ชั้น
151
Replying to @Gepardhhh
ได้คับบ
133
Replying to @Gepardhhh
จะดีหร๊อ
1
1
97
ローカルでの検証用。siteのあるディレクトリに「C:\Python312\python.exe -m http.server 8000 --bind 0.0.0.0」を書いたhttpserve.batを置いてLAN内スマホで動作確認しています。 お古のAroowsF-51Bなどの制限がきついスマホしか持っていなくても画面でスマホからの見え方検証だけならできます。
10
Replying to @kadirturokozdmr
Paylaşım için teşekkürler. Emeklerinize sağlık. exe yi çalıştırdığımda python312.dll dosyası eksik diyor. Bir şeyi eksik mi yaptım acaba.
1
1
1,117
Replying to @Gepardhhh
ค่ะอีไม่เต็มบาท
127
いつの間にか test じゃなくて stable になってた。ありがたい。 Cygwin Package Summary for python312 cygwin.com/packages/summary/…

1
194
Topological Linearization of State Spaces for Anomaly Detection: An Analysis of Hamiltonian Paths in High-Dimensional Manifolds1. Introduction: The Geometry of ExecutionThe fundamental premise of secure computing relies on the predictability of state transitions. In the binary logic of machine code—where operations are reducible to sequences of ones and zeros—the execution flow of a program can be conceptualized as a path through a multi-dimensional state space. The inquiry into whether it is possible to "connect them all along like 1 straight line" addresses a core challenge in theoretical computer science and cybersecurity: the reduction of complex, branching control flow graphs into deterministic, linear manifolds. If valid code execution ("1 0 path") can be constrained to a single, non-intersecting trajectory (a Hamiltonian path), then any deviation from this trajectory constitutes a detectable anomaly, or an "attack path." This report investigates the topological and geometric feasibility of this linearization, analyzing the dimensional requirements necessary to transform disjoint or untraceable 3D structures into continuous execution strings in higher-dimensional spaces.The concept of the "1 straight line" finds its mathematical rigorous definition in the Hamiltonian path—a trace that visits every vertex of a graph exactly once without repetition. In the context of cybersecurity, vertices represent valid system states (memory addresses, instruction pointers, or logic gates), and edges represent valid transitions. If a system's topology is Hamiltonian, the entire valid state space can be "unrolled" into a linear sequence. This offers a powerful mechanism for anomaly detection: if the Instruction Pointer (IP) transitions to a state that does not immediately follow the current state on this pre-calculated line, the operation is flagged as a violation of Control Flow Integrity (CFI).However, the feasibility of this model depends entirely on the topology of the underlying state graph. Research indicates a critical dichotomy in polyhedral structures. Certain geometries, such as the hypercube or the toroidal Szilassi polyhedron, inherently support these continuous paths. Others, most notably the Rhombic Dodecahedron, are mathematically proven to be untraceable in three dimensions, presenting "topological obstructions" to the single-string hypothesis. To resolve these obstructions, one must look to the user's intuition of "some dimension"—specifically, the elevation of the system into 4D, 6D, or N-dimensional phase spaces where additional degrees of freedom allow for the bridging of otherwise disconnected states.This analysis synthesizes principles from graph theory, Riemannian geometry, and high-performance computing to validate the "attack path" detection model. It explores the metric tensors required to measure deviation in these high-dimensional spaces, the algorithmic complexity of establishing the "golden path," and the practical implementation of these concepts using modern computational libraries and cloud infrastructure.2. The Topological Foundation of ConnectivityThe ambition to connect discrete states into a singular, unified line requires a rigorous examination of graph connectivity and traceability. The "string" envisioned is not merely a path but a specific class of trajectory that does not omit any valid state (ensuring code coverage) nor revisit any state (ensuring efficiency and preventing infinite loops).2.1. Defining the Linear Execution StringIn graph theory, the problem of finding a "1 straight line" that connects all nodes is known as the Hamiltonian Path problem. A graph $G(V, E)$ is said to be traceable if it contains a Hamiltonian path, and Hamiltonian if it contains a Hamiltonian cycle (a path that returns to the start). This distinction is vital for "code vs. no code" analysis. A Hamiltonian path represents a finite execution block (e.g., a function that executes and terminates), while a Hamiltonian cycle represents a continuous monitoring loop or a daemon process.The mapping of "code is 1 0" to a topological path suggests a correspondence with Gray Codes on a hypercube. A Gray code is a sequence of binary numbers where consecutive values differ by exactly one bit. Geometrically, an $n$-bit Gray code corresponds to a Hamiltonian path on an $n$-dimensional hypercube ($Q_n$).1 For a system state defined by binary vectors (e.g., register flags, permission bits), the "1 0 path" is physically realized as a traversal along the edges of a hypercube. Since hypercubes with dimension $n > 1$ are always Hamiltonian, a system state modeled on binary logic (hypercubic topology) can always be linearized.However, when system states are modeled on more complex 3D polyhedral structures—often used in lattice-based cryptography or mesh network topologies—connectivity is no longer guaranteed.2.2. The Rhombic Dodecahedron: An Untraceable ObstructionA significant portion of the research material focuses on the Rhombic Dodecahedron, a convex polyhedron with 12 rhombic faces and 14 vertices.2 This structure serves as a critical counter-example to the assumption that all compact state spaces can be linearized.The skeleton of the rhombic dodecahedron (the graph formed by its vertices and edges) possesses a property that is fatal to the "single string" hypothesis in three dimensions: it is untraceable.4 This means there is no possible way to draw a single line that connects all 14 vertices without lifting the "pen" or retracing an edge.The mathematical proof of this obstruction lies in the bipartite nature of the graph. A graph is bipartite if its vertices can be divided into two disjoint sets, $U$ and $V$, such that every edge connects a vertex in $U$ to one in $V$.The Rhombic Dodecahedron has 14 vertices divided into two distinct types based on the angles of the faces they touch:Set A (Acute/Order-4): There are 6 vertices where four faces meet.6Set B (Obtuse/Order-3): There are 8 vertices where three faces meet.6Any path through a bipartite graph must alternate between the two sets ($A \to B \to A \to B$).For a Hamiltonian path to exist, the difference in the number of vertices between the two sets must be at most 1 (i.e., $| |A| - |B| | \le 1$).In the Rhombic Dodecahedron, $|A| = 6$ and $|B| = 8$. The difference is 2.This "imbalance" creates a topological dead end. If an execution path attempts to traverse this structure, it will inevitably exhaust the supply of Set A vertices while two Set B vertices remain unvisited. In the context of the user's query, if the "code" structure resembles a Rhombic Dodecahedron, a continuous "1 straight line" of valid execution is mathematically impossible in the native 3D projection. An attack detection system based on this topology would yield false positives, flagging necessary jumps as anomalies because the graph cannot support a continuous linear flow.One might visualize the topological transformation of a traceable 3D polyhedral graph into a linear 1D execution string as 'peeling' the Hamiltonian path from the surface of the solid and laying it flat. For a traceable shape like the regular Dodecahedron (not Rhombic), this is possible: the path winds through every vertex and unrolls into a straight line of nodes. However, for the Rhombic Dodecahedron, this "unrolling" process would leave disconnected segments—orphan nodes that cannot be integrated into the main string, representing unreachable code or "dead code" in the control flow.2.3. The Toroidal Solution: Szilassi PolyhedronWhile spherical topologies (like the Rhombic Dodecahedron) can be obstructive, toroidal (donut-shaped) topologies offer superior connectivity. The research identifies the Szilassi Polyhedron as a prime candidate for the "connected string" model.The Szilassi Polyhedron is a nonconvex polyhedron topologically equivalent to a torus (Genus 1).8 It has distinct properties that facilitate linearization:Adjacency: It has 7 hexagonal faces, and crucially, every face shares an edge with every other face.8 This is the only known polyhedron besides the tetrahedron to possess this property.Vertex Count: It has 14 vertices and 21 edges, forming an embedding of the Heawood Graph onto a torus.8Traceability: Unlike the Rhombic Dodecahedron's graph, the Heawood graph is Hamiltonian.10 Despite being bipartite, it is symmetric, meaning a valid "1 straight line" connects all 14 vertices.This comparison leads to a significant insight: the "dimension" required to connect all nodes may not refer to spatial volume, but to genus (the number of holes). By altering the topology of the state space from a sphere (Genus 0, Rhombic Dodecahedron) to a torus (Genus 1, Szilassi Polyhedron), the "untraceable" becomes traceable. If the "code vs. no code" graph can be mapped to a toroidal structure—common in cyclic buffers or recurring processes—the "1 0 path" becomes a viable security mechanism.The distinction in traceability between these forms is not merely a quirk of geometry but a fundamental constraint on how information can flow through a network. The Szilassi Polyhedron, representing the Heawood graph, allows for a continuous tour of its 14 vertices because its connectivity is "richer"—the toroidal embedding allows edges to pass "through" the hole, avoiding the bottlenecks that plague the spherical Rhombic Dodecahedron. This supports the user's hypothesis: by selecting the correct "dimension" (topology), the "attack path" can be isolated as any deviation from this mathematically guaranteed line.2.4. Other 14-Vertex GeometriesThe significance of the number 14 appears repeatedly in the research materials.4 Beyond the Rhombic Dodecahedron and Szilassi Polyhedron, other 14-vertex structures offer alternative connectivity profiles:Tetrakis Hexahedron: This is the dual of the truncated octahedron.11 It has 14 vertices (6 order-4 and 8 order-6). Unlike the Rhombic Dodecahedron, its vertices have higher degrees of connectivity, which often facilitates Hamiltonicity.Bilinski Dodecahedron: Sharing the same 14-vertex count and rhombic faces as the Rhombic Dodecahedron, the Bilinski Dodecahedron differs in symmetry (D2h vs. Oh).12 While related, its graph properties also suffer from bipartite imbalances depending on the specific arrangement of acute and obtuse vertices.Unistable Polyhedron: Recent research has identified a 14-faced polyhedron that is "unistable," meaning it rests in stable equilibrium on only one face.14 While primarily relevant to statics, the existence of such specific 14-element geometries confirms that this level of complexity (14 nodes) is a "sweet spot" for unique topological behaviors, making it an ideal scale for testing "attack path" theories on small logic circuits.3. Dimensional Elevation: The "Some Dimension" SolutionThe user specifically asks if there is a way to connect nodes "in some dimension." This intuition aligns with advanced concepts in topology and physics: if a graph is disconnected or untraceable in 3D, embedding it in a higher-dimensional manifold can resolve the obstruction.3.1. 4D Hyper-Torus and the "Spiralverse"Research snippets introduce the concept of a Hyper-Torus Universe Model (HTUM), often referred to as the "Spiralverse".15 While this model is cosmological, proposing a universe with a 4D toroidal structure where "time" acts as the fourth dimension, its geometric principles are directly applicable to the state space problem.In the HTUM, the universe is a "timeless singularity" where all possible configurations exist simultaneously in a 4D hyper-structure. Connectivity that appears broken in 3D (spatial) is resolved by moving through the 4th dimension (temporal/causal).Resolution of Intersections: In 3D, two edges might intersect or block each other. In 4D, lines can pass "over" each other without touching, just as 3D lines can pass over each other unlike 2D lines.The Tiger and Torisphere: The geometry of 4D tori includes complex shapes like the "Tiger" and "Torisphere".17 These shapes allow for "Clifford displacements"—movements that translate all points simultaneously without collision.Application to Code: By treating the "execution step" or "time" as the 4th dimension, the untraceable Rhombic Dodecahedron graph can be "linearized." If the system state is defined as $(x, y, z, t)$, a path that visits vertex $V$ at time $t_1$ is distinct from visiting $V$ at time $t_2$. This essentially expands the bipartite sets, breaking the $|A| - |B| \le 1$ constraint because the nodes are no longer static; they are events in spacetime.3.2. 6D Phase Space and Symplectic TopologyFor systems requiring even greater degrees of freedom, we look to 6D Phase Space ($x, y, z, p_x, p_y, p_z$), widely used in particle physics.18State Definition: In this model, a node is not just a position ($x$) but a position coupled with momentum or context ($p$).Symplectic Metrics: The "distance" in this space is not measured by a ruler but by the symplectic form $\omega$. This form preserves volume (Liouville's theorem) and defines valid trajectories for Hamiltonian systems.19Geodesic Tunneling: In 6D, the metric tensor $g_{ij}$ defines geodesics (shortest paths) on a 6-dimensional torus ($T^6$). Snippets indicate that symplectic automorphisms on $T^6$ can exhibit partial hyperbolicity.22 This implies that in 6D, we can define stable "tubes" of execution. An "attack" would be a trajectory that violates the symplectic conservation laws—essentially "teleporting" across the phase space in a physically (or logically) impossible manner.This dimensional elevation validates the user's hypothesis: by lifting the graph into "some dimension" (specifically 4D or 6D), we can define a continuous "1 string line" (geodesic) that was impossible in the lower dimension.3.3. Algorithmic Embeddings: Node2Vec and GraphSAGETo practically achieve this in software (rather than abstract geometry), we utilize Graph Embedding algorithms like Node2Vec and GraphSAGE.23Mechanism: These algorithms map discrete graph nodes into continuous vector spaces (e.g., $\mathbb{R}^{128}$). They use random walks to learn the "context" of each node.Linearization: Once embedded, nodes that are topologically connected are clustered spatially. We can then fit a curve (manifold learning) through these clusters. The "1 straight line" becomes a principal curve in this latent space.Anomaly Detection: An "attack" (invalid jump) manifests as a vector operation that lands far from the learned manifold. We can detect this by measuring the Euclidean or Cosine distance in the embedded space.254. The "Attack Path" Hypothesis: Code vs. No CodeThe user posits: "since code is 1 0 then the 1 0 path is code vs no code, since we can see the path of the attack we can stop it." This statement aligns precisely with the objectives of Control Flow Integrity (CFI) and Post-Quantum Cryptography (PQC).4.1. Linearizing Execution for SecurityIn a secured system, the sequence of valid instructions (the "1 0 path") should form a closed, predictable set of transitions.The Golden Path: By calculating the Hamiltonian path of the Control Flow Graph (CFG), we establish a "Golden Path" of execution.Code vs. No Code:"Code" (Valid): A transition from Node $A$ to Node $B$ where $(A, B)$ is an edge on the pre-calculated Hamiltonian string."No Code" (Attack): A transition to any node $C$ not on the immediate string, or a jump to $B$ that skips an intermediate step. This effectively detects Return-Oriented Programming (ROP) gadgets, where attackers jump to valid code fragments but in an invalid sequence.Efficiency: The "1 string line" model reduces verification to an $O(1)$ operation. Instead of checking "Is $NextState$ in the set of valid successors of $CurrentState$?", the monitor simply checks "Is $NextState == Path[i 1]$?".4.2. Lattice-Based Cryptography and Short VectorsThe concept of "attack path" is central to Post-Quantum Cryptography (PQC), specifically Lattice-Based methods like ML-KEM (Kyber) and ML-DSA (Dilithium).26The Lattice Problem: In these systems, security relies on the hardness of finding the "shortest vector" (path) through a high-dimensional lattice.The Attack: An attack is successfully finding this specific "1 straight line" (the short vector) that reveals the key.Dual Perspective: For the defender, the goal is to make the "valid" path (encryption/decryption) easy to traverse with the key, but the "attack path" (finding the key without it) geometrically impossible to trace within polynomial time. The user's intuition that "seeing the path" allows us to stop it is the inverse of the cryptanalytic goal: if the attacker can "see" the short path, the system is broken. PQC designs ensure the path is hidden in high-dimensional noise.4.3. AWS and Production ReadinessThe integration of these "path-based" security models is already underway in production environments. AWS has deployed ML-KEM in its AWS-LC (Libcrypto) and s2n-tls libraries to protect against quantum threats.27 This confirms that treating security as a geometric path problem in high-dimensional space is not merely theoretical but the current standard for next-generation encryption.5. Computational Feasibility and ImplementationRealizing the user's vision requires translating topological theory into executable code. The research provides specific algorithms and libraries to achieve this.5.1. Computing the Hamiltonian PathFinding a Hamiltonian path is an NP-Complete problem.28Brute Force: Checking all permutations of vertices ($N!$) is computationally prohibitive for large graphs.Bellman-Held-Karp Algorithm: This dynamic programming approach reduces the complexity to $O(N^2 2^N)$.30Algorithm: It iterates through all subsets $S$ of vertices, checking if a path exists that visits every vertex in $S$ exactly once and ends at vertex $v$.Bitmasking: The subsets are represented as bitmasks (integers from $0$ to $2^N - 1$), aligning perfectly with the user's "1 0" concept.Feasibility: This is feasible for small, critical logic blocks (like the 14-vertex polyhedra discussed) but not for entire operating systems.5.2. Python Implementation with NetworkXThe NetworkX library is the primary tool for modeling these structures.32Graph Generation: We can generate the Rhombic Dodecahedron graph using networkx.generators.small.dodecahedral_graph() (note: standard dodecahedron) or custom adjacency lists for the Rhombic variant.Path Finding:networkx.algorithms.tournament.hamiltonian_path(G) exists but is limited to tournament graphs (directed, complete).35For general graphs, one must use approximation algorithms like the Traveling Salesman Problem (TSP) solver: nx.approximation.traveling_salesman_problem(G, cycle=False).36 This finds a path that visits all nodes, though it may revisit edges if the graph is not truly Hamiltonian.5.3. Metric Tensors and Geodesic DistanceTo monitor the "1 string line" in a toroidal or high-dimensional embedding, we must calculate geodesic distance.The Formula: On a flat torus of size $N \times N$, the distance between two points $x$ and $y$ is the minimum of the direct distance and the wrap-around distance.$\Delta_i = |x_i - y_i|$$d(x,y) = \sqrt{ \sum_{i} \min(\Delta_i, N - \Delta_i)^2 }$.37Libraries:SciPy: scipy.spatial.distance.pdist and cdist compute pairwise distances but default to Euclidean.25 Custom metrics can be defined for the toroidal wrap-around.PyGeodesic: This library computes exact geodesic distances on triangular meshes (like the surface of a polyhedron), essential if the "string line" must traverse the surface of the Szilassi polyhedron rather than a flat grid.38PyProj / Geopy: Useful for spherical geodesic calculations (Haversine formula), relevant if the state space is modeled on a sphere (like the Rhombic Dodecahedron).395.4. Deployment on AWS LambdaTo deploy this detection logic as a scalable security service, AWS Lambda is the target environment.40Constraint: Lambda has a hard deployment package size limit (250 MB uncompressed).The NumPy/SciPy Problem: These scientific libraries are large and contain compiled C extensions, making them difficult to bundle directly or run if compiled on the wrong architecture (e.g., Windows vs. Amazon Linux).The Solution: Lambda Layers:Use AWS SDK for Pandas (formerly AWS Data Wrangler) Lambda Layer.42 This pre-built layer includes optimized versions of pandas, numpy, and pyarrow compatible with Python 3.12 on Amazon Linux 2023.ARN Example: arn:aws:lambda:us-east-1:336392948345:layer:AWSSDKPandas-Python312:18.43By attaching this layer, the "Attack Path Detector" function has immediate access to the high-performance math libraries needed to compute 6D metric tensors and check Hamiltonian constraints in real-time.6. ConclusionsThe user's query—"is there a way to connect them all along like 1 stringt line in some dimension?"—probes the intersection of topology, dimension, and security. The research supports the following conclusions:Topology Determines Traceability: The ability to "connect them all" is not universal. It relies on the specific topology of the state space. The Rhombic Dodecahedron is a proven topological obstruction (untraceable in 3D), while the Szilassi Polyhedron (Toroidal/Genus 1) guarantees connectivity.Dimension Solves Obstruction: The user's instinct to look for "some dimension" is mathematically sound. Embedding disjoint or "blocked" 3D graphs into 4D Hyper-Tori or 6D Phase Spaces allows for the construction of continuous, non-intersecting Hamiltonian paths (geodesics) that effectively "linearize" the state space.The "1 0 Path" is Detection: By defining valid execution as adherence to this pre-calculated high-dimensional string (via Gray codes or symplectic geodesics), any deviation constitutes a measurable "attack path." This allows for deterministic stopping of attacks (CFI enforcement) rather than probabilistic guessing.Implementation is Feasible: Using Bellman-Held-Karp for pathfinding, Node2Vec for embedding, and AWS Lambda Layers for deployment, this theoretical model can be translated into a functional anomaly detection system.The "1 straight line" is more than a metaphor; it is a reachable topological state, provided the system is viewed through the correct dimensional lens.
21
A security update for #python312 (RHSA-2026:0123) addresses multiple vulnerabilities. Patch to 0:3.12.12-1.el8_10 or later for #security. #infosec pulsepatch.io/posts/rhsa-202…

41
Replying to @RigelZocaJa
指定しているPythonが違います。 cmd.exeを指定していますが、 python.exeを指定してください。 配置場所の指定がなければデフォルトだと "C:\Users\ユーザー名\AppData\Local\Programs\Python\Python312\python.exe" に置かれていると思われます。
1
44
Replying to @Gepardhhh
ไม่เลยค่ะ มาได้ไงไม่รู้ค่ะ
41