Memoria | Capstone project -

If so, you can use row_number():

Instead of

• A list of dictionaries (which contains metadata) (option 1)
• Lists of metadata in a single dictionary with corresponding column names (data, title, price, etc.) (option 2)

(What I call "metadata" is all the pieces of information that describes a single item : in your case, that would be : the item price, the extraction date, the reviews on a specific item, and so on.)

When scraping is done, I build the DataFrame only as a final step.

As a final note, I didn't want to mess with your original script too much, but I think you should consider two things :

• Build a function to wrap your scraping steps (or maybe even a class so you can add a single function that handles all the similar things you're doing : collecting metadata on a product)
• You should probably replace "Sin Marc", "Sin Reviews" with np.nan, it will make your data processing and analysis easier

In the modification I did in your script, I choose option 2. I'm not sure about that, but I would guess that option 2 is more efficient than option 1. However, I find it useful, sometimes, when you handle more complex data to build a dictionary first and then, happen the dictionary corresponding to a single item into a list of dictionaries (that would be option 1) : it can make it easier to track each item at a time.

You first include database.h which declares the p_register function:

The check shows that your code may or may not be used to manipulate data or access portions or your software/company which would be otherwise restricted and prohibited.

Lets get into detail. A1 injection. That simply says that you load readable data from an extern file which could be manipulated. e.g. if you keep access-data in a property-file which can be read or changed. The property files have no security measure (like CRC or encoding).

A5 access. It warns you that you - if you load and use the data right away - may infect your system with a manipulated access or redirection to prohibited systems (e.g. you save a link to a hidden port which is normally only accessable via some kind of login-control).

The key to be on the safe side is "sanitizing your input-data". Control each and every pair for (a) value and range (b) accessibility of data and links (e.g. compare it with entries in databases if this user is allowed to do that) (c) store only values which are really necessary for this workstation (e.g. size of monitor, shortcuts, options, ..). If you do all that you can see it as what it is - a fair warning.