qiwi | Qiwi у тебя в терминале

Ok, here is one way to obtain what you want in about 2min. Some tickers are bad, that's why it crashes.

Here's the code. I use joblib for threading or multiprocess since it doesn't work in my env. But, that's the spirit.

You have a list of dict in your first example. So first you need to select which dict you want. For instance, if your query is called 'json_list'

The {foreach} syntax from version 2 (which is still supported in version 3) uses string values for the key= and item= parameters. So you have to change your {foreach} loop to:

Please sort $product_var_tpl_list, not $product_var_tpl.

Following is sample code.

The problem is that you have a stack view with a fixed height that contains two views (cView and readerView) that have no intrinsic content size. You need to tell the layout engine how it should size those views to fill the remaining space in the stack view.

It works when you use a .fillEqually distribution because you are telling the layout engine to make all four views in the stack view have an equal height. That defines a height for both the cView and readerView.

When you use a .fill distribution there is no way to determine how high the cView and readerView should be. The layout is ambiguous until you add more constraints. The content priorities do nothing as those views have no intrinsic size that can be stretched or squeezed. You need to set the height of one of the views with no intrinsic size and the other will take the remaining space.

The question is how high should the collection view be? Do you want it to be the same size as the reader view or maybe some proportion of the container view?

For example, suppose your design calls for the collection view to be 25% of the height of the container view with the readerView using the remaining space (the two other views are at their natural intrinsic content size). You could add the following constraint:

Use pandas.Series.str.extract:

Try this

You're passing "SEK" as the currency argument and then try to access a hash value by:

In my six years of iOS programming, I don't remember ever seeing iOS calling viewDidLoad() twice on the same view controller. So it is most likely that you are instantiating CodeStackVC2 twice :)

As far as I can tell, you are creating the view hierarchy programmatically in didFinishLaunchingWithOptions. However, state restoration is invoked before this delegate method is called. So, iOS asks the view controller's restoration class for a new view controller instance, and after that your code setting up the base hierarchy is executed, creating a fresh view controller.

Try moving your code from didFinishLaunchingWithOptions to willFinishLaunchingWithOptions: (which is called before any state restoration). Then, since the view controller that iOS is trying to restore already exists, it won't call that method with the long name from the UIViewControllerRestoration protocol, and instead call decodeRestorableState(with coder:) on that view controller.

If you need a more in-depth explanation, try useyourloaf or of course the Apple docs - I have found both to be very useful in understanding the concepts behind Apple's implementation. Although I must admit, I took me several reads before I understood it myself.