HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
DirkJanJansen
Pandora-Enterprise_Resource_Planning
Python2020–2020
DirkJanJansen / Pandora-Enterprise_Resource_Planning

Pandora-Enterprise_Resource_Planning

ERP Application in PyQt5 and PostgreSQL relational database system. Python3 powered. Interface: Sqlalchemy-Core. Modules: Inventory, Sales, Purchase, Manufactory, Employees, Calculation, Accountancy (portal), Payroll administration, Management modules for inventory control and financial control with graphs are included. For documentation and database structure see Documentation directory. For instructions, installation and several screenshots see Installation directory.

5Distinct people
7Mentions
0Explicit recommenders
128GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

ERP Application in PyQt5 and PostgreSQL relational database system. Python3 powered. Interface: Sqlalchemy-Core. Modules: Inventory, Sales, Purchase, Manufactory, Employees, Calculation, Accountancy (portal), Payroll administration, Management modules for inventory control and financial control with graphs are included. For documentation and database structure see Documentation directory. For instructions, installation and several screenshots see Installation directory.

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 5:04:57 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by week7 dated mentions

Observed mentions: 2020-04-30 06:23:53 UTC to 2020-06-24 09:07:01 UTC. Weeks start Monday, UTC.

02462020-04-27 00:00:00 UTC to 2020-05-04 00:00:00 UTC (exclusive): 6 mentions; 1 submissions, 5 commentsApr 272020-05-04 00:00:00 UTC to 2020-05-11 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-05-11 00:00:00 UTC to 2020-05-18 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-05-18 00:00:00 UTC to 2020-05-25 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-05-25 00:00:00 UTC to 2020-06-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsMay 252020-06-01 00:00:00 UTC to 2020-06-08 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-06-08 00:00:00 UTC to 2020-06-15 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-06-15 00:00:00 UTC to 2020-06-22 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-06-22 00:00:00 UTC to 2020-06-29 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsJun 22

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Apr 272020-04-27 00:00:00 UTC2020-05-04 00:00:00 UTC615
May 42020-05-04 00:00:00 UTC2020-05-11 00:00:00 UTC000
May 112020-05-11 00:00:00 UTC2020-05-18 00:00:00 UTC000
May 182020-05-18 00:00:00 UTC2020-05-25 00:00:00 UTC000
May 252020-05-25 00:00:00 UTC2020-06-01 00:00:00 UTC000
Jun 12020-06-01 00:00:00 UTC2020-06-08 00:00:00 UTC000
Jun 82020-06-08 00:00:00 UTC2020-06-15 00:00:00 UTC000
Jun 152020-06-15 00:00:00 UTC2020-06-22 00:00:00 UTC000
Jun 222020-06-22 00:00:00 UTC2020-06-29 00:00:00 UTC101

What Hacker News says

7 sources
>The problem is that if you are putting this out there for purposes of education, it should use best practices There's a French saying that goes "C'est en forgeant qu'on devient forgeron" (it is by "black-smithing" that one becomes a black-smith). One way to discover best practices is by putting things out in the open and receiving benevolent feedback on how to do it better. The code will improve as the author reads more about best practices to apply on a real project they have shared with the comunity, and a benevolent comunity submitting issues and pull requests. Here's the link to create an issue in that repo: https://github.com/DirkJanJansen/Pandora/issues/new
In ERP-Application in Python, PyQt5 and PostgreSQL
Cool. :) As a general thought for "making it more presentable", it's probably a good idea to embed a screenshot right into the front page README. Just from the point of view that "when things look attractive, people are more inclined to check them out". (Yeah, it's a super generalisation, but it seems to hold true). As an example, we have a screenshot as nearly the first element people can see: https://github.com/sqlitebrowser/sqlitebrowser/ Since you already have a bunch of screenshots, it should be fairly simple to make happen. Maybe these two, as they seem both clean and representative? https://github.com/DirkJanJansen/Pandora/blob/master/Install... https://github.com/DirkJanJansen/Pandora/blob/master/Install...
In ERP-Application in Python, PyQt5 and PostgreSQL
I'm aware, that the code could be organised better. But keep in mind, that the program is not written by a professional. It's intended as an example for integration python with a database system for the community and i am convinced that the program helds many aspects as a learning purpose for instance integrating graphs. And screenshots by the way are available in the project at https://github.com/DirkJanJansen/Pandora/tree/master/Install... And as far as to your first comment over creating tables, this is not creating tables, but defining it to the program. I should read more accurate, before commenting
In ERP-Application in Python, PyQt5 and PostgreSQL
Looking at the Github, it really feels like you should organize your code better. There are many files with the same prefix that should go into their own src/{prefix} subdirectories. The README is really lackluster and should contain installation information and screenshots at least. https://github.com/DirkJanJansen/Pandora/blob/master/invoerI... What the heck is this supposed to be? Are you really creating a database table and then a connection, and executing that in the middle of some random code? You really need to separate this out. And this is not a cherrypicked complaint, this is the first file I randomly clicked in the repo. https://github.com/DirkJanJansen/Pandora/search?q=create_eng... This looks like you're creating a new engine anywhere you need database access. This is NOT how you use SQLAlchemy. Create a database.py file that
Read the rest
contains a SINGLE create_engine function, and define all your tables in one place. This code looks like a real mess. Don't take this as a personal attack. We all had to start somewhere. But this is not something I'd call top quality or really even quality.
In ERP-Application in Python, PyQt5 and PostgreSQL

ERP-Application in Python, PyQt5 and PostgreSQL

Download Link: https://github.com/DirkJanJansen/Pandora ERP Application in PyQt5 and PostgreSQL relational database system. Python3 powered. Interface: Sqlalchemy-Core. Modules: Inventory, Sales, Purchase, Manufactory, Employees, Calculation, Accountancy (portal), Payroll administration, Management modules for inventory control and financial control with graphs are included. For documentation and database structure see Documentation directory. For instructions, installation and several screenshots see Installation directory.
86 points · Open discussion

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.