Clément Robert neutrinoceros

## repl2script.py
# Python 3.8 is required, but this was only tested manually with 3.12
from __future__ import annotations

import argparse
import re
import sys
from dataclasses import dataclass
from functools import cached_property
from pathlib import Path

## test_shearingbox_adv.py
"""
Implementation examples and tests for the shearing-box boundary advection scheme of point-like particles.
"""

import numpy as np
import pytest

# half box size (best avoid integer, or "round-looking" values)
dy2 = 0.55

## write_vtk.py
"""
A simple example for writing a valid VTK file in pure Python + numpy (no extra requirements)
"""
import numpy as np

def main(x, y, z, fields, filename, subheader=""):
    nx, ny, nz = shape = (len(_) for _ in (x, y, z))
    ntot = np.product([_-1 for _ in shape])  # number of cells
    with open(filename, 'wb') as fh:
        # two lines of header

## Extension_yt_frontend.md

      
              1 file
            
          
              0 forks
            
          
              0 comments
            
          
              0 stars
            
          
                neutrinoceros
                / Extension_yt_frontend.md
            
            
              Last active
              November 12, 2021 10:12
            
          
    This is a personal note on the migration process to port a yt frontend into its own extension package so that it can be developed outside the main code base.
Steps

A working repo structure

The following structure isn't the only possible one, but it's designed to make migration to the core yt codebase easiest once the frontend is mature and battle tested.
I'll use dummy as a fake frontend name here, just replace it with whatever fits yours. Note that the source directory has to be named yt_<something> to comply with yt's extensions importing rules.


## function_signature_changes.py
import warnings

from functools import wraps
from types import FunctionType
from typing import Dict


def future_keyword_only(positions2names:Dict[int, str]):
    """Warn users when using a future keyword-only argument as positional.

## typing_changes.py
# in Python 3.6
from typing import Dict, List, Tuple
def eggs(a: int, b: List[int]) -> Dict[str, Tuple[int, ...]]:
    ...

# in Python 3.7+, we can use builtin types instead of their typing equivalents
# this becomes the default in Python 3.9
# see https://www.python.org/dev/peps/pep-0585/
from __future__ import annotations
def eggs(a: int, b: list[int]) -> dict[str, tuple[int, ...]]:
	# Python 3.8 is required, but this was only tested manually with 3.12
	from __future__ import annotations

	import argparse
	import re
	import sys
	from dataclasses import dataclass
	from functools import cached_property
	from pathlib import Path
	"""
	Implementation examples and tests for the shearing-box boundary advection scheme of point-like particles.
	"""

	import numpy as np
	import pytest

	# half box size (best avoid integer, or "round-looking" values)
	dy2 = 0.55
	"""
	A simple example for writing a valid VTK file in pure Python + numpy (no extra requirements)
	"""
	import numpy as np

	def main(x, y, z, fields, filename, subheader=""):
	nx, ny, nz = shape = (len(_) for _ in (x, y, z))
	ntot = np.product([_-1 for _ in shape]) # number of cells
	with open(filename, 'wb') as fh:
	# two lines of header
	import warnings

	from functools import wraps
	from types import FunctionType
	from typing import Dict


	def future_keyword_only(positions2names:Dict[int, str]):
	"""Warn users when using a future keyword-only argument as positional.
	# in Python 3.6
	from typing import Dict, List, Tuple
	def eggs(a: int, b: List[int]) -> Dict[str, Tuple[int, ...]]:
	...

	# in Python 3.7+, we can use builtin types instead of their typing equivalents
	# this becomes the default in Python 3.9
	# see https://www.python.org/dev/peps/pep-0585/
	from __future__ import annotations
	def eggs(a: int, b: list[int]) -> dict[str, tuple[int, ...]]: