Mootallica posted:

I might be blind because I haven't seen it discussed, but is the Python Humble Bundle worth it?


I was originally looking at the $15 tier as I don't think the other tiers would be any good for me (At best I just write small scripts to help automate things, web scraping and DB stuff) - but I remember reading earlier in the thread that Fluent Python is good and probably worth the $20?

Dominoes posted:

Is it possible to override Python's built-in error handling with a third-party module import? I'd like to improve them to be more like Rust's, where it makes educated guesses about what you did wrong, and what the fix is. (eg, rather than just raise an AttributeError or NameError, point out a best guess of the attribute or variable you misspelled.)

necrotic posted:

There's an entry in SecurityGroups that doesn't have a Tags key, which would throw that error. You probably want to make sure the Tags key exists before reading it!

necrotic posted:

That error means one of the securitygroup iterations does not have a key "Tags" defined, so the error is thrown. You basically want:

code:

for securitygroup in response["SecurityGroups"]:
    if "Tags" in securitygroup:
        for tag in securitygroup["Tags"]:
            # blah blah blah

LochNessMonster posted:

Lysidas posted:

Are you absolutely certain that you are communicating with a different server when you access (e.g.) https://www.company.com/some-path vs. https://www.company.com/? That is generally not how DNS, TCP/IP, TLS/SSL, and HTTP work -- one cannot have a specific URL path served by a different publicly accessible web server, with a different certificate, from the same hostname.

When you connect to https://www.company.com/some-path, the following happens, more or less:

1. Your system performs a DNS query for www.company.com
   
2. Your TLS/SSL library connects to the appropriate IP address over port 443
   
3. Your HTTP client uses the TLS-wrapped socket to request the path /some-path with hostname www.company.com
   
4. The server software fulfills this request in whatever way is appropriate
   

_{(Note that SNI alters this process a bit, allowing server software to return different certificates when different hostnames are requested, but this doesn't help you. This only applies when you have multiple hostnames mapping to the same IP address, not the same hostname apparently referencing different machines.)}

If you're absolutely sure that a different machine is responsible for the path https://www.company.com/some-path vs. https://www.company.com/, that doesn't mean you can directly connect to that machine to obtain its certificate. One can configure a reverse proxy like nginx to route requests for certain paths to different internal or even external servers, but in this case you are not communicating with that other server to get the content for https://www.company.com/some-path -- the server software for https://www.company.com/ is making this connection, presumably validating the other system's certificate if connecting over HTTPS, and then relaying the data to you. In this situation, you never directly connect to the other server, and even if it's publicly accessible, you have no way of knowing its hostname/IP address/anything about it.

e: and of course someone can set up https://www.company.com/some-path to redirect to a different hostname/path altogether, in which case it should be pretty trivial to parse that reply in your software to connect to that other host instead

The Fool posted:

Yeah, Basic Auth doesn't work for Sharepoint.

Thermopyle posted:

I really like how pipenv manages your virtualenvs for you.

I really do not like how slow it is at locking dependencies.

SurgicalOntologist posted:

This reminded me that I've never used pipenv and though I usually write library code I have one or two applications that I could port. I currently use a conda requirements file for those. Should I switch?

SurgicalOntologist posted:

Should I switch?

Thermopyle posted:

I think the way forward is too in flux right now.

But, I think if you choose the most popular one (pipenv), no matter what happens you will end up being fine.

Like there will probably be tools to convert your Pipfile to FuturePipfileReplacement. Actually, if whatever you use can export a requirements.txt you can probably move between all of the solutions without much effort.

SurgicalOntologist posted:

I think what's often missing in these discussions is the difference between applications and libraries. I didn't read the whole reddit thread but KR does mention that pipenv is only for applications, I'm just not sure it got much attention.

Master_Odin posted:

Except what about for developing libraries? I think it's more that including/excluding setup.py should be determined on if you're writing an application or a library (exclude on former, include on latter), but you should probably always have a Pipfile and Pipfile.lock for ease of development? KR has certainly included them in requests at the very least.

SurgicalOntologist posted:

Genuinely asking, what are the benefits for ease of development? Once I have setup.py, if I want to develop a new machine I just run pip install -e. and I'm ready to go.

Dominoes posted:

You should try it.

Bash code:

pip install pipenv
cd ~/myproject
pipenv install

Then you can

Bash code:

pipenv shell

from inside your proj directory to activate the environment

or

Bash code:

pipenv run command

to run a single command.