tzf.pyramid_routing

Fizyk przygotował paczkę, za pomocą której w wygodny sposób można wczytywać ścieżki we frameworku Pyramid ;).

Instalacja przez pip:
pip install tzf.pyramid_routing

Github:
git clone https://github.com/fizyk/pyramid_routing.git
cd pyramid_routing
python setup.py install

Dodawanie ścieżek

Załóżmy, że tworzysz jakąś prostą appkę, gdzie za pomocą urla, chcesz zobaczyć profil jakiegoś użytkownika, statystyki (ogólne, jak i dla każdego usera z osobna) oraz prosty blog. Link do appki to: http://localhost:6543.

Struktura appki:
/my_app
  lib/
    routing/
      __init__.py
      blog.py
      user.py
  views/
    __init__.py
  __init__.py
development.ini

W pliku __init__.py aplikacji umieszczasz:
config.include('tzf.pyramid_routing')

W pliku konfiguracyjnym np. w development.ini  ustawiasz coś na wzór:
routing_package = my_app.lib.routing
gdzie my_app to nazwa aplikacji, a reszta to ścieżka do katalogu, gdzie będzie cały Twój routing.

W  katalogu routing, tworzysz 3 pliki: __init__.py, blog.py oraz user.py.

 __init__.py
routes = [
    dict(name='index', pattern='/'),
    dict(name='statistics', pattern="/statistics"),
]

blog.py
routes = [
    dict(name='blog:index', pattern='/'),
    dict(name='blog:post', pattern="/post/{\d+}"),
]

user.py
routes = [
    dict(name='user:index', pattern='/{name}'),
    dict(name='user:statistics', pattern="/{name}/statistics"),
]

Co to tak właściwie robi? Nazwa modułu mówi o tym jak ma wyglądać pierwszy parametr ścieżki url. Np. dla modułu __init__.py będą to:
  • http://localhost:6543
  • http://localhost:6543/statistics
dla modułu blog.py:
  • http://localhost:6543/blog/
  • http://localhost:6543/blog/post/785
i dla modułu user.py:
  • http://localhost:6543/user/sromek
  • http://localhost:6543/user/sromek/statistics

Zmienna routes w modułach musi wskazywać na listę słowników, takich, która przyjmuje metoda pyramid.config.Configurator.add_route. Dokumentację paczki znajdziesz tutaj.

Comments

Post a Comment

Popular posts from this blog

GitLab - extends keyword

Image
In the previous post I had written about the include keyword. Now, let's dive in the extends  keyword. What can you do with this? Here is the definition from GitLab documentation: extends defines entry names that a job that uses extends inherits from. It’s an alternative to using YAML anchors and is a little more flexible and readable. So, when is it useful? It is useful when you want to be DRY and keep your setup cleanly. Let's assume that you want to build a docker image and give developers possibility to deploy the image on dev , staging and prod environments. We are going to do that without the extends keyword, and after that we will think how we can do it better. Example without the extends  keyword: As you can see, there is a lot of code which repeats itself: stage, image, when  and script . We can remove a lot of code! So, let's do that. We are going to create a hidden job .deploy  (you will not see this job in a pipeline) and the rest of the jobs ...
Read more

Managing Secrets in GitLab / Git

Image
Let's say that you have to log in via ssh into an instance, and you work with GitLab, so you want to keep the private key in GitLab somewhere. Is it secure? Let's see! Custom environment variables You can use custom environment variables. Here you can read more about them (Developers cannot change them, only Maintainers and Owners can). There are two types of variables: Variable (the runner creates an environment variable that uses the key for the name and the value for the value) File (the runner creates an environment variable that uses the key for the name. For the value, the runner writes the variable value to a temporary file and uses this path) It seems that we can use File type for our purpose. We can set up it via API or UI . So, let's do that! Go to project's Settings > CI/CD . There will be Variables section (btw, you can specify variables also per group and even for all projects (in admin panel)). Click Add Variable button and add a variable: Key: ...
Read more

Py.test - Splitting conftest file

If you have to maintain a massive project, you probably have many fixtures in conftest file. And there is a problem; this file grows and grows. So, at some point, you decide to split this huge file into smaller files. But, py.test has to know the fixtures are keeping in these files. So, what you can do? I see three patterns here for this: import these guys inside conftest.py file create more conftest.py files use pytest_plugins Import fixtures inside conftest file You can for example do this: 1 2 3 4 5 6 7 8 9 from tests.my_fixtures.fixs1 import ( fix11, fix12, fix13, fix14, fix15, ... ) from tests.my_fixtures.fixs2 import ( fix21, fix22, fix23, ) from tests.my_fixtures.fixs3 import ( fix31, fix32, fix33 ) But, there are some problems with this approach. You import them in an explicit way, so if you create a new fixture, you have to remember to add this guy in the import clause. So, this strategy is not the best solution. If you have many fi...
Read more