Jorge Arévalo jorgeas80

Table of Contents generated with DocToc

FrontEnd Masters - ES6 notes
Rest Parameters

Nice answer on stackoverflow to the question of when to use one or the other content-types for POSTing data, viz. application/x-www-form-urlencoded and multipart/form-data.

“The moral of the story is, if you have binary (non-alphanumeric) data (or a significantly sized payload) to transmit, use multipart/form-data. Otherwise, use application/x-www-form-urlencoded.”

Matt Bridges' answer in full:

The MIME types you mention are the two Content-Type headers for HTTP POST requests that user-agents (browsers) must support. The purpose of both of those types of requests is to send a list of name/value pairs to the server. Depending on the type and amount of data being transmitted, one of the methods will be more efficient than the other. To understand why, you have to look at what each is doing

Interesting ES6 Features

The purpose of this is not to be an exhaustive list or a reference for ES6 features. This is intended to share the interesting ideas that are coming down the pipeline and to explore their intentions.

Create bootable USB from .DMG image file in Linux

Courtesy: [email protected]

Install `dmg2img`

$ sudo apt-get install dmg2img

PSQL

Magic words:

psql -U postgres

Some interesting flags (to see all, use -h or --help depending on your psql version):

-E: will describe the underlaying queries of the \ commands (cool for learning!)
-l: psql will list all databases and then exit (useful if the user you connect with doesn't has a default database, like at AWS RDS)

	class JsonResponseMixin(object):
	"""
	Return json
	"""
	def render_to_response(self, context):
	queryset = self.model.objects.all()
	data = serializers.serialize('json', queryset)
	return HttpResponse(data, content_type='application/json')

	JSON parsing using getJSON

	import mock
	from django.test import TestCase, Client

	import datetime
	class StubDate(datetime.datetime):
	pass

	class TestApp(TestCase):

	@mock.patch('app.views.datetime.datetime', StubDate) #app is the $django_application_name

	"""
	TL/DR:
	Never instantiate mock.Mock() directly.
	Instead use either mock.create_autospec(YourClass) OR mock.patch('YourClass', autospec=True).

	The "spec" feature of Mock is great, it helps avoid your mocked API drifting out of sync with your real API.
	But there is a gotcha if you are mocking classes directly - it's easy to mock the class but you need to
	ensure the spec applies to the instance as well.
	"""

	/* Useful celery config.

	app = Celery('tasks',
	broker='redis://localhost:6379',
	backend='redis://localhost:6379')

	app.conf.update(
	CELERY_TASK_RESULT_EXPIRES=3600,
	CELERY_QUEUES=(
	Queue('default', routing_key='tasks.#'),

	<html>
	<body>
	<form action="/upload" enctype="multipart/form-data" method="post">
	<input type="text" name="title">
	<input type="file" name="file">
	<input type="submit" value="Upload">
	</form>
	</body>
	</html>

Jorge Arévalo jorgeas80

Interesting ES6 Features

Table of contents

Create bootable USB from .DMG image file in Linux

Install dmg2img

PSQL

Install `dmg2img`