summary refs log tree commit diff stats
path: root/win32/copy/share/xml/iso-codes
diff options
context:
space:
mode:
authorTingPing <tingping@tingping.se>2013-10-01 11:21:28 -0400
committerTingPing <tingping@tingping.se>2013-10-03 16:23:46 -0400
commiteb93130cd3a846650dfbb972194190e91564df02 (patch)
tree76a9be4044a9b8e3d108cdce3a0b5d6ecf089f27 /win32/copy/share/xml/iso-codes
parentd643056ca03fb0c6265ae33237fde73a3ec4e7bd (diff)
Remove gtkspell support
Diffstat (limited to 'win32/copy/share/xml/iso-codes')
0 files changed, 0 insertions, 0 deletions
8'>28 29
30
31
32
33
34
35
36
37
38
39
40
41





                 


            

                                                                      
 

                                                                              














                                                                                                                                                 











                                                                              
Hacking GAnarchy
================

Project Structure
-----------------

Dependencies
------------

`requirements.txt` lists known-good, frozen dependencies. if needed or
desired, install dependencies listed in setup.py directly.

GAnarchy uses GAnarchy-based dependencies. they are identified by `gan$COMMIT`
names. e.g. in requirements.txt:

```
-e git+https://soniex2.autistic.space/git-repos/abdl.git@1b26ad799217af7e187fdae78e862a6bf46e5591#egg=gan0f74bd87a23b515b45da7e6f5d9cc82380443dab
```

or in setup.py:

```
install_requires=[
    "gan0f74bd87a23b515b45da7e6f5d9cc82380443dab",  # a boneless datastructure library
]
```

(the comment is just a hint for humans to read)

note however that not all forks are compatible with the project.
requirements.txt provides known-good versions.

Input Validation
----------------

GAnarchy accepts untrusted input: from the user, from remote servers, etc.

Where relevant, input should be validated in `data.py`. For example, URIs
should be normalized (domain and protocol should be converted to
all-lowercase), NULs should be rejected, etc. (FIXME: As of writing this, this
is not the case)